Release Notes 2022.5.0

Release Highlights

Incorta 2022.5.0 release brings conditional formatting to Bar and Column visualizations. In addition, it provides a series of enhancements and fixes across Incorta.

New Features

• Conditional Formatting for Column and Bar visualizations

Conditional Formatting for Column and Bar visualizations

Conditional formatting is now available for Column and Bar visualizations. You can apply multiple conditional formats to a measure column in a bar or a column chart insight that has only one measure pill and no coloring dimension pills. Conditional formats are preserved when changing a tabular insight to a bar or column insight and vice versa.

Enhancements and Fixes

This release introduces some additional enhancements and fixes that help to make Incorta more stable, engaging, and reliable.

Physical Schema and Business Schema

• Fixed an issue that caused an erroneous successful extraction process despite the failure of rotating Parquet files
• Resolved an issue where a materialized view would not properly read columns from non-english format sources
• Resolved an issue where query execution could fail to resolve business views due to an updated SQLi execution process
• Fixed a case where loading tables using a data agent failed after upgrading to the 2022.4.0 release
• Fixed an issue that caused incremental load jobs of tables with SQL-based data sources, such as Microsoft SQL Server and Oracle, to fail when the Incremental Script had multiple conditions with the ? option to retrieve new and updated data
• Resolved an issue where business views could not be dragged and sorted

Visualizations, Dashboards, and Analyzer

• Fixed an issue where the aggregated, listing, and pivot table created appeared incomplete when one of its cells was selected
• Resolved an issue where the subtotal of an aggregated table would not be appear in certain display configurations
• Resolved an issue where SSO users were not directed to their default dashboards
• Resolved an issue where the Analyzer could fail when max group limit was exceeded

Known Issues and Workarounds

The following table illustrates the known issues in this release, with a workaround if it is available:

• Exporting a tenant with a global variable that uses the newly supported syntax (query or queryDistinct functions), and then importing it to the same or another cluster will cause the Edit Global Variable dialog to show an empty Value. This applies to the following paths:

  • A tenant from a 2022.4.0 cluster to the same or another 2022.4.0 cluster
  • A tenant from a 2022.4.0 cluster to a 2022.5.0 cluster
  • A tenant from a 2022.5.0 cluster to the same or another 2022.5.0 cluster

  To resolve the above issue, you can manually edit the value to enter the query expression again.

• Formula columns that reference global variables are evaluated as string in the following cases:

  • Importing a tenant
  • Restoring a tenant
  • Starting up a server or a cluster

• Global variables with date or timestamp data types are not evaluated properly when referenced in the Analyzer.

• Incremental load jobs of tables with SQL-based data sources, such as Microsoft SQL Server and Oracle, will fail if the Incremental Script has multiple conditions with the ? option to retrieve new and updated data

• After changing the data source of an object in an imported physical schema or tenant to an Incorta SQL Table or changing an Incorta SQL Table in an imported physical schema or tenant to another object type, MV for example, the Disable Full Load option will be automatically enabled, which will lead to skipping these objects in the next schema full load jobs.

  • You need to either disable the feature manually for objects that support disabling full loads (physical schema tables and MVs with incremental load enabled) or recreate the objects.