Hey Carl!
The _cfv keyword supports both numeric and text values.
If you use this keyword along with Knack’s built-in display rules, the keyword will have precedence because executed after the view’s render, thus overwriting the rules.
In the case of the Stock Qty you see above, yes the field is numeric. The keyword string is this one:
_cfv=[lt,125,yellow, black], [lt,115,orange, black], [lt,75,red, black]
It is placed in the field’s description like this:
The _cfv keyword can be used in grid and list views. In such cases, it will be applied to the current view only, unless a specific selector is used (ktlSel option).
When placed in the field, it is applied all across the app, in all grid and lists, and has precedence of the view/grid usage.
In the example here, I have multiple groups of parameters, defining color ranges based on the “less than value” (lt) operator. Since they are executed from left to right, the latter overwrites the previous and this creates the gradient effect.
There’s also several string operators: equals, not equal, starts with, etc.
And options to propagate the color to the row, etc. Pretty cool stuff!
In short, yes I think it works a lot like Excel.
Norm