Kurve Solutions

Migration Process

• Completion
  • When a Kurve admin or record owner opens a record, it automatically migrates to the new API.
  • Migrated records are not compatible with earlier Kurve versions.
  • Upon opening your graph or report, you’ll see one of the following: 
    • A success notification confirming the migration.
    • An error dialogue outlining any lost features — download the error report for future reference.
• This version of Kurve is NOT backwards compatible
  • Please click here to review our migration process if you need to restore to V1.29.1
  • Please reach out if you need any assistance.

Major Changes:

2.0 transitions to the Query Data API within TRIRIGA which changes how we pull data from TRIRIGA. There are key differences between the previous API and the new API as listed below. All post migration features to review will be shown as an error pop up that you can download in Kurve.

Post Migration Features to Review:

• Columns like triRecordSY and UNIT-related columns (Area-Units) will no longer be automatically added to queries (unless you have manually added them in the TRIRIGA query). 
  • Queries using these fields for graphs or reports must be updated to include them.
• Columns with wrong types are fixed: 
  • In old Kurve, columns were sometimes saved with the wrong type (e.g., a numeric field stored as text) when the user did not have full access to the related BOs)
  • 2.0 automatically corrects this.

Report side:

• Conditional formatting rules, filters, and aggregations (sum/avg/count) will be removed if column orginally had the wrong type.
• Users must reapply them after migration.

Graph side:

• Graph filters deactivated and the filter type & value are cleared if column originally had the wrong type
• Users must reselect these after migration.

• Duplicated column settings in Kurve reports and graphs are lost in these cases: 
  • TRIRIGA Source Query had Group settings on any column.
  • Graph created directly from a TRIRIGA query (not a Kurve report).
  • Kurve Report was never saved.
• Graph configurations (dimension, measure, colorBy, graph filters) will be reset if they relied on: 
  • triRecordSY or UNIT columns.
  • Custom columns remain selected but may need refinement if they relied on the above.
• Custom Columns will need to be edited if they referenced:
  • triRecordSY or UNIT columns.
  • Duplicated columns - if a custom column was using a duplicated column and the report was saved at least once and the source query has grouping turned on any column
• In pivot mode, the following settings will be lost:
  • Column width adjustments
  • Sorting
  • Pinning
  • Filtering

Functionality Updates:

• Enforce_GUI_Level_Query_Security: There is a setting on the TRIRIGA ADMIN console that is by default off. In order to enforce proper security, it needs to be turned on
  • If it is turned off: a user without access to the BO can still receive data from that BO
• UOM columns are now a single numeric column (previously split into number + unit).
  • For example: 

• Custom Columns now display full long IDs in the expression field.
• Duplicate columns from multiple BOs will now be displayed with the same name (no more Name-1, Name-2).
• Kurve now loads records in pages as set in the new Kurve Global Settings page
  • Improved feedback during the loading process
• TRIRIGA Query with Groups/Summary Applied: 
  • Record counter hidden while loading.
  • API Call settings (set in the Kurve Global Settings) will be ignored and we will load all the data at once
• Query filters are now available for all columns, not just the primary BO.
• Localization: Kurve will automatically translate according to the language set in a user's profile; Kurve is now supported in English, French, Spanish, and German.