This QuickStart lists all the new and public beta features released, as well as bugs fixed for the year 2023.
It is summary in nature, and you should always refer to the specific Sigma documentation links provided for more information.
Although features may carry a "Beta" tag, they may be released by now.
All other features are considered released (GA or generally available).
New connection schema and dimension tables:
The Sigma Audit Logs connection now features a SIGMA_SHARED
schema, with dimension tables containing information about your Sigma organization's resources, objects, assets, etc.
The dimension tables can be joined with the AUDIT_LOGS table to add context to audit log events.
For example, join AUDIT_LOGS with the DOCUMENTS table to add document attributes (e.g., creation date, document path, and archive status) to event entries related to user interactions with workbooks, datasets, etc.
List of New Dimension tables:
SIGMA_SHARED
schema additionsThe SIGMA_SHARED
schema in the Sigma Audit Logs connection now features the following dimension tables containing information about your organization:
TEAM_MEMBERS:
Organization team member attributes
DOCUMENT_ELEMENTS:
Workbook element and page attributes
These new tables can be joined with the AUDIT_LOGS table to add context to audit log events.
Documentation on Audit Logging is here:
There is a QuickStart on using Audit Logs here:
In order to improve the admin experience and provide admin functionality at scale, numerous actions can now be performed in bulk.
User Management:
Team Management:
User Attributes and Exports:
Column-Level Security provides granular control over data access allowing you the flexibility to restrict or grant access to column-level data. This ensures that the security of sensitive or confidential information is only accessible to authorized users. Column-Level Security (CLS) is managed through team membership and user attributes.
Column-Level Security provides the following benefits:
You can now connect Sigma directly to your data in a MySQL data warehouse. Learn how to create and manage the connection in Connect to MySQL.
Sigma Admins can designate a workbook to use as a custom homepage for an organization or team. The first page of the workbook becomes the custom homepage.
A custom homepage functions as a landing page for its viewers.
Think of this like an embedded Sigma workbook on your landing page, inside Sigma!
An organization can have multiple custom homepages, assigned to different teams.
Use a custom homepage to provided targeted content, educate, link to other content and more.
For example, when you are first rolling out Sigma to your users, you may want everyone to see some training content or other important information. A custom homepage is a great way to do this and can be changed later, as your needs evolve.
For example, let's say you want all users to see Sigma's foundational QuickStarts on the homepage.
First, we need to create a new Workbook in Sigma, with buttons that link to each QuickStart we want.
That workbook might look something like this:
In this workbook, each blue button links to a different workbook, and each of those has the Embed
element on the page.
The embed element is configured to load the desired QuickStart. For example, for the Getting Started
button, the configuration looks like this:
The other workbook that is being loaded for the Page
looks like this (in edit mode).
There is one additional workbook for each button.
Last, we need to tell Sigma which users we want to assign this new custom home page to.
Navigate to Administration
> Account
and click the Enable
button for Custom Home Pages
:
In this example, we will just assign it to All members of your Sigma organization
:
When a user clicks on one of the buttons, they stay inside Sigma, but can review external content. In this case, the external content is a Sigma QuickStart:
This new permission provides the option to restrict or grant folder creation permissions. To configure this go to Administration
> Account Types
> Create New Account Type
.
To learn how to configure federated access in Sigma, refer to this QuickStart.
Sigma provides full native support for the JSON data type in BigQuery connections. This enables you to process and analyze semi-structured data effectively. For details on how to use JSON, see Google documentation on Working with JSON data in GoogleSQL.
Admins can now remove multiple members of a team using a bulk action. To remove team members in bulk, go to your Administration
> Teams
> select a team > select members to remove > and click the Remove
from team button.
For more information about managing teams, see Manage Teams.
Admins can now initiate a password reset for multiple users with a bulk action setting. The selected users receive an email alerting them to reset their password.
Prior to this feature, administrators had to create a Sigma Team in order to assign specific attributes to users, who needed to be a member of this team.
Sigma now supports assigning specific user attribute values directly to users.
For example, the user Finance TestUser
has the Attribute Region
set to the value East
. This attribute will be used to filter data automatically, to the "East" region.
Administrators can now impersonate users from the Team page in the Admin portal.
Previously, admins could only impersonate a user from the People page.
The Impersonate Users feature provides admins with ability to impersonate a user and view, edit, access Sigma resources based on the user's account type.
To stop impersonation:
To learn more about user impersonation click here.
Workbook warehouse views are now generally available (GA).
Warehouse views are virtual tables in Snowflake that you can query using Sigma or any other application in your data ecosystem.
Instead of storing data in a Snowflake database table, a view saves a SQL statement that expresses specific query logic defined by the data element or input table in Sigma.
Warehouse views can be very useful, depending on the use case:
Review the FAQ for common questions.
The warehouse view is created and you are able to check the status See Warehouse view status
You are able to access all of the available warehouse views under Administration
:
For more information, see Create and manage workbook warehouse views and Review warehouse view details
When an embed user creates an input table, Sigma automatically selects the connection and write schema if the user only has access to a single connection with one schema.
This update bypasses the Select a connection
requirement when applicable, providing a more simple and streamlined user workflow.
POST /v2/teams
API no longer limits the number of team members returned.
The /v2/connections
endpoint now returns the following connection metadata fields:
{
"account": "string",
"warehouse": "string",
"user": "string",
"role": "string",
"timeout": {
"default": 0,
"worksheet": 0,
"dashboard": 0,
"download": 0
},
"poolSizes": {
"adhocPoolSize": 0,
"catalogPoolSize": 0,
"resultPoolSize": 0,
"schedulePoolSize": 0
},
"writeAccess": boolean,
"friendlyName": boolean,
"writeDatabase": "string",
"writeSchema": "string",
"materializationWarehouse": "string"
}
Returns a paginated list of team members and can be used to identify team admins, based on a unique identifier (teamId)
GET /v2/teams/{teamId}/members
curl -X GET "https://api.sigmacomputing.com/v2/teams//members" \
-H "accept: application/json" \
1: The GET /v2/workbooks/{workbookId}/embeds
method now includes public
in the response to indicate if the embed is an application or public workbook.
2: The GET /v2/workbooks/{workbookId}/controls
method returns the name and value-type for all Sigma Controls
present in the specified workbook:
3: A new parameter, userKind
, is now available for the Update a Member in Your Organization
endpoint. This parameter defines the type of user.
The three possible values are guest
, internal
, or embed
.
4: The /v2/workbooks/{workbookId}/queries endpoint now returns elementName.
5: The /v2/workbooks/{workbookId}/pages/{pageId}/elements endpoint now returns name and columns.
6: The /v2/workbooks/{workbookId}/pages/{pageId}/elements now returns visualization Type.
You can now use the PATCH /v2/members/{memberId}
endpoint to reassign specific documents when you archive a member. In the request body, set isArchived`` to
true, and set
newOwnerId` to the member who will receive the documents from the archived member.
Workbooks enable you to manage specific tasks within your system. When you create a new workbook using the POST /v2/workbooks
endpoint, you can assign an owner by passing the ownerId
in the request body.
If you don't include this, the owner is the user whose token was used to call the API.
A new query parameter is also available for this endpoint: versionTagId
. For more information on using Sigma version tagging, click here
Bug releases are broken down by week for specificity.
No release notes during this period.
1 Sigma now verifies user account type permissions and only sends version tag email requests to users granted the Create
, edit
, and publish
workbooks and Apply tag
permissions.
2 Viewer-licensed users (who cannot edit workbooks or apply tags) no longer receive the requests.
3 Initial clicks on list control elements in embedded workbooks no longer cause the iframe display to jump to the top of the workbook.
4 The PDF export feature now executes successfully in user-backed embeds.
5 Administrators can now view all scheduled exports for published and tagged versions at the workbook level. Schedule views are no longer impacted by version permissions granted to users who create the schedules.
6 When a user configures an export for a tagged workbook version and doesn't have access to the source workbook, the document version or bookmark field in the Send Now
or Schedule Exports
modal now defaults to the current version. The field no longer defaults to "Invalid selection."
7 Use of the API to generate a public embed for workbook elements no longer results in a broken link.
8 The embed menu now updates the workbook owner when ownership is reassigned.
9 Resolved an issue that prevented users from deleting hidden pages in workbooks.
10 When swapping the source of a tagged workbook version, the Sources
of tagged workbook dropdown now excludes connections with a different Cloud Data Warehouse or Database Management System provider as the initial source.
allows run-time swapping of the Snowflake Warehouse and Role for a Sigma connection. There are ways to leverage this using one or both Warehouse and/or Role along with different methods to restrict data access in Snowflake itself.
Please refer to this QuickStart on how to implement dynamic role switching with Snowflake using User Attributes defined in Sigma, with an Application Embed.
To learn more about dynamic role switching with Snowflake, click here.
Admins can now convert Embed users to Standard, or vice versa. If you convert an Embed user to Standard, you must define their Account Type.
The following optional user-backed embed parameters are now available:
The :show_footer
embed parameter is now case-insensitive, for example: allow :show_footer=False
.
For more information, see Embed Sandbox.
Sigma no longer automatically adds colons (:) to separate parameters in the embed sandbox URL.
For example, if you enter param1=value1 param2=value2
in the Other Parameters
field, the URL is appended with ?param1=value1&
param2=value2
Previously, the URL would be appended with ?:param1=value1&:param2=value2
.
We have added three new parameters to the embedding API.
You can review all the available parameters here.
use_user_name displays the workbook creator's name (instead of email) in embed menus and system-generated emails.
The first_name and last_name (have to use both) parameters replace the default name ("Embed User") that is shown in Administrative and other interfaces.
If both first_name
and last_name
parameters are absent, the current user keeps their current name (or, if a new user is created, their first name will be set to Embed, last name to User)
The parameter, disable_mobile_view for user-backed embeds is available. If this parameter is set to yes, workbooks won't automatically resize to the mobile layout.
Elements that fail to load in embedded workbooks now trigger a postMessage event that includes the element ID, message, and API error code.
{ type: ‘workbook:chart:error'; nodeId: string; message: string | undefined; code: string; }
Where nodeId refers to the id of the element that failed to load in the embedded workbook, and the message and error code provide more info as to why.
The errorCode will be one of the API error codes:
"EEXIST" | "EPERM" | "ENOENT" | "EACCES" | "EINVAL" | "ESTALE" | "ETIMEDOUT" | "EAGAIN" | "EFBIG" | "NETWORK" | "UNKNOWN"
We added the following optional parameters for user-backed embeds.
For more information about using embed parameters with Sigma, please refer to this QuickStart.
Version Tagging is now generally available. For more information, see Version Tagging
Summary:
Version tagging allows you to employ a software development cycle to control workbook versions using tags. For example, orgs can have a development, staging, and production version of a workbook and migrate changes as needed. This allows you to control which workbook versions are viewable by your users.
When you create a tag and assign it to a workbook, you essentially freeze the state of that workbook. The process of tagging a workbook creates a duplicate that can be shared with other stakeholders and users.
For example, you can create a Production tag and assign it to a workbook that's used by embed users, guests, or other Sigma end users. Moreover, you can tag additional versions of the same workbook such as Development or Staging. These versions can be used by different stakeholders in your org for review purposes. Once reviewed, you can migrate this copy to Production for your users.
One of the benefits of this solution is your org can modify a Development workbook without affecting the experience of your customers who use the Production version. Once you complete your developmental changes, you can easily update the Production version of the workbook.
If you are interested in Version Tagging in an embedded scenario, please refer to this QuickStart.
Admins can now use version tags with embeds, in the embed sandbox.
This allows you to test before using them in your production environment.
For example:
Sigma provides access and capabilities based on a cumulative set of permissions inherited or granted at different levels of the data architecture (connection, schema, database table) and organizational structure (organization, team, user).
We have added an additional permission level to the list of permissions that already exist.
The Can write only
permission restricts access to data while enabling users to create input tables and CSV upload that write data to the connection's write-back destination. This permission type is ideal for enabling input tables and CSV uploads in embedded workbooks with restricted data access.
For more information about the new permission type, see Data permissions overview.
A segmented control provides a "linear strip" of two or more named segments.
Each segment acts exactly like a radio button, selecting the matches and excluding other data records.
When you have to make selections from a long list of values, segmented controls can be a better option because they provide a smaller subset of relevant values, a more economical dashboard layout, and a nicer overall experience for viewers.
There are two types of segmented controls: Based on a manually-entered list. You must have values that select data on the target of the control.
Based on a column in the data source or workbook element. These controls can have a maximum of 5 distinct values, sorted on record count or alphabetically.
List filters and controls now support input copied from tabular formats!
You are now able to copy multiple cell values from Excel, Google Sheets, Sigma tables, etc., and paste them in the Search field.
The input is automatically comma-delimited, enabling you to filter it as multiple distinct values.
This feature will save users lots of time when the need to search for a long list of items is required.
Suppose we want to search a 4M row table for just a list of target Order Numbers
. Instead of using the order number filter, and picking them one at a time (really impractical), you can just paste the list into the search field and you are done!. VERY COOL time saver:
You can use the new Create list
from preset option to easily create a drill down control for a visualization that has year, month, and day categories, without manually creating them.
ArraySlice takes any array and extracts a subarray given starting location/index and desired length. The length is optional field here. So if this is absent, then the entire array starting at start location will be returned.
It can take dynamic values, meaning you can choose different starting indices and different lengths for each row.
If you specify starting location negative then it will consider it from the back of the array. So if you want to extract last element, just type ArraySlice([array], -1)
ArrayDistinct - Returns the array without duplicate values.
To learn more about array functions, click here
Use custom functions in your Sigma practice to encode business logic centrally, instead of repeating it, or have users create their own (potentially with errors). Encapsulate complex calculations that are common business use cases for easier use, and to expose your proprietary warehouse functions and make them more consumable.
Custom functions are part of Sigma Administration
, and under Account
> Custom Functions
:
For a simple example, let's say we want to create a standard way to calculate margin that all Sigma's users (who have the appropriate rights) can use.
We simply Add
a new Custom Function
and define it as:
Setting the slide control to On
(shown in blue) for Include function in formula bar suggestions
will give users the same functionality when creating new calculations, as if this new custom function was Sigma standard.
The user can simply start typing the function name in the formula bar as usual (in this case, the name is PlugsMargin
).
Sigma prompts the user to identify which column should be used for each required value in the custom function, but the user does not need to know or worry about the details of the underlying calculation; it just works. The column names selected do not even have to have matching names.
The user is made aware that this is a custom function by the bubble with the title "Custom" in the function help, as shown above.
Sigma has added a new function that makes it easy to compare one column's value with another when working with dates.
For example, let's assume we have a table that includes an Annual Gross Profit
column containing the gross profit for each year between 2019 and 2023.
We can use the DateLookback
function to return the previous year's gross profit and facilitate a period-over-period analysis.
We simply use this formula in a new column:
DateLookback([Annual Gross Profit], [Year], 1, "year")
The formula above determines a one-year offset from the period in the Year
column, then references the offset period and returns the corresponding value from the Annual Gross Profit column.
The results look like this:
The DateLookBack
> Period
can be and of these values:
"year", "quarter", "month", "week", "day", "hour", "minute", or "second"
Sigma has added support (based on customer feedback) for a few specific functions that are critical for financial calculations. They include:
CAGR - Returns the compound annual growth rate of an investment.
Effect - Returns the effective annual interest rate.
FV - Returns the future value of an investment.
Nominal - Returns the nominal annual interest rate.
NPer - Returns the number of periods for a loan or investment based on known amount, interest rate, and periodic payment amount.
Pmt - Returns the periodic payment for a loan based on the amount, number of periods, and constant interest rate.
PV - Returns the present value of a loan or an investment, when using constant and regular periodic payments.
XNPV - Returns the net present value of an investment for payments or incomes at irregular intervals.
Sigma added support for the Geography data type, and the corresponding set of
Area - Calculates the area of a geography, in specified units.
Centroid - Calculates the geographic center of a geography.
Distance - Calculates the minimum distance between two geographies, in specified units.
Intersects - Determines if one geography intersects another geography.
Latitude - Returns the latitude component of a point.
Longitude - Returns the longitude component of a point.
Geography - Converts data in GeoJSON or WKT formats into the Geography data type.
Json - Converts the Geography data type into GeoJSON format.
MakePoint - Constructs a point from latitude and longitude data.
MakeLine - Constructs a line from a series of points and line segments.
Perimeter - Calculates the perimeter of a geography, in specified units.
Text - Converts the Geography data type into WKT format.
Within - Determines if one geography is fully within another geography.
Metrics are custom aggregate calculations that you can reuse across workbook data elements that share the same data source: a dataset or a connection table
We have added search functionality to find reusable metrics saved to datasets and connection tables, to save your valuable time.
For more information, see Using Metrics.
To complement the Pmt (payment) function that calculates the size of a loan repayment with a constant interest rate and equal installments, Sigma added two more financial functions:
You can also use two new Passthrough functions to support the Geography data type:
AggGeography - Calls a warehouse aggregate function that returns a Logical data type; aggregation version of CallGeography.
CallGeography - Calls a warehouse function that returns a Geography data type.
We have added a new RegExp text match filter to enable you to filter text columns, based on specified patterns.
These included text strings, character classes, ranges, etc.
These filters support the RegExp syntax and behavior of the connected CDW or DBMS.
You can either match or not match:
Matches RegExp: Includes values that match one or more specified patterns.
Does not match RegExp: Excludes values that match one or more specified patterns.
For example, if you want to only see items in the Product Line
that contain the text TV
or 4K
:
The Repeat function returns the results of repeating a string a specified number of times.
For example, adding these five new columns:
Repeat([Product Type],0)
Repeat([Product Type],1)
Repeat([Product Type],2)
Repeat([Product Type],3)
Repeat([Product Type],-1)
...will return the following values for the Product Type column:
Repeat is one of the Text functions supported by Sigma.
The VariancePop function calculates population variance, which determines the spread of distribution or degree to which the column or grouped values deviate from the mean.
The addition of this function complements the existing Variance function, which estimates sample variance. For more information about these functions and when to use each, see VariancePop and Variance.
For example, assuming a table contains the average temperature recorded for each month in 2021 and 2022, the following formula will calculate the temperature variance for each year (years being grouped):
VariancePop([Avg monthly temp])
Input tables now support Calculation Columns
.
Calculation columns allow you to use formulas to populate input table column data.
To utilize a calculation column, open the element menu, select Add new column
> Calculation
, then enter a formula in the formula bar.
Input tables now support a checkbox column type in place of the logical type.
To update these to the Checkbox type, open the column menu
and select Change column type
> Checkbox.
True
values convert to selected checkboxes, while False
values convert to cleared checkboxes.
Checkboxes enable additional workflow capabilities by simply capturing a "yes/no" response from a Sigma user. For example, record approvals, validations and enabling data triggers based on the user's response.
We have added the ability to apply rules based on specified conditions to format single colors, color scales, or data bars in input table columns.
Conditional formatting is accessed in the Element
format panel, or open a column menu
and select Conditional formatting
:
In this example, FY23Forecasts
cell is red when the At Risk
checkbox in the corresponding cell is checked on:
You may now apply conditional formatting to Input Tables in a similar fashion as you would typical tables, using conditional formatting rules.
Input tables (and individual columns) now support autofill, which will save users time in certain use cases.
Select a cell or range of cells, then drag the fill handle (blue box in the lower right corner of the selection) to highlight adjacent cells you want to populate.
Sigma automatically fills the highlighted cell or range with data based on the selected values and patterns.
For text and checkbox columns, Sigma repeats the selected cell values.
For number and date columns, Sigma projects values to continue a patterned sequence (like consecutive numbers or incremental dates).
If no pattern is detected, it repeats the selected cell values.
Input tables are now compatible with Databricks connections. These dynamic workbook elements support structured data entry that allows you to integrate new data points into your analysis and augment existing data from Snowflake or Databricks.
To review how Input Tables solves several common use cases, check out this QuickStart
You are now able to duplicate columns in input table elements the same way you can in table and pivot table elements.
Click the caret () in the column header to open the column menu, then select Duplicate column.
Use the fill range
keyboard shortcut to overwrite selected cells with the value in the first (top-left) cell of the range. Select a range and apply the applicable keyboard shortcut based on your operating system:
For macOS: ⌘ + return
For Windows: ctrl + enter
You can now add hyperlinks to Input Table columns.
In the column menu, select Transform
> Set link
, then choose a column as the link source or create URLs with a custom formula:
Let's say that we have a table called that has the name of an image in one column, a picture and the URL to that image in another.
We prefer not to show the ugly URLs but do want the user to be able to click on the Image Name
to open the picture in a new browser tab, full size.
We just have to transform the Image Name
column to link
and then link the Image URL
column to it:
Now the Image Name
column is a hyperlink and we can just hide the Image URL column
:
Sigma supports multiple users working on content at the same time. This functionality is great for collaboration and efficiency but in the case of input tables, can create a problem too when saves are happening at nearly the same time.
For example, if one user is editing an input table in a workbook's published version (in View
or Explore
mode) and another user concurrently publishes an updated version of that workbook, what happens to the input table data that is "in-flight"?
We have addressed this edge use case to prevent input table data loss without impacting collaboration.
When you click Save
in the input table element, Sigma informs the user that there has been an update by another user.Sigma provides the option to load and apply your changes to the latest workbook version, so that nothing is lost.
Granted, this is an edge use-case, but we have taken action to address it so that no data is potentially lost.
In the workbook lineage, input table summary cards now include a Connection
field that identifies the connection Sigma uses to write the input table data to the CDW/DBMS. This makes it easier to determine the input table's destination for the added data.
Input tables support AI-generated columns that allow you to augment your data and derive valuable insights for improved data-driven analysis and decision-making.
Sigma helps you accurately convey your data requirements through structured AI prompts that create the following types of AI-generated columns:
Once enabled, OpenAI functionality (as described above) is made available in Input Tables:
AI-enhanced input tables utilize the OpenAI integration, which allows Sigma to leverage OpenAI language models (e.g., GPT-3.5 and GPT-4 models that power ChatGPT).
Organizations can now swap the connection source when applying version tags to workbooks containing input tables.
Connection swapping allows you to move the workbook through the development process.
We have updated the existing "Embedding 4: Application Row Level Security" QuickStart for a "superuser" use case.
In many cases, customers have one (or more) users who will need to see all the data ("superuser"), while others only see the data permitted. We demonstrate how to do this in the Sigma UI as well as with custom SQL.
Allowing For "Superuser" Access
Implementing Row Level Security:
This QuickStart provides insight into the different methods available for content creators to limit data access to a user, based on an implementation of row level security (RLS) in Sigma.
How to: Federate Access with Sigma Embedding
How to: Responsive iframes with Sigma
How To: Leverage Parameters and User-Attributes with Sigma Embedding
Fundamentals 6: Administration
You can review all the available parameters here.
In this QuickStart we discuss and demonstrate how to extend Sigma's functionality by crating their own plugins.
There is a QuickStart on using Audit Logs here:
In this QuickStart, we discuss column level security and demonstrate how to apply it in Sigma, using the administrative user interface.
This QuickStart walks you through the process of connecting to a Sigma template, exploring security data, customizing the template for more interactivity, and connecting the template to your Snowflake environment's data (optional).
Secure Your Organization with Security Analytics Using Snowflake and Sigma
In this QuickStart, we will cover the recently added support for the key pair authentication method (public key + private key) for Snowflake connections.
We have added an additional QuickStart category called "Templates" that will cover how to take advantage of all the amazing Sigma templates that are included for free, for all Sigma customers.
The first QuickStart in this category is Snowflake Cost per Query Template Setup
This QuickStart provides instructions on how to set up Sigma's Snowflake Cost per Query template.
You can share Sigma templates with other organizations.
This functionality is particularly useful for customers who manage multiple Sigma organizations or need to create new Sigma organizations for their customers.
By allowing you to share templates across different organizations, it streamlines the process of providing consistent tools and resources, enhancing collaboration with your customers.
The templates tab is now split between External
and Internal
.
1: Dynamic text now reflects date or number formatting changes applied to the source column.
Cartesian charts (bar, line, area, scatter, box, and combo) now display the value axis and data labels with metric abbreviations or SI units when the Automatic format
option is applied by default or through manual selection.
For example, the value 10,000,000,000 is displayed as 10B. However, if a chart's source element uses a specific format (number, currency, financial, etc.), the Automatic
option inherits the source format.
Chart reference marks now support center-positioned labels. In the Element format
> Reference marks
section, click the Position
field and select Top center
or Bottom center
to display the label above or below the line.
### Chart color scales When you apply color scales to charts (in the `Element properties` > `Marks` > `Color tab`), the color menu now displays all options in various sequential and diverging color scale categories. The menu also offers new color scales, including color-blind accessible options.
The full palette:
Add descriptions to chart and table elements and display them as subtitles or tooltips.
Navigate to to Element format
> Title
and select the Show description
checkbox to enable and configure the element description:
For more information about element descriptions, see the Sigma Community post
Not a member of the Sigma Community? Sign up today!
You are now able to configure the visibility of chart legend headers.
In the Element format
> Legend
section, the new Show legend header
setting is enabled by default. Disable the setting to hide the header. When the element features two chart legends (i.e., color and size), the setting applies to both legend headers.
Illustrate geospatial objects on a map with the new Map - Geography visualization. Create a connection map to display spatial networks, correlations, and relationships, or build a choropleth map to identify variability and patterns across distinct geographic areas.
For example:
You can now add chart mark colors by category in the Map
- Region
and Map
- Geography
visualizations. Previously, these were not available in these map types.
This update brings parity in color configurations across all map types.
Data label placements, responsiveness, and overlapping for Radial charts (like donut and pie charts) have been improved to be much more readable.
Here are some examples:
Charts now include additional date filtering options in the data point menu, which can be accessed by right-clicking any data point.
Previously, the Keep only
and Exclude
filters allowed you to filter based on the single date value associated with a data point. Now, you can filter a date range that starts or ends with the data point's date value by selecting the On and after
or On and before
options:
Chart legends in Sigma now support double-click actions.
Before this update, a rapid double-click was interpreted as two separate inputs, selecting the value with the first click and deselecting it with the second. Now, Sigma treats a rapid double-click as a single input.
Charts that support references marks now allow you to duplicate existing reference lines or bands in the Element format
> Reference marks
section:
KPI chart elements are now generally available (GA).
These new elements add a new level of visual interactivity to your Sigma workbooks, enhancing user engagement and encouraging repeated visits.
For more information about KPI charts, see Build a KPI chart.
When the Comparison
property is configured in a KPI chart, both the comparison value and label are now hidden if the referenced benchmark or target value is null.
Sigma's KPI visualization element has replaced the Single Value visualization (SVV) option.
While you can no longer create new SVV elements, you can instead build KPI charts for improved single metric analyses.
For more information about the SVV deprecation and benefits of KPI charts, see the Sigma Community post.
Now supports for geography data is in WKT format (using Snowflake and BigQuery connections only) and variant data in GeoJSON format.
For more information, see Build a geography map.
Visualizations that support reference marks now include the ability to customize the reference mark label font size and color.
See Label font
options in Element formatting
> Reference marks
.
Sankey visualization elements are now available for general use (GA).
Sankey diagrams are typically used to assess the flow and change of data between stages in a process or system. Create simple Sankey diagrams to demonstrate data distribution, workflows, networks, etc., or build advanced multi-level diagrams to analyze complex data relationships and identify changes in variables across stages, categories, or periods.
When a scatter plot features two chart legends (i.e., color and size), you can now configure the visibility of each legend individually. Previously, only the Show legend setting was available, which allows you to show or hide both legends.
To configure individual legend visibility, go to Element format > Legend and enable or disable the Show color legend and Show size legend settings.
Customize data labels in Stacked 100% bar charts with new number formatting options.
In the Element format
> Data labels
section, the new Display value as a percent
setting is enabled by default. Disable the setting to display the labels as absolute values. When displaying percentages, you can use the percent decimal precision tool to increase or decrease decimal places.
You can now stretch your button elements to take up the entire width of the element.
This adjustment allows you to align your buttons regardless of the text length. It's a small but useful user interface improvement that some users will certainly appreciate.
Quickly highlight summarized totals by creating KPI visualizations directly from table summaries. To add a KPI, right-click a table summary to open the menu, then select Create KPI element.
Change the default display type (the value displayed when not interacting with the trend line) in the Value property:
You can now add reference lines and bands to the trend line in Element format
> Reference marks
.
Customize chart mark colors with more flexibility and control using the enhanced color selector. Select the and icons to toggle between the color palette—now featuring a Theme palette—and the new hex color picker.
Theme palette: provides a predefined set of colors based on the selected workbook theme (Workbook settings
> Workbook formatting
> Theme
).
Hex color picker allows you to enter a hex value or select the tint, tone, or shade of a specific hue.
Trellis charts (also known as small multiples or panel charts) have been enhanced with the following upgrades:
If you never used trellising to enhance a visualization, here is why you may find them useful.
KPI chart trend lines can now display y-axis grid lines and value labels.
To enable the y-axis, go to icon Element format
> Trend
and select the Show y-axis
checkbox.
For more information about formatting KPI chart trend lines, see Build a KPI chart.
Control the vertical alignment of content in text elements for improved text display.
Go to Element
properties and choose top
, center
, or bottom
alignment.
Without trellis:
This initial chart shows a basic view that compares total revenue per fiscal year from 2019 to 2023. The stacked bars differentiate revenue for each product family, providing an additional dimension to explore within and across each year.
With trellis:
By incorporating trellis columns to our example, we deepen the analysis. We can still analyze total revenue by fiscal year and product family, but the additional dimension allows us to compare these data points within and across smaller data subsets based on store region.
This is just a quick example, and there is much more we can do by using a trellis.
Users with Viewer
licenses can now request permission to explore workbooks by clicking Request explore access
in any workbook header.
Sigma administrators will receive the request. They can upgrade a user's license by reassigning them to an account type with the ‘Explore workbooks' permission enabled.
For example, this is what a user with Viewer
rights would see when a workbook is shared to them:
Users can now attach annotated screenshots to their comments in Sigma.
This allows Creators
and Admins
to capture an image of a workbook element, draw on it, and save it with a comment in the element's comments.
An annotated picture is worth a thousand words!
For example, let's say you notice that new customer orders are off this month.
You may want to share a comment, directed at a co-worker to investigate, so you open the comment sidebar:
Now you can select the Workbook Element you want to include, click the camera icon:
Select a color, annotate it, and add your comment:
This is a great way to communicate and collaborate inside Sigma.
Use the @
character to direct your comment to any valid Sigma user:
Badges are now applied to the source workbook and visible on all tagged versions of the workbook.
When a Viewer-licensed user clicks Create New
in the side panel, Sigma notifies them that the ability to create workbooks requires an account upgrade.
The user can send a request to organization admins, who can then upgrade the user's license by reassigning them to an account type with Create
, edit
, and publish
workbooks permission.
Sigma has added this very useful enhancement to make your workflows even faster.
When interacting with a data element or input table, we can now bulk relocate multiple columns using the Move to
action in the Columns
menu.
This functionality is available in the Element properties
panel and directly in the element.
In the animation below, take note that the order of the columns we select to move is maintained when they are moved to the start
using this new feature:
We want to make you are aware that as part of Sigma's plan to sunset the classic workbook layout and transition to exclusive use of the newer grid layout, the Revert to Classic Layout
option has been removed from Workbook
settings > Layout
settings.
The feature requires the following:
For more information about this update, see the Sigma Community post.
The element menu now features an Alert
action that opens the Schedule exports
modal and auto-populates select fields based on the corresponding data element or input table.
This allows users to quickly create a recurring export as a conditional alert to monitor a specific element.
For example, we may want to set an alert when a specific KPI falls below a threshold:
Selecting Alert when
from an elements menu will then allow the user to configure a schedule for delivery, using the existing schedule exports modal:
For more information, see Schedule a conditional export or alert.
Label configurations for control elements are now consolidated in the Element format
> Label
section with the following new options:
You can copy a page from one workbook to another, and from one page to another.
This feature will save users time by allowing easy reuse of existing, full pages. This eliminates the need to copy individual page elements, one at a time.
CSV upload is now available to Sigma organizations hosted on Microsoft Azure and Amazon Web Services Europe (AWS-EU).
For more information, see Upload CSVs.
Enhance visual appeal and table readability with pre-configured table styles with customizable configurations. Easily personalize the appearance of tables to seamlessly align with branding preferences and personal aesthetics.
Sigma provides style presets for out-of-the-box aesthetics and readability, and you can customize all style components independently for more personalized table designs.
For more information about table style options and how to customize them, see Customize table styles.
This is also covered in the QuickStart, Fundamentals 2: Working with Tables
The highlight functionality allows you to quickly identify rows with a common value. Right-click any cell containing the value you want to highlight, then click Highlight rows with {value}. Sigma automatically creates a conditional formatting rule that can be modified or deleted in the Element format panel.
Sigma now features a new default blue (#0059EB) across the product.
To preserve the appearance of existing workbooks, the color change has not been applied to custom workbook themes that utilized the previous default blue as the primary color.
You must manually update custom workbook themes to change the primary color to the new default blue.
Tags are a way to support continuous workbook development without affecting what outside audiences see.
We have added approval workflows into the existing version tagging functionality.
When a user doesn't have permission to use a protected tag, they can submit a request for an authorized user to review and apply the tag
Authorized users include all Admin users and any user who's granted permission to use the tag and also assigned to an account type with the Create
, edit
, and publish
workbooks permission enabled.
This action triggers the following improved review and approval workflow:
Grid Layout mobile view has been enhanced with the following updates:
Workbooks with Grid Layout (BETA) enabled now support PDF exports. A scheduled export PDF attachment can capture an individual element, a single workbook page, or the entire workbook, and you can choose between portrait or landscape orientation.
The highlight functionality allows you to quickly identify rows with a common value.
Right-click any cell containing the value you want to highlight, then click Highlight rows with {value}.
Sigma automatically creates a conditional formatting rule that can be modified or deleted in the Element format
panel.
This is a real time-saver.
We are introducing the concept of grouping data and calculations at various category levels, to keep track of the order between the coarsest and finest granularity of data.
This can be very useful and time-saving when there is a preferred way that data should be organized.
Some examples of hierarchies are:
For example, let's say we always prefer that pivot tables show data using "Store Region" and "Product Type".
We could start by creating a new Workbook, adding some data to a page called Data
:
We can add a hierarchy to this table by clicking on the +
and selecting Manage hierarchies
:
Now we click + New =hierarchy
and select the Store Region
and Product Type
columns. We gave it the name Product Hierarchy
and that is what we will refer to later.
When we create a new pivot table, we can directly add Product Hierarchy
as a Pivot Row
:
The rest of the pivot is configured as normally and the results are:
While this was a simple example, hierarchies can save you time and effort when there are many columns to choose from.
We added new keyboard shortcuts to help you work with input tables. See Keyboard shortcuts
> Input tables
.
You can now suspend the scheduled refresh of materializations if they are not accessed for an extended period of time.
For more information, see pause scheduled materializations.
To review the Materialization with Sigma QuickStart click here.
Users can now send workbook error reports with trace IDs that facilitate improved, targeted error investigations.
When you select multiple elements to delete, the confirmation modal now lists all dependencies. View names of elements to be deleted alongside the impacted elements that currently use them as sources.
When sorting a table column, you can force nulls to be ordered first or last regardless of the selected sort order (descending or ascending).
To customize null value sorting, right-click the column header and select Custom sort
, then select an option in the Nulls field:
Nulls field options:
You can now detach a control directly from its element without having to go to the control first.
Custom options for number formatting now includes "pp", for percentage point, a formatting option for values and value comparisons.
Sigma has added a guided workflow (think "wizard") for building period-over-period analyses. This new functionality provides a quick and convenient way to evaluate performance over time.
This allows users to generate dynamic period comparisons without entering complex custom formulas, then easily visualize the results to identify trends, patterns, and anomalies.
Users now have the ability to wrap the text in their pivot tables. By default, we truncate text that is too long to fit in a cell.
Users now have the option to expand the line height and see the entire content of the header or cell.
Scheduled exports now provide the option to select which tagged version of the workbook you want to include in the export.
Sigma has been making lots of improvements to the search result rankings over the last few months to make your search experience even better! Sometimes it's difficult to notice search improvements since they're typically released incrementally over time, but we want to let you know that we are constantly improving your Sigma experience.
In addition to personal bookmarks, you can now create shared bookmarks that are available to all users with access to the workbook.
Any time a workbook has controls where multiple different configurations are common, shared bookmarks can be used to make the user experience of navigating to those configurations easier.
For example, a sales workbook can have pre-filtered bookmarks for each sales region; a Quarterly Business Review workbook can have bookmarks set up for each quarter; a Product workbook can have bookmarks set up for each product area – the possibilities are endless.
Shared bookmarks are always available to everyone who has access to a Workbook.
The Multi-tab Excel export feature has been promoted to general availability (GA), for all Sigma customers.
You can now merge your Excel exports to be in a single file, with one element in each excel tab through Scheduled Exports
and Send Now
.
There are three ways to get multi-tab excel exports:
Users can also do a combination of these.
For example: if you have an attachment for an entire workbook, entire page, and four other elements, and I checked the `merge Excel`` option, three Excel files will be sent in the email, one for the workbook, one for the entire page, and one for the four combined elements.
Bookmarks now provide a notification when changes made (such as changing a filter's value) for the bookmark are no longer relevant in the workbook. In other words, someone changed the base workbook such that the bookmark is no longer accurate. A modal gives the option of updating or deleting the bookmark.
Background: Up until now, copying a workbook URL with some changes captured a snapshot in time. It was a static asset, decoupled from the published version.
This proved to be problematic because when the "original" workbook is updated, those changes are not propagated such that the bookmarked URLs users had made still referred to the old workbook.
For example, creators would publish a workbook, apply some filters, then share that link out to their users. Later, the creator would make updates to their workbook, and get complaints that their viewers that the still had an old draft since they were using a "stale" url.
Many customers thought something was broken in Sigma and this wasn't an intuitive experience.
Personal bookmarks address this issue by making the URL dynamic, and update with the original workbook. Explore URLs capture the individual edits on top of a published version.
In the case where you do just want a static snapshot of a workbook, you can still simply choose the Save As
option.
Recent Explores Often users make multiple explorations but do not save them, only to discover later that they wished the had. Recent explores address this but keeping track of all your unsaved explorations:
Tables can now display images in cells. When a column contains image URLs, you can render the images by selecting Transform
> Set image
in the column menu.
Image columns have some display options:
When you create a version tag, you can now select a permission level for users or teams: Public
or Protected
.
This allows org's greater control over who can publish updates to important workbooks that are exposed to stakeholders and embed customers.
Protected tags allow you to restrict access and select the users or teams that can apply a tag on a workbook.
The users must have Can edit permissions for the workbook. Public tags are unprotected, but the user must have Can edit permissions for the workbook as well.
We have added the ability to change the background color in text elements.
In the Element properties panel, choose to show or hide the text element background area.
Enabling the background creates a card display and adds padding around the text content for consistency with data elements and input tables.
You can then select a custom background color from the color palette or picker, or you can keep the default selection based on the workbook theme.
For example:
Users (the "requestor") without permission to use a protected tag can now submit a request to set that tag on a specific workbook version.
After the request is made, an email is sent to all the members (the "approvers") with explicit access to the protected tag.
After reviewing the workbook, the approver then can apply the requested tag to the workbook in question.
You are now able to filter a workbook's version history by applied
or requested
version tag. This results in a a more focused list of records.
Users can now create warehouse views from workbooks that use row level security.
When they do so, the warehouse view popup will contain a Data permissions
row displaying the user who configured the warehouse view, whose permissions are used to create the view.
Additionally, if any of the user's system functions values change, the view will automatically get updated.
Creating a new warehouse view:
Additional Resource Links
Blog
Community
Help Center
QuickStarts
Be sure to check out all the latest developments at Sigma's First Friday Feature page!