Small and medium business | Business Central, N...

Customer Statement Copy Report Filters Not Working Properly

(6) Share

Report

Posted on by TO-13112302-0

Hi all,

My end users only have read access to customers, so when they run the Customer Statement Report they were getting errors as the report updates "Last Statement No." on the Customer Card.

As a work around I copied the original report (Report 1316 Statement) and created my own just adding the permissions, so they don't get that error. I then updated "Report Selection - Sales -> Customer Statement" so that way clicking on the "Statement" Button will run the report.

THE ISSUE: Literally everything else is working properly except the filter "Customer No." doesn't pull the correct Customer number. (See below I was on customer# 10010, but it pulled up 1052).

Important Notes:

- 1052 is the last customer I ran the report for so I'm assuming it's using the last saved values.

- As far as I've spot tested this behavior (filter Customer No. is the last used Customer No.) is consistent for every single Customer except customer number 10000 (I have no clue why this one is different).

Thank you!

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Mohana Yadav 61,204 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Did you try removing SaveValues property under Request Page of report?

requestpage

{

SaveValues = true;

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 12,965 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello John,

This happens because your copied report is remembering the last-used request page filters, so when users click Statement from the Customer Card it reuses the previous Customer No. (1052) instead of the current one (10010); this isn’t related to permissions and is standard report behavior—fix it by setting SaveValues = false; on your custom report, or by explicitly forcing the customer filter in code when the report runs so it always uses the current customer record.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Suggested answer

Dhiren Nagar 2,898 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,

I think this should not happen ideally, because in the backend code I checked that system applies the current record to the report.

You can check the following things:

1 - In your custom report, have you changed the Data Item or Data Item sequences?

2 - Are you using any Custom Report Selection for this customer or other customer? Customer card -> Document layout option. If Yes may be try removing the record.

3 - For safer side just keep the property SaveValues = false.

I hope any of the above will solve this issue. If not you can raise a support request to Microsoft.

Regards,

Dhiren.

Was this reply helpful? Yes No
TO-13112302-0 29 on at

Like (1)

Report
Copy link

Link copied!

Thank you all for the attempts to help.

I understand it is pulling from SaveValues = True;.

And I do want it to pull the other SaveValues like how the normal report does (ex. Start Date/End Date should be the same as when the report was last ran), just not understanding why the Customer No. behavior isn't the same when it is the same report code copy and pasted.

Regarding these questions:

1 - In your custom report, have you changed the Data Item or Data Item sequences?

- No, it is an exact copy of the base report: Report 1316 Statement just with that permissions line in the screenshot.

2 - Are you using any Custom Report Selection for this customer or other customer? Customer card -> Document layout option. If Yes may be try removing the record.

- No.

Was this reply helpful? Yes No
TO-13112302-0 29 on at

Like (1)

Report
Copy link

Link copied!

Hello John,

This happens because your copied report is remembering the last-used request page filters, so when users click Statement from the Customer Card it reuses the previous Customer No. (1052) instead of the current one (10010); this isn’t related to permissions and is standard report behavior—fix it by setting SaveValues = false; on your custom report, or by explicitly forcing the customer filter in code when the report runs so it always uses the current customer record.

Regards,
Oussama Sabbouh

Not saying you're wrong, but SaveValues = True if I look at the base code for Report 1316 (the report I copy and pasted from). But that report doesn't have any issues pulling the correct customer no.

How would you force the customer filter in code when the report runs?

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 12,965 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

What you’re seeing is by design in Report 1316: when run from the Customer Card, the report updates the Customer record (specifically Statement Last Ran), which causes BC to auto-populate the No. filter and also requires Modify permission on Customer. Copying the report doesn’t change this behavior, and there’s no supported way to add Modify permissions to the base report or suppress the update via setup. Turning off SaveValues would avoid persistence but breaks usability, as you noted. Bottom line: there is no configuration-only fix — the only clean solution is a custom copy of report 1316 with the Customer.Modify() logic removed, otherwise users must have Modify rights.

Regards,
Oussama Sabbouh

1 people found this reply helpful.

Was this reply helpful? Yes No