1. On-premises 6.0
  2. Guides
  3. Concepts
  4. Tools
  5. References
  6. Integrations
  7. Data applications
  8. Releases
    1. Release Model
    2. Release Notes 6.0
    3. Release Notes 6.0.1
    4. Release Notes 6.0.2
    5. Release Notes 6.0.3
    6. Known Issues

Known Issues in 6.0 Release

The following are the known issues in the 6.x releases along with the workaround and fix version if any. This list may contain issues from earlier releases that haven't been resolved yet.

Known issueStatusAffected VersionsWorkaroundFix Version
Trying to download an insight on another tab while it is being downloaded on another browser tab or refreshing the current tab and trying to download again causes the second trial to fail and throws an error.Open6.0Wait till the first download operation is completed and then try to download again.
Using internal session variables with SQLi service might cause out of memory error.Open6.0Add -Dengine.max_off_heap_memory=<value in Bytes> in the <installationPath>/IncortaNode/sqli_extra_jvm.properties, where the SQLi service is installed to set an off heap limit. For example, -Dengine.max_off_heap_memory=10737418240 will set the off heap memory to 10 GBs.
Running total is not displayed correctly when the measure has null values.Open6.0
Runtime filters are not displayed inside a dashboard.Open6.0Refresh the dashboard page.
When enabling Spark-based extraction on a data source while running Spark 3.3, the extraction of the respective table fails.OpenSpark 3.3Turn off the Enable Spark Based Extraction in the Table Data Source or Edit Dataset dialog.
A formula column that only references a physical column with null values shows wrong results as the Loader Service does not respect the null values when materializing the formula column.Open6.0
The count and distinct functions return null values instead of zeros when using them in a flat table or a session variable.Open6.0
Applying an average aggregation on a decimal column with null values only throws an error and causes the insight to fail to render.Open6.0
PK index calculations take a long time during load jobs when there are a large number of segments or increments to check.Open6.0Do one or more of the following:
  ●  Contact Incorta Support to merge these segments and reduce their number.
  ●  Create a materialized view or Incorta-over-Incorta table that consumes these segments and creates a less number of segments.
  ●  Contact Incorta Support to edit the Loader Service engine.properties file and set the new option store.offsets_exists_parallel to true. This option requires a lot of resources. Thus, it is suitable for very large clusters.
When multi-schema loading is enabled, adding a load plan from Schema Manager doesn’t display the total number of schemas correctly.Open6.0
Numeric Range Slicer does not function properly with variablesOpen6.0
When the Pause Scheduled Jobs option is enabled in the Cluster Management Console (CMC), the emails of manually activated scheduled jobs are not sent.Open6.0
Scheduled jobs of overwritten dashboards and physical schemas are not deleted.Open6.0
The “You have successfully deleted 1 schema(s)” message is erroneously displayed when trying to delete a physical schema while loading it.Open6.0
Access rights to a parent folder are not propagated to child folders and dashboards if the same access rights were revoked before.Open6.0
Aggregated tables with hierarchical data do not support conditional formatting based on other measures when adding multiple attributes.Open6.0
No validation on functions is triggered in the Formula Builder when creating global variables.

Open6.0
Global Variables that return a list of values are not functioning properly when referenced in materialized views (MVs) or individual filters.

Open6.0
Global Variables will not appear on the list of variables when referenced in a column individual filter, that is when you type $ in the Search Values box.Open6.0You can add the global variable manually, if applicable. In Query, Contains, and Starts With are examples of functions that accept a global variable as a filter value to be added manually.
Using the DISTINCT operator on a measure in a Pivot table that is built over an Incorta SQL View throws errors.

Open6.0
In an imported physical schema or tenant, the Disable Full Load option will be automatically enabled after changing the data source of an object to an Incorta SQL Table or vice versa, which will lead to skipping these updated objects in the next schema full load jobs.Open6.0You 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.

Note:
This issue does not apply to newly created Incorta SQL Tables.
Incrementally loading a table without a key for the first time results in an error.

Open6.0Attempt to load the table incrementally again
Insights might not render when you run the same query multiple times for the same dashboard.

Open6.0
Email addresses added as CC or BCC in a scheduled data notification are not saved.

Open5.2.1 and later