Skip to main content
Question

Report Discrepancies

  • June 26, 2026
  • 0 replies
  • 0 views

We have a custom report used to review outstanding customer deposits. After our recent Acumatica upgrade from 24R1 to 26R1, the report began returning different results depending on the user running it.

When I run the report as an administrator, the report displays the full data set correctly, including 2025 and 2026 activity. However, when our Controller runs the same report with the same parameters, the report only appears to show data from 2024 and prior. Any 2025/2026 activity is missing from his output.

I initially suspected this was a security/access issue, but I have not been able to identify the cause. I checked user roles, GL access, and report access, and I also temporarily gave the Controller Administrator rights. Even with Administrator rights, the report still behaved the same way for him.

A few additional notes:

  • The issue started only after the upgrade from 24R1 to 26R1.
  • The report is custom and is based on GLTran data.
  • The Controller can see 2025/2026 transactions in Account Details, so he does appear to have access to the underlying GL activity.
  • When I traced the report for both users, the generated SQL appeared to be the same.
  • Despite that, the report output is different by user.
  • If I modify the report to only show transactions from 1/1/2025 forward, the Controller’s version comes back blank, while mine still returns data.

Has anyone seen this behavior after an upgrade, where a custom Report Designer report returns different visible output by user even though the users appear to have access to the underlying GL data? Are there any post-upgrade report settings, cached report definitions, user-specific report settings, or Report Designer changes in 26R1 that could cause this?