1. Home
  2. On-premises 5.2
  3. Guides
  4. Tours
  5. Concepts
  6. Tools
  7. References
  8. Integrations
  9. Data applications
  10. Releases
    1. Release Model
    2. Release Notes 5.2
    3. Release Notes 5.2.1
    4. Release Notes 5.2.2
    5. Release Notes 5.2.3
    6. Release Notes 5.2.4
    7. Release Notes 5.2.5
    8. Release Notes 5.2.6
    9. Release Notes 5.2.7
    10. Release Notes 5.2.8
    11. Release Notes 5.2.9
    12. Release Notes 5.2.10
    13. Release Notes 5.2.11
    14. Maintenance Packs
    15. Known Issues

Known Issues

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

  • In 5.2.8, when trying to download an insight in one tab while it is being downloaded from another browser tab or refreshing the current tab and trying to download again causes the second trial to fail and throws an error. (Resolved in 5.2.9)
    • Workaround: Wait till the first download operation is completed and then try to download again.
  • When creating a Google Drive, Google Sheet, Box, and Dropbox data source the authentication token will expire after two weeks.
    • Workaround: Every two weeks create new tokens and re-authenticate the data source.
  • The extraction job is not respecting the table thread pool size if it is less than DataSet thread pool size
    • Workaround: Set the dataset.thread.pool.limit to be equal to or greater than the thread.pool.limit if you have thread.pool.limit configured in the loader service.properties file
  • Loading a physical schema after removing columns that are used in joins will show a Success load status instead of Finished with errors, even when the Stop on Error toggle is enabled.
    • Workaround: Do not delete any columns that are used in joins unless you delete or update the join in the same update job.
  • Opening the SQL Query dialog of a Table with NetSuite Suite Analytics as a data source takes several minutes to load
  • Email addresses added as CC or BCC in a scheduled data notification are not saved when using the EWS protocol
  • Synchronization jobs that occur during rendering a related insight on a dashboard cause the rendered insight to fail
  • Adding columns in a specific order to the Grouping Dimension tray of a Listing table, and then enabling Subtotal cause the INC_04050735: Unexpected error while sorting groups error message to appear in the Visualization canvas of the Analyzer.
  • Some physical schemas experience a prolonged loading time.
  • Configured data agents will not resume functioning properly after the upgrade
  • Cascaded filters do not work properly if a prompt field is sorted using another column
  • Arabic names are not displayed properly when syncing an LDAP directory with Incorta
  • An error occurs when creating an SQL table based on SQL Server data source and adding a query hint in the query statement
    • Workaround: Ignore the error, select Done, and then save the changes. The table will load without any errors.
  • Schema load logs for materialized views (MVs) are missing the following when entering the transforming phase: HA, Task, Schema Name, Table Name, Job ID, Job Type (Transforming), ETL, Load Type (INCR)
  • Notebook auto-complete for Spark Python is not working as expected
  • Insights might not render when you have the same insight duplicated many times in the same dashboard tab
  • In the Schema Designer when a table requires stage loading, the warning message appears as Full load required for a new model to take effect instead of Staging load required for new model to take effect.
  • In the Schema Designer, for a given unloaded object, the Preview Data button is enabled instead of being disabled
  • In the Schema Designer, a warning message should be displayed when enabling the encryption for a Key column
  • In the Table Editor, the Filters tab is displayed for alias tables
  • Missing Geo Column type from the column type list
  • Missing In operator in the security runtime filters operators
  • Updating the bookmark for dashboard with an applied filter after editing the filter results in an error
  • Loading a table without a key incrementally for the first time results in an error
    • Workaround: Attempt to load the table incrementally again