Hi @nimster!
It's definitely a feature we need to document better 
:
"Use dynamic column settings" is evaluated as a Boolean, if true then the "Column settings" input will be used, otherwise it will not. Any setting that has an "fx" is an option to define a setting which would normally be toggled on/off based on some {{ }} value instead.
"Column settings" takes an array of objects [{},{},{}]. The key/values in that object can define a small number of setting dynamically. If any setting is used here, it should overwrite the options in the column setting popover.:
name: if a column's name is included in the array, it will be displayed. If there is no object that includes the column name, it will be hidden.
type: the column type to display the cell values in this column as. This can be any of the types which are available inside of this dropdown-
Their correct identifiers are:
- default
- modal
- button
- checkbox
- datepicker
- textinput
- dropdown
- string
- date
- datetime
- datetime_tz
- link
- object
- integer
- percent
- float
- usd_dollars
- usd_cents
- boolean
mapper: you can dynamically define the mapper to be used in each column as a string, but you will need to escape the {{ }} tag here for it to work. This also only resets when the data updates or the page reloads I believe.
Here's an example using these keys:
Because "name" and "sales" aren't included in the array, they are hidden. 'id' is set to a datepicker, and email is mapped as self+1. Since email is a string, this just concats a 1 to the end.
colorMapper: you can also dynamically define the colorMapper using the same stipulations as the mapper key.
I'll work on this post a little more as I dig into the feature, and create an updated docs page to help with the topic!