Hey, this is a great improvement! I’m curious about one limitation - the list of “condition” fields is limited to just those that are shown in the widget, meaning we can’t set up formatting rules based on “hidden” columns. Is this intended behavior or something that can be easily addressed?
For example, in the above video, the first two rules are based on the presence of a specific string in a text field representing status:
These rules depend on that exact text appearing in the “Status” field. But if, for example, the app needs to be multilingual, these rules would fail and need to be duplicated for every language. For this kind of case, our team would use an integer ID for each different status so we could build rules that would work regardless of user language.
Since the user doesn’t care about the status ID, we would rather not show that column in the app - but this limitation in conditional formatting forces us to include it in the list of “fields” and just place it horizontally beyond the viewport of the widget so we can use it in a rule like this.
Curious of your thoughts on this - please let me know if I should make a separate feature request post, thanks!
Stay tuned!