Views:

Applies to Product -Dynamics 365 Supply Chain Management


What’s happening?
An attempt was made to set a report parameter 'FormLetterRecordId' that is not defined in the report.


Reason:
This occurs when a customer updates to a new version of an application, and the application team has made an update to the out-of-box controller class, such as adding a new parameter. If the customer has created a custom version of the report design without creating a new version of the report controller, the custom report design does not recognize the new parameter from the out-of-the-box controller, resulting in this error from the reporting platform.


Resolution:

  1. Check Report Parameters: Ensure that all required parameters for the report are correctly defined and mapped. Review the report design in the Report Designer.
  2. Fix Custom Code: Customers should fix their custom code to ensure they use a single report name from the beginning. This is the long-term and correct way to resolve the issue.
  3. Temporary Fix: As a short-term solution, customers can modify their custom report to ensure it has the exact same parameters as those defined in the original report. Ensure that the parameter names match in casing.
  4. Flighting Flag: If the customer is on the specified version, the flighting flag "Reporting_FixUnknownReportExecutionParameters" can be turned on to unblock the customer. Work with the designated team to add this flag for the environment only. After setting the flag, the report should run, but a warning will be displayed indicating that an unexpected report parameter was automatically removed during the rendering process. This warning cannot be disabled.
  5. Verify Report Controller: Ensure the report controller has the correct report name set by checking the relevant method.