Edit models

When you create a model you can edit its tables, columns, column properties, formulas, filters, parameters, and other settings.

Edit an existing model

If you have edit permissions for a model:

In the top navigation bar, use the workspace selector to go to the Data workspace.
Select the name of the model, then select Edit model.

You don't have edit permissions for the pre-configured models that Guidewire created. To customize these models:

Open the model, then select Joins to see its source tables.
Create a new model and add the same tables and columns to your new model.
Customize the model by adding or removing tables and columns.

Add and remove tables

You can join more tables to a model if you want to use their columns. You can also remove tables if you don't use any of their columns.

To add a table:

In the top navigation bar, use the workspace selector to go to the Data workspace.
Select the name of the model, then select Edit model.
Drag and drop one or more tables. To find a specific table, use the search bar, filter by tag, or sort the list.
1. If tables were already joined at the table level, those joins appear as recommendations in the model diagram. Select the join icon , then select Accept recommended join.
2. If a table doesn't have a recommended join, that means it wasn't already joined at the table level. Edit the original table in Explore to create the join. Then add the table and its recommended join to the model.
  Important: If you join in the model but not in the table, it creates a chasm trap. Chasm traps prevent you from viewing underlying data in an Answer.

To remove a table: In the model diagram, select the ellipsis in the corner of a table, then select Remove table.

Add and remove columns

To add columns:

In the top navigation bar, use the workspace selector to go to the Data workspace.
Select the name of the model, then select Edit model.
Select Columns, then in the sidebar, expand a table name to see all of its columns.
1. To add all of the columns from a table, click and drag the table name into the center of the screen. Or click and drag individual columns.
2. After adding columns, check for any that are highlighted in red, which means there's a duplicate column name. Remove duplicate columns or give them unique names.
3. If needed, rename columns to make them business-friendly. Explore automatically capitalizes column names and replaces underscores with spaces.
4. Select Save changes, then give the model a business-friendly name and description.

To remove columns: Select the check box next to a column, then select Remove.

Column properties

In the Columns tab of the model editor, select a property value to edit it. Or you can bulk edit column properties. The default values are inherited from the source table in Explore. Explore automatically sets some properties based on the data type and column type. Some properties aren't editable, if they aren't relevant to the column.

Property	Description
Column name	Users type this name to add a column to their search. Make sure it's meaningful to users.
Source table name	You can't edit this property. If the value is Formula, that means the column comes from a custom formula created in the Formulas tab in the model editor.
Source column name	You can't edit this property.
Description	When a user searches data to create an Answer, they can see this description in the Column information panel.
Data type	You can't edit this property.
Column type	Describes if the data is an Attribute or Measure. Measures must contain a numeric value that can meaningfully use math. This property is set automatically, but sometimes you need to fix it. For example, if Explore incorrectly sets a number like a zip code as a measure, you can change it to an attribute. Note: Guidewire recommends setting this property at the table level so that it's consistent for all models that use the table.
Additive	If additive is set to Yes, users can perform calculations such as `average`, `min`, and `variance` on that column.
Aggregation	Sets a default aggregation type for the column so that users don't have to set it when they search data. If the column is set to Additive: Yes, there are more available aggregation types. Note: Guidewire recommends setting this property at the table level so that it's consistent for all models that use the table.
Hidden	Hides the column from users who have View permissions for the model. For example, you might add columns to the model in order to use them in the model's filter or formula. But if those columns aren't otherwise useful for reporting, you can hide them. Note: Users with Edit permissions can see and use the column. If they create an Answer or Liveboard with the hidden column, everyone can see the data.
Synonyms	Synonyms help users find a column when they use different search terms. Add synonyms in a column separated list.
Suggest values in search	Determines whether the column's values will appear as suggestions when users search data. For example, if you start a search with the `Status` column, then begin to type `Bo`, the value `Bound` appears as a suggestion.
Geo config	Sets the type of geographic data in the column, for use in geo map charts. This property is set to Auto select by default. If you find it's inaccurate when creating charts, you might need to go back to the model and set the geo config property manually.
Index priority	Determines the order that the column and its values appear in the search suggestions. It also affects which columns Explore prioritizes when generating AI Answers. The default priority is 1 for all columns. You can change it to a number between 1 and 10.
Format pattern	Sets the display format for numbers or dates. See the ThoughtSpot documentation for valid formats: Set number and date formats
Currency type	Sets the display format for currencies.
Attribution dimension	If set to Yes, this property prevents double counting with chasm trap models. A chasm trap occurs when fact tables have no direct relationship to each other except through shared dimensions. Explore automatically sets this property when tables join over a chasm trap and generate an attribution query.
SpotIQ preference	Determines if the column is included in Spot IQ analyses. Default means the column is included.
Calendar type	If you created a custom calendar, you can apply it to the column.
Custom sort	Defines a custom sort order for the column values. When users create a chart with the column, they can switch from Alphanumeric sort to this predefined Custom sort. Add the values in a column separated list, in order.

Formulas

In the Formulas tab of the model editor, you can create new calculated columns. The formula is added to the model as a column. To learn more about formula functions, see the ThoughtSpot documentation: Formula function reference

Formulas can also mask data to hide the value of a column from certain groups.

Filters

In the Filters tab of the model editor, you can limit the rows that appear in the model. You can exclude or include rows with specified values. Create a filter when you want to:

Remove rows that aren't useful for analysis and reporting.
Hide data from specific groups of users. Create one version of a model with some columns filtered out, then share it with that user group. You can create another version of the model with different filters, and share with other users.

Important: When you view columns in the Columns tab (not the Filters tab), you can click on the table header and Sort or Filter. These settings change what you see in the model editor, but they don't apply to the model permanently or affect users.

Parameters

In the Parameters tab of the model editor, you can create parameters (a container for adjustable values) to later use in formulas or Liveboards. For example, if you create a parameter with the values high, medium, and low, users can select from those values in a Liveboard. In a formula, you can then reference the parameter: "If a user sets the parameter to high, show XYZ values."

You don't have to create parameters on the model level; Users can create their own parameters when they create an Answer. But, you must create a parameter in a model if you want to:

Apply the parameter to an entire Liveboard (not just one Answer).
Use the parameter in a formula within the model.

To learn more about parameters, see the ThoughtSpot documentation: Using parameters

Data model join rule

In the Settings tab of the model editor, you can choose how joins are applied during a user’s search:

Apply joins progressively (recommended for most cases): When a user creates a search with the model, joins are only applied for tables whose columns are included in the search.
Apply all joins: All possible joins are applied.

Disable row-level security

In the Settings tab of the model editor, you can disable row-level security for the model. You must have the Row-Level Security (RLS) Bypass role. Row-level security is created at the table level and inherited by the model, so this setting allows you to bypass it. To learn more about RLS, see Hiding data from specific groups or users.