Attempt was made to set a report parameter FormLetterRecordId that is not defined in this report.

(4) Share

Report

Posted on by MYGz

2,334

Hi,

I'm getting this error while trying to print Sales Order Confirmation Report

Confirmation (SO###) An attempt was made to set a report parameter 'FormLetterRecordId' that is not defined in this report.

Any clues what could be wrong?

I'm using 10.0.43 VHD. But the UAT is on 10.0.45 and I have restored the DB on VHD.

Appreciate any tips.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (4)

Answers (1)

Martin Dráb 239,029 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Okay, so you're talking about a development environment where you restored a database from a higher version of F&O than what you have. Are you intentionally developing on an older version?

How did you run the report?

Was this reply helpful? Yes No
MYGz 2,334 on at

Like (1)

Report
Copy link

Link copied!

Hi,

I was able to successfully upgrade the development environment also to 10.0.45. But still the same error.

It's a custom report and I'm printing using "use print management" option after going into "Sales Order Confirmations" page from Sales Orders List page form.

Thanks

Was this reply helpful? Yes No
Martin Dráb 239,029 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

A custom report? That's a critical piece of information. Next time, please mention such things already when creating a thread.

You didn't say that explicitly, but I'm assuming you mean that the report worked before the DB restore. Is it the case?

Does your report have FormLetterRecordId parameter or not? If so, have you tried redeploying it?

Which method does throw the exception?

Was this reply helpful? Yes No
Verified answer

MYGz 2,334 on at

Like (1)

Report
Copy link

Link copied!

Hi @Martin Dráb

Thanks for your inputs.

It turned out that the custom table and classes were used for the Custom Sales Order Confirmation report and it was to be called from a custom button instead of standard buttons. Hence the error.

Was this reply helpful? Yes No