asked on January 7, 2022
We are running into issues with conditional formatting we observed string values are used to store formats like "#value < 9000" but this fails to perform the correct comparisons because the values are strings and not numbers. Additionally, it seems a recent update actually turned off selecting non-number fields in the conditional formatting modal, so now if we upgrade we can't select Date.Day (and many others) if we wanted to.
It seems that .Day and .Year fields should be treated as numbers. Otherwise on upgrade we are faced with a breaking change were customer lose any conditional formats they have set. Looking forward to your thoughts.
⋅ January 12, 2022
Hello, John,
Thank you for reaching out to us.
Our team is currently working on your question. We will get back to you soon.
Kind regards,
Nadia
⋅ January 12, 2022
Hello, John,
Please find our answer below.
Conditional formatting wasn't intended to work with the strings. Still, string fields were available for selection in the conditional formatting pop-up. Several versions ago we decided to hide such fields from the pop-up to avoid further confusion. However, when such formatting rules are defined in a report, they still work the same way as in previous versions. In other words, if you decide to upgrade Flexmonster, the hiding of the fields on the UI won't affect already created reports.
Speaking of the .Day and .Year fields, we would also like to specify that due to date hierarchy logic, it is not possible to treat such fields as numbers.
Please let us know if our answer helped you. Feel free to contact us if other questions arise.
Kind regards,
Nadia
