Skip to main content
Question

Data discrepencies in a quick report when using one site as a parameter

  • January 3, 2025
  • 1 reply
  • 38 views
S
Do Gooder (Partner)
Forum|alt.badge.img

My customer is using IFS Cloud 23R2 SU10and the error,

Error stack:
Uncaught (in promise): r0: {"headers":{"normalizedNames{},"lazyUpdate":null}, “status":500," statusText":"Internal Server Error"

is encountered when trying to generate/ export one quick report. Sometimes, the report does not contain any records when generated (whereas the same parameters result in several records when executed in the backend) or the frontend displays a less number of records than the backend or a client error when trying the export the records.

This issue only happens with one of the sites and the report does not have any issue when working with the other sites. Therefore, I suspect that this might be a data issue related to the site the customer is having the issue with.

Could someone please help with how to narrow down/ the next steps?

Thanks in advance!

T
Do Gooder (Customer)
Forum|alt.badge.img+3
  • truth_trump
  • Do Gooder (Customer)
  • January 3, 2025

Hi ​@sachini01 

you may need to thoroughly:

Check Data Integrity

  • Investigate the underlying data for the problematic site:
    • Look for missing or corrupted records in the database.
    • Check for null values, foreign key constraints, or orphaned records that might break the report query.
    • Run the report query directly in the database for the problematic site and compare the result with other sites.

3. Inspect Backend Query Execution

  • Execute the quick report's SQL query in the backend for the problematic site and analyze:
    • The exact number of records returned.
    • Whether any conditions or joins in the query are failing or filtering out records incorrectly.
  • Check for query performance issues such as timeouts, locks, or slow execution.

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings