Note that there are some explanatory texts on larger screens.

plurals
  1. POSSRS 2008 R2 using two iif statements
    primarykey
    data
    text
    <p>In an existing SSRS 2008 r2 report, I have the following <code>IIF(RowNumber(Nothing) Mod 2 = 0, "Gainsboro", "White")</code> for the background color for every other detail line row. Basically one detail line is white and the next detail line is a light green color.</p> <p>Now the user wants every other detail line to remain white and light green color when displayed on the report server. However when the report is to be exported to excel, the user wants all lines exported to excel to be completely white.</p> <p>Here are the steps the user will complete:  The user will select ‘Hide’ from the ‘Excel Export_Hide Headers’ dropdown list.  The user will next select the view button prior to exporting the report to excel.  The user will then select the export to excel option. **The user is basically going to hide the header rows when the report is suppose to be exported to excel. . When the header rows are are being hidden, the following logic is being used: <code>iif(Parameters!ExcelToolbar.Value = 0,false,true)</code>.</p> <p>Thus can you tell me how to tie the <code>iif(Parameters!ExcelToolbar.Value = 0,false,true)</code>, with the <code>IIF(RowNumber(Nothing) Mod 2 = 0, "Gainsboro", "White")</code> statement?</p> <p>Would this be nested iif statements? If so, can you tell show me how to setup the applicable nested iif statements? If this is not the solution, would you show me in code, explain to me, and/or point me to a url that will solve my problem?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload