Table Settings reopens the setup wizard for a connected table so you can add or remove source fields, rename or retype columns, and change filter rules after the table exists. Saving changes the table's shape straight away; the data catches up on the next Import.
What you can use it for
- Bringing in a field you skipped. Add Pay Frequency or Employee Work Address months after creating the table; it fills on the next Import.
- Tightening or loosening the filter. Narrow the roster to full-time employees, or widen it again, without rebuilding anything.
- Turning a text column into a dimension. Decide later that Cost Center should roll up by a Cube dimension and switch its type.
- Tidying column names to match how your team talks about the data.
Before you start
- You need Integrations access and edit access on the table.
- Table Settings never calls the source. Field, type, and filter changes are applied to the data only when you run Import.
- Mapping is not part of Table Settings. Edit it on the table's Mapping page.
- Review at the end of the wizard is a recap of the name, scenarios, and access. To add or remove scenarios, use the scenario pane on the table view.
How to change the settings
1. Open the connected table and select the Table Settings icon (the gear) in the header, next to the filter count. To jump straight to the filters, select the filter count and then its pencil icon.
2. On Select Source Fields, check or uncheck source fields, then select Next.
3. On Configure Columns, rename columns or change a Column Type, then continue.
4. On Apply Data Filters, add, change, or remove rules, then select Next.
5. On Review, check the summary and select Done. If you renamed or removed a column, Cube asks you to confirm the column changes.
6. Return to the table and select Import to apply the changes to the data.
How filter rules work
Each rule names a field, an operator (is in or is not in), and one or more values. Type a value and press Enter to add it as a chip; select the chip's × to remove it, or the trash icon to remove the whole rule. Values are free text and match regardless of case or surrounding spaces; dates are compared as dates. All rules must match ("Include records when all match"), each field can carry one rule, and only fields you selected on Select Source Fields are offered. With no rules, every record is imported.
Dimension fields are not offered in the field list. To leave out dimension values such as a location, map them to Ignore on the Mapping page. Ignore and filter rules behave the same way on Import.
A field used in a filter rule is protected: it cannot be unchecked on Select Source Fields, cannot be switched to a dimension type, and cannot be deleted. Delete the rule first, then make the change. The wizard tells you this inline.
What each change does on the next Import
| Change | What happens |
|---|---|
| Add a source field | A new column arrives empty and fills on the next Import |
| Remove a source field | The column and its data are removed after you confirm. If the field was a dimension column, its mapping goes with it. |
| Rename a column | The name changes after you confirm. Formulas keep working because they are bound to the column, not its name. |
| Switch a column to a dimension type | After you save, run a dimension sync from the Connection Overview to see the values, map them on the Mapping page, then Import. If you Import first, it syncs the values and stops because they need mapping. |
| Switch a dimension column to Text | After you save, the dimension's tab and mapping are gone, and the column holds the raw source value on the next Import. |
| Change a type (for example Text to Numeric) | Save is never blocked. If existing source values do not fit, the next Import fails without writing. In edit mode, cells that do not fit block Save until corrected or cleared. |
| Change a filter rule | Synced rows that no longer match move to Out of Sync and keep every value. Rows that match again return to Synced. Records that never matched are not brought in. |
Examples
Fixing a filter value
A roster's first Import fails. The analyst opens the filter summary from the header and sees Pay Frequency is in YEARLY, but the source value is YEAR. She opens Table Settings, moves to Apply Data Filters, changes the rule to Pay Period is in YEAR, selects Done, and imports again. 305 rows arrive.
Narrowing to full-time
The roster has 305 Synced rows. The analyst adds Employment Type is in FULL_TIME, saves, and selects Import. The table still has 305 rows: 296 Synced and 9 Out of Sync, the part-time staff, with every note and assumption intact. She removes the rule and imports again, and the 9 return to Synced.
Making Cost Center a dimension
Cost Center 2 was imported as Text. The analyst switches it to the dimension type in Configure Columns and saves. On the Connection Overview she runs the dimension sync; the Mapping page shows 12 unmapped values. She maps them and imports. Cost Center 2 now rolls up by her Cube dimension.
Other things to know
- Custom columns and their values are kept through every Table Settings change.
- Data Source is skipped in Table Settings because a table's source cannot change. To pull from a different integration, create a new table.
- The filter count in the header always shows how many rules are active, and selecting it lists them.
- Calculated columns recalculate after the next Import.