In addition to replacing and adding control value selections, the Set a control value action now supports the ability to remove selections. When you configure separate Set control value actions using Add to existing selection and the new Remove from existing selection option, you can enable users to easily add and remove values from filter controls.
Release notes are now also available on the Sigma Community site. There, you can opt in to receive notifications about future release notes in order to stay on top of everything new happening at Sigma. For more information on how to subscribe to release note notifications, see About the release notes category. You can also subscribe to automated updates in any Slack channel using the Sigma Community release notes RSS feed.
Updated details for source selection
When browsing for a data source in Sigma, such as when choosing or changing the source for a data element, you can see the connection name, full path to the table, and any usage statistics for the table.
Workbook features
Dynamic text for embed element URLs
Embed elements accept dynamic text in the URL field. You can now press = while editing the URL field to open the formula bar and configure a dynamic entry. This can be used to make embed contents responsive to control values, as well as changes to other workbook elements.
Number input control operators
Configure a number input control to filter the targeted data differently. You can now choose other filter operators besides the default of = (equal to) to show data that is greater than or equal to (>=) or less than or equal to (<=) the inputted number value.
Usage dashboards have been improved to provide better performance and easier navigation. To view insights into how your organization uses Sigma and data on your queries, embeds, materializations, and more, go to Administration > Usage. You can also now create and save custom views of your usage dashboards, which allows you to customize the appearance, layout, sorting, and filters of your existing dashboards, or even create new ones of your own.
For more information, see Usage dashboard overview. Outdated documentation about specific usage dashboards has been removed.
Manage upgrade requests in the Administration portal (GA)
The ability to view and respond to account upgrade requests in the Administration portal is now generally available. When a user requests an upgrade to their account type to explore or create workbooks, an admin can review the request in Administration.
Materialization support for version-tagged data models (GA)
Schedule materialization for each tagged version of a data model. If the published version already has a materialization schedule for one or more elements, you can choose to reuse the same schedule for the tagged version.
When you promote a tag to a new version of the data model, such as moving a tag from an older version of the data model to the latest published version, a new materialization run is started. While the materialization runs for the newly tagged version, the materialized data for the previously tagged version of the data model is used.
See the status of elements in your data model in the model overview panel visible when you open a data model for editing but have not yet selected any elements. Elements enabled as a source show with a and elements disabled as a source show with a .
Embeds
New outbound event emitted for saved workbooks
When a workbook is successfully saved using the Save as option from the embed menu, an outbound workbook:saveas event is emitted.
Removed links to Sigma pages in embedded application workbooks
In embedded applications, Sigma no longer includes links that reference Sigma processes or link to Sigma documentation. Sigma links in these sections of a workbook do not appear in embeds:
Column details
Functions bar, specifically the Function icon
Lineage / query history
Metric tab
Performance
Input table error handling
The following changes to input tables have been implemented to improve data integrity and prevent unexpected data loss:
Input table edits that are unsuccessful due to configuration or availability issues in the connection or data platform (which must be resolved by the customer) are now treated as fatal errors and will no longer be retried.
When Sigma detects a configuration or availability issue in the connection or data platform, it blocks edits to relevant input tables and displays an “Unable to edit” message directly on the input table elements until the configuration issue is resolved.
Sigma sends admins an email alert that identifies the misconfigured or unavailable connection, displays the error message, and provides troubleshooting guidance.
Workbook features
Export to Microsoft Teams and SharePoint (Beta)
Export a workbook, workbook page, or element from Sigma to a Microsoft Teams channel or a Microsoft SharePoint folder.
To start exporting to Teams or SharePoint, a user with the Admin account type must set up a Microsoft integration and the relevant account type permission must be enabled for users.
When you export a workbook, page, or element to a PDF, you can now choose the page size. In addition to the previously supported Letter size, you can now export to Legal, Tabloid, A0, A1, A2, A3, and A4 page sizes.
Bug fix
Formulas in action configurations were previously limited to functions supported by all compatible data platforms. You can now use any function supported by your connection's data platform.
The Create a member (POST /v2/members) endpoint includes a new option to add users to teams when adding them to Sigma. Specify the teamId in the addToTeams option to add a user to one or more teams when you create them in Sigma, and optionally use the isTeamAdmin option to make the user an admin of the team.
Functions and calculations
New DayOfYear function and day_of_yearDatePart argument
Return the day of the year as a number (1-365, or 1-366 in leap years) from a date using the DayOfYear function. You can also return the day of the year as a number using day_of_year in the precision argument of the DatePart function.
RegressionSlope function
The RegressionSlope function calculates the slope of the linear regression line. The function is now supported for Databricks, Snowflake, and PostgreSQL.
The RegressionIntercept function calculates the y-intercept of the linear regression line. The function is now supported for Databricks, Snowflake, and PostgreSQL.
The RegressionR2 function calculates the R2 value, or coefficient of determination, of the linear regression line. The function is now supported for Databricks, Snowflake, and PostgreSQL.
Sigma is now deployed in Azure Canada. Located in Toronto, this deployment gives customers in Canada more control over data storage while enabling compliance with internal policies and external data residency requirements.
Configure data labels per series on Cartesian charts (GA)
If your Cartesian (bar, line, area, or scatter) or combo chart visualizes multiple series of data, you can configure different data label settings for each series. See "Format and show data labels" in Display chart data labels.
Workbook features
Limit display values in a data element (GA)
Limit the number of values displayed in a grouped table, pivot table, or chart, and group the remaining values in an "Others" category. You can transform an existing column or use the VisibilityLimit function with a sorted table.
English (Canada), English (Ireland), Spanish (Mexico) and Chinese (Traditional) are now supported workbook locales. This includes language, date format, number format, and currency. You can preview a workbook in
en-ca, en-ie, es-mx, or zh-tw.
After copying and pasting a workbook or data model element with one or more columns that use metrics, those columns display correctly.
You can now successfully tag and swap the sources of a workbook version that uses a data model with data from multiple connections.
When the signature of a stored procedure used in a stored procedure action is changed, the action now validates that the signature is the same and uses the new signature if possible.
When viewing a workbook lineage in an embed, the Shared with me link now launches the embed modal instead of the native Sigma modal.
When you disable automatic user creation for embeds, you can now manage embed users in the Administration portal.
When Sigma encounters errors during a data source swap involving custom SQL and input tables, Sigma now show the error messages at the bottom of the page.
User-friendly names for cloud platforms in the Administration portal
Friendly names are now used for cloud platforms in the Administration portal. To view your cloud platform, go to Administration > Account > General Settings, then locate the Site section. The Cloud field identifies the platform hosting your organization.
API request URLs now visible in the Administration portal
You can now view the base URL required for authenticating to the Sigma REST API in the Administration portal. Go to Administration > Developer Access. For more information, see Get started with the Sigma REST API.
API
New option for Create API credentials endpoint
The Create API credentials (POST /v2/credentials) endpoint includes a new scopes option to allow you to create embed credentials.
Set scopes to embed to create credentials for embedding Sigma.
Set scopes to api to create credentials for interacting with the Sigma REST API.
New option for the Create a member API endpoint
When creating a member using the API, choose whether to send an invitation email to a non-embed user. The Create a member (POST /v2/members) endpoint now includes the sendInvite query parameter.
Data modeling
Improved management of data model source visibility
Instead of managing the visibility of an element in a data model with a on the element, now you manage the visibility of a table as a source from the Modeling tab.
For data elements that display "No Data" when no data is returned, you can now customize the text that is shown. For more details, see Customize no data text.
Highlight non-breaking space characters in SQL element
The Custom SQL element now highlights non-breaking space ( ) characters that might be present in SQL queries. Non-breaking space characters can prevent SQL statements from running successfully.
Bug fixes
Automatic team assignments based on the SAML userGroups attribute now works for all teams, public or private. Previously, it only worked for public teams or users with the Admin userRole.
When a JWT embed URL is missing a nonce value, the emitted error is now more specific.
For a properly configured stored procedure action, running the action no longer results in intermittent "Invalid stored procedure" errors, such as "TypeError: Cannot read properties of undefined (reading 'parameters')".
Element menus in workbook templates no longer include the option to create warehouse views, as warehouse views aren’t supported for template elements.
Previously, Sigma prevented editing SQL in a SQL element below a certain size. Now, attempts to edit SQL in a small SQL element opens the maximized view of the element with the SQL tab active so that you can edit it without changing the workbook layout. After editing, you can minimize the view to return to the full workbook layout.
Column order enforced when dynamically moving columns
When you use a multi-select list control to dynamically move columns into and out of groupings or properties (via the Move columns action), the column order in the table now matches the order of the values defined in the control.
Formula support in image URL
When configuring an image element, you can enter dynamic text in the Image URL field to source the URL from a formula. For example, Lookup([Team/Profile Image URL], CurrentUserEmail(), [Team/Email]) references the Profile Image URL column in an existing Teams table to dynamically display profile images based on the current user.
Bug fixes
Sigma now uses improved logic for presenting the initial workbook page from a URL with the :nodeId parameter when the page includes conditional visibility rules. If the user cannot view the page, the first visible page is shown.
Sigma did not support workbook deletion for JWT-signed secure embeds. Now a user can delete a workbook from the menu and get redirected to an error page with the document browser to navigate to another workbook.
For JWT-signed embeds, errors are now sent when the JWT token cannot be parsed and when the current user is not invited to the workbook they are attempting to access.
Users now see an alert message 20 minutes before their connection-level OAuth session expires, prompting them to re-sign into the connection. For more information on OAuth, see Configure OAuth.
AI
Warehouse AI model integration (Beta)
If your organization is connected to Snowflake or Databricks, you can use warehouse-hosted AI models to power Sigma AI features. For information about selecting your data platform as your organization's AI provider, see Configure warehouse AI model integration.
Embeds
New outbound event emitted for deleted workbooks
When a workbook is successfully deleted from the embed menu, an outbound workbook:ondelete event is emitted.
The connection_oauth_tokens JWT claim is now available. This is an optional claim that allows you to pass OAuth tokens through JWT-signed URLs for connection-level OAuth. For more information, see JWT claims in Create an embed API with JSON web tokens.
Bug fixes
Archived connections no longer cause unexpected errors in shared templates.
Changing organization level authentication from OAuth to another authentication method no longer causes independent OAuth configuration options to disappear in Administration.
The More menu for tables has been updated to remove a nonfunctional Make owner option.
When using connection-level OAuth, your email is no longer checked to see if it matches the email used for signing in to Sigma.
Previously, in Snowflake OAuth connections with service accounts enabled, if the serviceAccountWarehouse was not set in Sigma, it would be evaluated as undetermined (resulting in an error). Now, if the warehouse is set by a user attribute, the service account will use the default value of the user attribute.
When pressing Tab to navigate between elements in a container, the navigation order matches the position of the elements within the container.
When a container is selected, pressing Tab correctly changes selection from the container to the top-left-most element in the container.
When the top-left-most element in a container is selected, pressing Shift + Tab selects the parent container.
When selecting an element in a workbook to navigate to with the Navigate in this workbook action, the list of elements for a page matches the order of the elements on the page.
Passing multiple SAML userRole values is now supported
When configuring SAML, it is now possible to pass in multiple userRole values. The first valid account type in the list of userRole values will be assigned. See Configure your IdP in Set up single sign-on with SAML.
Workbook features
Transpose a table (Beta)
Transposing a table is now supported from rows to columns or columns to rows. This feature allows you to pivot or unpivot data according to your use case.
Limit the number of values displayed in a grouped table, pivot table, or chart, and group the remaining values in an "Others" category. You can transform an existing column or use the VisibilityLimit function with a sorted table.
Custom totals and subtotals for pivot tables and grouped tables (GA)
In a pivot table or grouped table, you can change the way that totals and subtotals are calculated by choosing to change the aggregate used for a subtotal, or modifying the formula for a grand total or subtotal directly.
With this update, the default names of subtotals and totals update to Column Name total for subtotals or Grand total for totals. You can change the label of any subtotal or grand total.
After deactivating a SCIM user, the folder created to contain the deactivated user's documents no longer includes a UUID and matches the behavior described in Deactivated user documents.
When revoking access to a connection, database or catalog, schema, table, or stored procedure in Sigma, you can now only revoke access from the level to which the access was granted.
When a user has inherited access to a document from a version-tagged folder, the version tag is now shown in the Share Workbook or Share Data Model modal.
When sharing a workbook, version tags now appear for all access levels as expected.
When a user has access to specific version tagged documents in a folder, you can now grant access to all versions of documents in the Share Folder modal.
Allow users with View license to ask natural language queries with Ask Sigma
The Use Ask Sigma permission can now be enabled for users with the View license (or Lite license). See Account type and license overview. No existing account types were changed. To enable Ask Sigma for users who did not previously have access, update their account types to add the permission.
To continue analysis in a workbook, a user's account type must also have the Create, edit, and publish workbooks permission enabled.
Allow users with View license to browse connections
The View connections permission can now be enabled for users with the View license (or Lite license). See Account type and license overview.
Users with this permission enabled on their account type can view database or catalog, schema, or table names that they have access to. This permission does not grant access to data in connections. See Manage access to data and connections.
New permission for calling stored procedure actions
Manage which users can call stored procedure actions from a workbook with the Call stored procedure actions permission. The permission requires an Act or Essentials license. For more details, see Account type and license overview.
Input table support on BigQuery connections (Beta)
Input tables are now compatible with BigQuery connections. The dynamic workbook elements support structured data entry, allowing you to integrate new data points into your analysis and augment existing data from your data platform.
For more information about input tables and how to use them, see the following documentation:
Use the Update row and Delete row actions to modify input tables. Update row allows user interaction to update values in an existing row, while Delete row removes an entire row. These actions are designed to support form functionality but can be used in other ways to accommodate different data app use cases.
Use multi-select columns in input tables to enable users to add one or more discrete values to a single cell. You can create and manage a predefined list of custom values or choose an existing data source or element in the workbook to populate the list. Values are displayed as individual pills and can be assigned different colors for visual differentiation and clarity.
Add custom context menu items in tables, pivot tables, input tables, and charts to provide clear, discoverable triggers for actions relevant to selected cells and data points. You can add standalone menu items or create nested submenus that execute any action effect, including calling stored procedures, generating iframe events, and opening modals.
Data models provide a semantic layer for your data, letting you organize and store data in a structured governed way without modifying raw data. You can create and manage reusable data elements with visual semantic modeling in an entity relationship diagram, empowering business users to independently model and explore data.
Add relationships between tables in a data model to enable business users to work with related data without performing ad hoc joins. A relationship defines the join logic for Sigma to use to join the tables, making the columns from both tables available to the source table for analysis and exploration on demand. When a user analyzes the source table in a workbook and adds a related column, Sigma performs the join.
Relationships between data model tables only support many-to-one or one-to-one joins, and are not automatically created between tables from a connected data source, even if the table has primary and foreign keys defined.
Newly available functionality:
Use related columns in data models
Add relationships to elements disabled as a source
Adding metrics to data models is now generally available. Metrics are dynamic and reusable calculations that are specific to a data source. As such, metrics usually reference specific columns. Create a metric to provide reliable and efficient aggregate calculations, abstracting complex formulas away from business users.
When defining a metric on a data model, you can reference other metrics in your formula. Metrics propagate downstream, so a metric defined on one data model is also available to any data elements that use that data model as a source.
Applying column-level security (CLS) to elements in data models is now generally available. Column-level security restricts access to column-level data, ensuring that sensitive and confidential information is secure and accessible only to authorized users. Configure CLS in a data model element for specific users or teams.
Updated behavior when targeting a data model source parameter from a workbook control
When passing values from a workbook control to a data model, you no longer need to target the source parameter with a specific data model table element. Instead, you can associate a control element in the workbook with a control element in the data model itself.
Existing workbook control elements that target data model elements with source parameters continue to work.
When you publish a data model with changes that could break downstream elements, you are now prompted to map changed columns to prevent errors such as Unknown column [columnID] or Column [ColumnID] does not exist.
When chatting with a Sigma support engineer, you can now click and drag the handle on the top left corner of the live chat window to move it to a more convenient location on your screen. This helps you more easily interact with Sigma Support and access key parts of your screen at the same time.
Add shortcuts to documents (GA)
If you want to save links to documents in more than one location, you can add a shortcut. Use shortcuts to make specific data sources easier to find in the source picker, or to organize documents to make key workbooks and data models easier to access.
When working with data elements in data models and workbooks you can organize columns into folders, letting you nest columns into relevant groups. Folders that you create in a data model or parent element are available to downstream elements, like a data element that uses a data model as a data source, or a child element.
Use popovers to display information in containers anchored to specific button elements. Popovers allow you to present relevant content (tables, charts, controls, etc.) only when needed, creating a more efficient and simplified workbook interface.
More precise formatting of grand totals and subtotals
You can now format the grand totals and subtotals of a pivot table or grouped table separately from other values in the column. For example, format the grand total row of a pivot table to display numbers in SI units, while the values columns display whole numbers.
When adding date data in an input table, the format of the data now respects the locale of the Sigma organization. For example, if your Sigma organization uses a locale of English (Great Britain) and you paste a date value of 10.05.2025 into an input table, the date correctly appears as May 10, 2025.
When adding a version tag to a data model and swapping sources from one connection to another in cases where the table is available at a different path in each connection, the data sources no longer fail to swap with the error "Failed to find the table in connection".
Users in an embed can no longer open the source of a data model.
SAML configuration values now available in Administration portal
When setting up single sign-on with SAML, you can now copy and paste your SAML configuration values (e.g. prefix, RelayState) from the Administration portal. Go to Administration > Authentication > Edit, and your configuration values will be available under Authentication Method & Options. Your prefix will already be included in any relevant fields.
If users attempt to run a query with OAuth credentials that do not exist, they are now shown an improved error message.
When sharing a template containing input tables across organizations, the input table data entry permissions in the shared template now matches what was defined in the source document.
