Overview of data modeling settings
You can change data modeling settings in two ways, both of which change the model. If you want to make a few small changes, make them in the ThoughtSpot application. If you want to make many changes, 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.
If you are using ThoughtSpot’s dbt sync to create ThoughtSpot Models based on your dbt models, change the data modeling settings in your dbt schema.yml file, using ThoughtSpot’s dbt metadata tags.
Modeling settings
The following index includes mutable data modeling settings that you can apply to columns, both tables and Models.
| Setting | Description |
|---|---|
Sets the name of the column to be used in searches. |
|
Adds a text description of what the column contains. |
|
Read only. Shows the column’s data type. |
|
Sets the type of column, either |
|
Controls the type of aggregations that will be available for a column. |
|
Sets the default aggregation type for a column. |
|
Sets the visibility of a column. |
|
Adds synonyms that can be used in the search bar to refer to a column. |
|
Excludes specified columns from SpotIQ analyses. By Default, all columns are included in SpotIQ. |
|
Sets the type of index that will be created for a column. |
|
Enables a column to be used in geo map visualizations. |
|
Changes the priority of a column in search suggestions. |
|
Specifies the format to use for numeric values or dates that show in the column. |
|
Specifies the format of currencies in a column. |
|
Only applies to tables that join over a chasm trap. Designates whether the tables depend on this column for attribution. You cannot change the attribution dimension in the modeling file. You can only configure it on a table-by-table basis. |
|
Specifies what type of calendar a date type column uses. It can be Gregorian calendar (default), a fiscal calendar, or any custom calendar. |
Data modeling best practices
As a best practice, make any data modeling settings in the table when you will be creating multiple Models that use that table. This way, you won’t have to make the same settings in each Model. The settings will be inherited when you create Models that uses columns from the table.
If you have settings that only apply in the context of a particular Model, make those settings in the Model rather than in the underlying table(s).
Note that if you make your settings at the table level, and then create a Model that uses columns from the table, the settings are inherited from the table at the point in time that the Model is created. If you then go back and change the settings at the table level, your changes will not be reflected in the Model.
If you want the Model to have the changes you made at the table level, you must drop those columns from the Model and re-add them. Then save the Model. At this point, the new settings will be used in the Model. Note that any saved Answers or Liveboards based on the Model may display differently because of your changes. For example, if you’ve changed the geo map setting from "None" to "Country", you will now see a map where before you might have seen a table.
Related information
