What's New

API

Access Sigma from the command line using the Sigma CLI (GA)

You can access the Sigma REST API programmatically from your terminal using the Sigma command-line interface (CLI) tool. The Sigma CLI (sigma) simplifies interaction with the Sigma REST API by providing quality-of-life features to developers, such as authentication management, typed commands, and profile-based configuration.

For more information, see Sigma CLI.

Databricks HTTP path included in connection API responses

For Databricks connections, the Get connection details (GET /v2/connections/{connectionId}) and List connections (GET /v2/connections) endpoints now include httpPath in the response. The field provides the HTTP path of the SQL warehouse and is not included when a user attribute sets the HTTP path.

New API endpoints for managing materialization schedules (Beta)

The following endpoints are now available for creating. updating, and deleting scheduled materializations of workbook and data model elements:

• Create a materialization schedule for a workbook element (POST /v2/workbooks/:workbookId/elements/:elementId/materializationSchedules)
• Create a materialization schedule for a data model element (POST /v2/dataModels/:dataModelId/elements/:elementId/materializationSchedules)
• Update a materialization schedule for a workbook element (PATCH /v2/workbooks/:workbookId/elements/:elementId/materializationSchedules)
• Update a materialization schedule for a data model element (PATCH /v2/dataModels/:dataModelId/elements/:elementId/materializationSchedules)
• Delete a materialization schedule for a workbook element (DELETE /v2/workbooks/:workbookId/elements/:elementId/materializationSchedules)
• Delete a materialization schedule for a data model element (DELETE /v2/dataModels/:dataModelId/elements/:elementId/materializationSchedules)

Use these endpoints to create and manage materializations programmatically.

For more details on scheduling materializations of workbook and data model elements, see Schedule materialization for a data model or workbook (Beta).

New API endpoint for creating shortcuts

The following endpoint is now available for creating shortcuts to documents and other items in Sigma:

• Create a shortcut (POST /v2/shortcuts)

Use this endpoint to surface documents and other items in other folders or workspaces without duplicating them.

For more details on creating and using shortcuts in Sigma, see Add shortcuts to documents.

Data modeling

Restrict access to data model elements (Beta)

You can now configure data security rules for an entire data model element using column-level security (CLS). When configuring CLS in a data model, you can now select All columns, or select each column in the element individually, to restrict and hide the entire element for users who do not have access.

Users editing the data model can still see the element while in the draft of the data model, regardless of if they have access to it according to the CLS rule. Users who do not have access to the element cannot see it in the data model overview page or source picker, and cannot access it in workbooks or data models that use it as a source.

For more information, see Restrict access to data model elements using CLS.

Update selected references when migrating a dataset to a data model

After you migrate a dataset to a data model, you can now update the documents that use the dataset as a data source to use the new data model selectively instead of all at once. Update references in small batches to confirm that the data model returns the same results as the dataset before proceeding with the remaining references.

For more information, see Update selected references after a migration.

Embeds

Inbound event to refresh workbook data in embeds

Use the workbook:refresh inbound JavaScript event to refresh the data in one element or all elements in a workbook. For more details, see Inbound event reference.

Reports

Move report elements to a new page

You can now move report elements to a new page while preserving the position of the elements.

See [Move elements to a new page](/docs/Build reports/build-and-customize-reports/customize-element-size-position-and-layering#move-elements-to-a-new-page).

Workbook elements

Incremental data fetching for plugins

When a plugin loads data from a workbook element, Sigma sends the data in batches of 25,000 rows. As of version 1.3.2 of the @sigmacomputing/plugin package, plugins can be configured so that each batch contains only the new rows, instead of re-sending every row already loaded, reducing load time for plugins that use data from large elements.

Existing plugins continue to work without changes. To opt in, replace usePaginatedElementData with useIncrementalElementData. If you use the plugin development API without React Hooks, use subscribeToIncrementalElementData.

For more information, see the plugin development API on GitHub.

Updated region data for maps

Region maps now use updated boundary data. Regions whose names or codes changed no longer plot on the map and appear in the missing data modal. This includes Connecticut counties, whose borders were redrawn.

US territories are now supported as US states, including Puerto Rico.

For lists of supported country and US county names, as well as supported US zip codes, see Maps - Region.

Bug fixes and improvements

• The Sigma MCP connector can now query elements from data models.

• The icons used to represent data models and data model table elements have been updated. Previously, the same icon was used to represent a data model and the elements within it.