What's new in Sigma

Admin

Input table audit logging (GA)

Audit logs now record events and metadata related to input table activity. Admins can parse input table audit log data to understand the type of edit performed (e.g., create input table, add row, update row, delete row, etc.), who was responsible, and when the activity occurred. The metadata identifies the edited input table as well as the number of affected rows and columns, but it does not record the content of the edits.

For more information about input table audit log events and metadata, see the INPUT_TABLES event category in the Audit events reference tables.

Data apps

Option to view actions targeting selected element

Quickly view and navigate to elements with actions that target the selected element. In the action sequence menu, select Show actions targeting this element to view a list of trigger elements sorted by page, then select an element to open its action sequences.

For more information about actions, see Intro to actions.

Functions and calculations

UrlPart Function

You can now use the new UrlPart function to extract specified components (host, port, path, etc.) from a URL.

Workbook features

Error notifications when exporting to a deleted Google Drive folder

An error is now shown if there are exports scheduled to deliver to a deleted Google Drive folder.

See Export to Google Drive.

Hide or show fixed pivot table headers (Beta)

You can now hide or show fixed row and column headers in pivot tables. This functionality has rolled out for some organizations, and will continue to be incrementally rolled out over the next week.

See Hide or show fixed pivot table headers (Beta) .

Updated default export notification names

When scheduling exports, the default naming now follows this format:

• When exporting an entire workbook: [Destination] [Format Type]
• When exporting a specific page or element in a workbook: [Attachment Name] [Destination] [Format Type]

Bug fixes

• Percentage-formatted input table columns with data validation have been updated with the following behavior:
  • In the data validation range configuration, integer input is now treated as a percentage. For example, if a user enters 80 as the minimum value, the input is converted to 80% instead of scaling to 8000%.
  • In the column, integer input is now treated as a percentage and is accepted when it meets the validation criteria. For example, if the validation range is 75%–100% and a user enters 85, the input is converted to 85% and passes validation.
  • In the column, percentage input (value with % suffix) is no longer rescaled. For example, if a user enters85%, the input is interpreted literally as 85% instead of scaling to 8500% (as a conversion from 85). When input fails validation, the tooltip message now displays the range as percentages. For example, if the validation range is 75%–100%, the tooltip indicates “Input must be between 75.00% and 100.00%” instead of “Input must be between 75 and 100.”