Skip to main content
Solved

Custom Report AR Aging by Employee Not Working in 2023 R2


Forum|alt.badge.img

Hi there,

 

I’ve modified the original AR Aging report to AR Aging by Employee report in 2022 R1. The report will generate the AR Aging based on the customers assigned to the logged in user (salesperson) only. The report works fine until the version got upgraded to 2023 R2 where it failed to show any records.

 

The tables that I’ve added:

  1. CustSalesPeople (linked to CustomerMaster on BAccountID).
  2. SalesPerson (linked to CustSalesPeople on SalesPersonID).
  3. EPEmployee (linked to SalesPerson on SalesPersonID)

 

I’ve added a line on Parameters called UserID to retrieve the user info by inserting the default value:

=Report.GetDefUI('AccessInfo.UserID')

 

I’ve added a line on Filters to link the parameter UserID to EPEmployee table:

 

Despite all this, all it takes is just an upgrade to break this report. I’ve attached the report as well and hopefully someone can help me understand on why the report is not working anymore.

Best answer by ericklasimin61

Problem solved. Turns out that there is nothing wrong with the report itself but rather the restriction group configuration that is causing the issue.

View original
Did this topic help you find an answer to your question?

8 replies

Forum|alt.badge.img+1
  • Jr Varsity II
  • 37 replies
  • August 1, 2024

In your joins, the “ARInvoice” table is used a parent table before it was actually joined into the report through the “CustomerMaster” table.- this should cause an error when trying to run the report. You need to join that table into the report before using as a parent table.

 

 I would also check your “filters” tab as it seems your braces don’t match up and would be causing unexpected results.

 

If neither item above works, can you attach what error message you are receiving?


Forum|alt.badge.img
  • Author
  • Jr Varsity III
  • 49 replies
  • August 1, 2024

Hi @mbridges00 , thank you for taking your time in looking into this. The table screenshot above was only showing the lower part (additional tables added on top of the originals) of it, but here’s the full table joins:

 

On Filters, the only line added is:

EPEmployee.UserID Equal @UserID

Hence, no brackets were modified from the original filters.

 

There is no error message appearing when running the report, but rather there are no records displaying at all.


Forum|alt.badge.img+1
  • Jr Varsity II
  • 37 replies
  • August 1, 2024

If you remove the last line (EpEmployee.UserID = @UserId) from the filters tab, does the report populate?


Forum|alt.badge.img
  • Author
  • Jr Varsity III
  • 49 replies
  • August 1, 2024

Yes, the report is populated with records, but now it will show all salesperson’s AR Aging instead of the logged in user. I have confirmed that both the values from the parameter and the one in DAC is the same as shown below:

 

Parameter:

 

DAC source data:

 

I’m puzzled as to why the system failed to equate these two values.


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2754 replies
  • August 26, 2024

Hi @ericklasimin61 were you able to find a solution? Thank you!


Forum|alt.badge.img
  • Author
  • Jr Varsity III
  • 49 replies
  • August 27, 2024

Hi @Chris Hackett , unfortunately, the issue has yet to be resolved even after updating to Build 23.214.0020.

 

I have tried raising a case to the principal, but they dismissed the case under the pretext of “The report has been customized.” and suggested me to create this post. What worked without any issues previously suddenly stopped working without knowing the reasons why. I do hope they can shed some light on this issue.


Forum|alt.badge.img
  • Author
  • Jr Varsity III
  • 49 replies
  • Answer
  • August 29, 2024

Problem solved. Turns out that there is nothing wrong with the report itself but rather the restriction group configuration that is causing the issue.


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2754 replies
  • August 29, 2024

Thank you for sharing your solution with the community @ericklasimin61!


Reply


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