Table component: Column Attribute Data

General Discussion
3

Thanks Phil
It appears that the columnAttributesTable dataset (always?) has 30 columns, one for each formatting attribute that is exposed.
It has n rows, one for each column of the source ‘data’ (the dataset whose data is displayed on the table).

So I guess what you are saying is, in the template:

  1. create a ‘default’ row in the template.
  2. for each column in the ‘data’ dataset, create a new row in a new dataset using the default row
  3. assign this new dataset to the columnAttributesTable of the table in the template
    So, the template will have a “standard” table, but with the columnAttributesTable configured as a dataset instead of None

Then, when I instantiate an instance, update the columnAttributesTable dataset as required. Note: The only attributes I plan to change are the ‘editable’ and ‘hidden’ attributes.

Is this what you are suggesting? From your experience, can the columnAttributesTable be updated in this way?

Thanks
Ross