web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Attempt was made to se...
Finance | Project Operations, Human Resources, ...
Unanswered

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

(1) ShareShare
ReportReport
Posted on by MYGz 2,063
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)
  • Martin Dráb Profile Picture
    Martin Dráb 237,002 Most Valuable Professional on at
    Attempt was made to set a report parameter FormLetterRecordId that is not defined in this report.
    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? 
  • MYGz Profile Picture
    MYGz 2,063 on at
    Attempt was made to set a report parameter FormLetterRecordId that is not defined in this report.
    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
  • Martin Dráb Profile Picture
    Martin Dráb 237,002 Most Valuable Professional on at
    Attempt was made to set a report parameter FormLetterRecordId that is not defined in this report.
    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?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Congratulations to the October Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 596 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 570 Super User 2025 Season 2

#3
CU05031448-0 Profile Picture

CU05031448-0 556

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans