Skip to content

Known Issues and Workarounds in CI Report

Enterprise Platform Release Notes 2021 R1 SP1

These “Known Issues” have been identified in Cost Insight Report 2021 R1 SP1.

  • Incorrect ‘Activity Time’ Field in All Activities Derived Table for Oracle and Microsoft SQL Server Database Types

    If you use a Microsoft SQL Server or Oracle database type, in the Cost Insight Report Ad Hoc reporting tool, in the All Activities derived table , the value for ‘Activity Time’ field is incorrect.

  • Digital Factory (VPE) Performance and Digital Factory (VPE) Performance Details Cost Insight Report out of the box reports unavailable due to JasperReports Server bug

    Due to a JasperReports Server bug, If you launch a VPE Performance or a VPE Performance Details out of the box report, Cost Insight Report generates this error:

    “There was an error on the server. Try again or contact site administrators.”

    Due to this error the VPE Performance and VPE Performance Details reports are temporarily unavailable.

  • Cost Insight Report superuser password reverts to default after migration to aPriori Enterprise Server Platform 2020 R1.

    When you migrate to a new version of Cost Insight Report, the JasperReports Server superuser account password reverts to the default value. As a best practice, change the superuser password to either the password that you used before the migration or to a new password (recommended).

    For information about the default superuser password, contact aPriori Customer Support.

  • An issue with Chrome prevents you from downloading exported PDFs.

    Due to a problem with the Chrome browser, attempts to download exported PDF reports result in the error: “Failed - Network error

    Workarounds:

  • The LastPass password manager prevents all browsers from exporting any Cost Insight Report to any file extension.

    When you attempt to export a report, the browser opens a new tab for the Cost Insight Report log-in page. If you log in, the new tab opens to the Cost Insight Report home page. This issue is caused by a LastPass script that is appended to the page and executed on an export form submission.

    Workarounds: