You can change these settings in two ways, both of which change the model. If you want to make a few small changes, you should make them in the ThoughtSpot application . If you want to make many changes you should edit the modeling file. Whether you are changing data modeling settings using the modeling file or the Web interface, the settings and their accepted values are the same.
The following index includes mutable data modeling settings that you can apply to columns, both tables and worksheets.
|Column Name||Sets the name of the column to be used in searches.|
|Description||Adds a text description of what the column contains.|
|Data Type||Read only. Shows the column’s data type.|
|Column Type||Sets the type of column, either
|Additive||Controls the type of aggregations that will be available for a column.|
|Aggregation||Sets the default aggregation type for a column.|
|Hidden||Sets the visibility of a column.|
|Synonyms||Adds synonyms that can be used in the search bar to refer to a column.|
|SpotIQ Preference||Excludes specified columns from SpotIQ analyses. By Default, all columns are included in SpotIQ.|
|Index Type||Sets the type of index that will be created for a column.|
|Geo Config||Enables a column to be used in GeoMap visualizations.|
|Index Priority||Changes the priority of a column in search suggestions.|
|Format Pattern||Specifies the format to use for numeric values or dates that show in the column.|
|Currency Type||Specifies the format of currencies in a column.|
|Attribution Dimension||Only applies to tables that join over a Chasm Trap. Designates whether the tables depend on this column for attribution.|
|Calendar Type||Specifies what type of calendar a date type column uses. It can be Gregorian calendar (default), a fiscal calendar, or any custom calendar.|
|Entity Category||Specifies how to categorize the data in the column: person, place, time, and so on. Important for configuring SearchIQ (Beta).|
|SearchIQ Enabled||Indicates if the column is enabled for SearchIQ. Note that SearchIQ is in Beta.|
Data modeling best practices
As a best practice, make any data modeling settings in the table when you will be creating multiple worksheets that use that table. This way, you won’t have to make the same settings in each worksheet. The settings will be inherited when you create worksheets that uses columns from the table.
If you have settings that only apply in the context of a particular worksheet, make those settings in the worksheet rather than in the underlying table(s).
Note that if you make your settings at the table level, and then create a worksheet that uses columns from the table, the settings are inherited from the table at the point in time that the worksheet is created. If you then go back and change the settings at the table level, your changes will not be reflected in the worksheet.
If you want the worksheet to have the changes you made at the table level, you must drop those columns from the worksheet and re-add them. Then save the worksheet. At this point, the new settings will be used in the worksheet. Note that any saved answers or pinboards based on the worksheet may display differently because of your changes. For example, if you’ve changed the GeoMap setting from “None” to “Country”, you will now see a map where before you might have seen a table.