1. Check your zoom level on your browser - there is a visual bug when viewing the end of your report if you have your zoom level set to 90% or 80% and have custom columns. If you are noticing a misalignment with the header of the report and the data underneath, ensure you have your zoom level set to 100%.

  2. Version 1.11: if you are using query filters on a query with no BO selected, you will be unable to edit those query filters after. This problem will be solved in Version 1.12. The work around for now will be to re-create your report with the desired query filters.

  3. Zooming Issues: there is a visual bug with the graphing library we use that causes an issue in Kurve in regards to zooming into graphs with too much data. When you try to zoom in, no results will be appear in the zoom. The work around for this is to use other filtering options to reduce the number of dimension values, limit your data set, or choose another field for the dimension.

  4. Have you created a custom column then changed the type after creation and aren't able to filter according to your updated filter type? Sometimes there are issues converting the column to the correct filter type. A simple refresh of the page should solve the problem.

  5. If you're using Microsoft Edge and noticed an issue re-formatting your number columns, don't worry, we are aware of this issue! The formatting of currency is currently broken in Edge and we are waiting on a fix from their end to resolve the matter.
    • We recommend using Chrome for using Kurve

  6. Are you trying to filter your graph based on values of True and False that are in your report? 
    • In versions 1.7.0 and earlier, this is a known issue
    • Our recommendation would be to create a custom column where you reference Yes/No or 0, 1 instead

  7. Naming conventions for fields: 
    • For example, you may notice your number or date columns do not have the appropriate filter type (i.e. they're showing as unique text values)
    • Kurve reads the suffix to determine the filter type to add to that column
    • Some OOB TRIRIGA Fields have been set up with the wrong suffix (i.e Active Start Date and Active End Date)
    • Suggestion: Add a custom column and add the column as whatever data type you are looking for
    • Example: If I want to be able to filter for a date range using Active Start Date, I would re-add this column as a custom column and select Date as the output

  8. When in doubt, try it out in Chrome and see if the issue persists

  9. Some licenses do not provide the necessary requirements in order to use Kurve
    • Users with only the Request Central license will not have access to Kurve because the license does not provide sufficient access to the Group module
    • Kurve requires all licenses to have access to this in order to utilize the sharing functionality

  10. In 1.7.0 and earlier, if you format your dates as DD/MM/YYYY, Kurve will not recognize the values as actual dates

  11. In 1.7.0 and earlier, there is a bug with custom column expressions. If you attempt to do an expression using the Less Than symbol and there is a letter immediately after, this would corrupt the report. We have added functionality (1.8.0) to ensure this doesn't happen. In previous versions, if you're using the Less Than symbol, always ensure you add one space after before the next character.

  12. In versions 1.9 and 1.10, if you share your report with a security group, the users in that security group will be unable to create a graph from the report. This is being worked on, and will be fixed in the 1.11 release

  13. "Error! The connection to TRIRIGA was unsuccessful. Please try again or contact your administrator for assistance."
    • This is an error that can randomly happen when you try to load a Kurve graph or report. It could either be stemming from the TRIRIGA Server side or from the request sent through the UX API itself. A refresh of the page recorrects the issue.
  14. Graph Filtering: there are issues when filtering in a graph if the column has a contains/does not contain filter, but is also selected as a measure.

    • Parsing will convert the text to a number, which will cause issues with uppercase function and also won’t filter correctly if value has non-number text that was removed by the parsing

  15. V1.17.0 Report Filtering: Floating filter is not visually displaying under the field name when filtering in a report
    This is a visual bug, the filters are applied and can be seen from the filter panel on the right side of the report. This is a bug with the reporting library that we use, we will continue to monitor this for a fix.

  16. The following TRIRIGA date and date/time formats not compatible for Query Filtering:  

    • yyyy.MM.dd hh:mm a zzz
    • MMMMM dd, yyyy hh:mm a zzz
    • dd-MM-yyyy HH'h'mm'min'
    • yyyy-MM-dd HH:mm
    • dd.MM.yyyy
  17. On or Before Query Filter on DT Fields: there are some inconsistencies using On or Before for DateTime fields.
    In this scenario, if the time component of the date-time is anything other than midnight (00:00), inconsistencies occur. For example, if you're filtering for events on or before a specific date, events occurring later in the day may not be included as expected. This behavior is consistent with how TRIRIGA filtering operates, which suggests that it might be a deliberate design choice rather than a flaw. However, the issue has been identified and reported to IBM for potential resolution.