What's new in Sigma

API

New endpoint to duplicate a version tagged workbook

The following endpoint to duplicate a version tagged workbook is now available:

New endpoint to retrieve the full path for a table

The following endpoint to retrieve the full path to a table in a connection is now available:

New endpoints to get document sources

The following endpoints to get the source of a workbook or get the source of a dataset are now available:

New endpoints to manage API credentials

The following endpoints to create and delete API credentials are now available:

Embeds

Test JWT-signed embed URLs in the embed sandbox

You can now test embed URLs signed with JSON Web Tokens (JWTs) in the embed sandbox. In addition, the embed sandbox now allows users who have been granted embedding credentials to use the embed sandbox even if they are not assigned the Admin account type.

For more details, see Test an embed URL in the embed sandbox.

Data modeling

dbt Semantic Layer integration (Beta)

You can now configure and query a dbt Semantic Layer integration, allowing you to leverage your predefined dbt metrics in Sigma workbooks.

For more information, see Configure a dbt Semantic Layer integration (Beta) and Query a dbt Semantic Layer integration (Beta).

Workbook features

Configure workbook actions in sequences (Beta)

Organize multiple actions into a sequence to run them in a specified order. You can have multiple sequences on a single element, each with an optional condition.

With action sequences, you can:

  • Ensure that multiple actions on an element execute in the intended order.
  • Drag and drop individual actions within or between sequences to quickly change the order.
  • Duplicate entire sequences of actions.

If you previously configured multiple actions on an element, the introduction of sequences places each of those actions in its own sequence by default. If you keep those actions in separate sequences, your configuration is unchanged and the action execution will behave as it did before.

For more information, see Configure actions in sequences (Beta).

Make actions conditional (GA)

When you define an action for a workbook element, you can now define an optional condition for that action. Customize the trigger behavior of your action based on the value of a control element or using a custom formula.

See Make an action conditional.

Reset to last published value when clearing a control with an action

The clear control workbook action now supports a Reset to published value checkbox. Checking this box resets the control value to the last published value. On a tagged version of a workbook, this setting resets to the tagged version's value.

See Clear a control value.

Schedule exports as an email burst (Beta)

You can send a custom-filtered report to a dynamic list of recipients as a scheduled email burst. Send a workbook, workbook pages, and individual workbook elements as supported attachment types, such as PDF, Excel, or PNG files.

For more details, see Export as email burst (Beta).

Pivot tables support column-specific custom sort order

You can now quickly sort pivot table columns using the context menu, and specify custom sort orders for specific columns. For example, you can now choose to sort a specific pivot table column by the values in a different column. See the section on Customize the sort order of pivot tables in Customize the sort order of data elements.

Bug fixes

  • Clicking the More icon associated with a version tag in the Version history menu no longer reloads the page.
  • In embedded workbooks with themes applied, the theme now applies to the side panel of the workbook as expected.
  • In pivot tables with multiple pivot columns, centering column headers now centers all headers.
  • When configuring actions based on “When selecting cells” trigger, holding ⌘ Command (Mac OS) or Ctrl (Windows) on your keyboard to select multiple values or spans of values now correctly passes the discrete values to the action configuration instead of including all cells between the selections.
  • When multiple action sequences have been configured on an element, Sigma now evaluates the condition of each sequence before beginning any action execution, as expected.