Hi Guys ,
I'm facing an interesting issue that I need to share. I have a simple query returning for instance 10 rows. I need to fade 1 row over 2 . until now everything's fine I create a conditionnal style on the list column body and add those case statement mod(RowNumber (),2) =0 , mod(RowNumber (),2) =1, for each one I associate the wanted color. All this step works as a charm. My Problem comes when I want to hide/show some row depending on differents business cases ( create conditionnal variable /apply it to the list column body/ set the box type to none if row's hidden) . it turns out that when a row is hidden the rownumber keeps the initial number of row 10 it doesn't recalculate the number of row :( to apply the fading accordingly as a result the fading is messed up. u can see an example on the attached document
The slightest tips/advise on this will be very appreciated
Thank you
Can you filter the query to only return the rows needed to satisfy the business cases rather than using the hide/show logic? That way your alternate shading logic would work as is and the report could even run more efficiently by not returning unnecessary rows that just get hidden anyway.
@ lynn
u're truly right , the pb is the way i'm getting the data from the FM. Data come from views which returns everything in a single rows . the only way to integrate the result in a list it's to drag and drop each value as a singleton. that makes things difficult. client doesn't want to change the way data are returned so we have to get by