The docs tell me I can use a dynamic data key to color rows of a table component that meet certain criteria.
I have a named query data source, standard table, header and row details setup. I enabled Alternate Row on the details, then added a custom row for low inventory.
On the Fill:
The column name is CurrentStock. No matter the number value I use, I don't see any light red in the preview. (Note: I just created a report viewer to see it live, and still no red.)
So, I tried the keychain syntax: named_query.CurrentStock, still no dice. Not sure where to go from here.
Note: just tried this, below and nothing.
One other unrelated question on reports: The data spills over onto a second page, but the header and data are at the bottom, instead of the top. Why is this and how can I fix it?
If there is only one color you want to use for the one condition, just set the fill color with the color picker then set the fill to CurrentStock<=5, this should work.
Ok, I got it to work, but I am not sure what the problem is, or actually I am not sure why the problem is.
I put the red coloring on a custom details row, like you click this:
add your custom row version... and that's where the condition stock<=5 was placed. After I added the conditional coloring to the standard row version, then I saw red.
Some thoughts on this:
Why does the custom row version not display? (See the first image in the first post "LowInv".
Why does the alternate row version override the conditional coloring on the standard row version?
I must admit I didn't know custom row versioning existed, and did not find it that intuitive.
As far as I can tell its whole thing is to override the standard row version for rows that meet the criteria.
As for your first bullet point, if the Version Key keychain expression results in the name of your custom row version it would apply the stroke and fill as configured for that custom row version.
