Skip to main content
Question

Report Discrepancies

  • June 26, 2026
  • 2 replies
  • 9 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?

2 replies

WillH
Semi-Pro II
Forum|alt.badge.img+4
  • Semi-Pro II
  • July 1, 2026

I’d be looking at the RPX file to confirm there wasn’t any conditional logic in the report itself that was aware of the user?
Not that that should change behavior between versions.

(I haven’t used 26r1 much yet, so this is general advice)

My troubleshooting go to s:

  1. Does the user have the same behavior if you change their roles?
  2. Does the user have the same behavior if you login as them?
  3. Does the user have the same behavior in a different browser?
  4. Does another user with the same roles as the initial user have the same issue?
  5. Are you using Modern UI or Classic UI? Does switching between modern and classic change the report behavior?

Given the reference to year dates, I would generally suspect it’s something about Open vs Closed financial periods as a first reference.


  • Author
  • Freshman I
  • July 1, 2026

I’d be looking at the RPX file to confirm there wasn’t any conditional logic in the report itself that was aware of the user?
Not that that should change behavior between versions.

(I haven’t used 26r1 much yet, so this is general advice)

My troubleshooting go to s:

  1. Does the user have the same behavior if you change their roles?
  2. Does the user have the same behavior if you login as them?
  3. Does the user have the same behavior in a different browser?
  4. Does another user with the same roles as the initial user have the same issue?
  5. Are you using Modern UI or Classic UI? Does switching between modern and classic change the report behavior?

Given the reference to year dates, I would generally suspect it’s something about Open vs Closed financial periods as a first reference.

 

I poked around previously and couldn't find anything within the RPX file that contains conditional logic- it’s a very simple report that displays our outstanding deposits. 

Thanks for the troubleshooting steps, my responses below:

  1. Yes, I made them Admin temporarily, but it didn’t change the outcome.
  2. Yes, this was the first thing I tried.
  3. Haven’t checked, will be checking.
  4. Haven't checked, will be checking.
  5. We’re still on Classic UI, ill check this as well. 

Would financial period status behave differently per user, or is that setting system-wide? I assumed it was global.

 

Thank you!