Finance | Project Operations, Human Resources, ...

An attempt was made to set a report parameter 'XXX' that s not defined in this report.

(7) Share

Report

Posted on by Shooowtek

843

hello,

when running a customized SSRS report, the following message appears: "An attempt was made to set a report parameter 'SuppressDepreciationOfPaymentSection1' that is not defined in this report."

I checked and indeed, the report contains a duplicate of this parameter. I tried to delete it, but then errors occur during the deployment of the report.
How can I fix this?

The issue occurs only in the UAT environment. In the DEV environment, the report runs without any problems.

Thanks.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (6)

Answers (0)

Jonas "Jones" Melgaard 4,985 Most Valuable Professional on at

Like (1)

Report

It can unfortunately be a bit tricky to get rid of this error, you might need to examine the XML definition of the report to make sure it's entirely gone.

I have found an article that covers it a bit (The number of defined parameters is not equal to the number of cell definitions in the parameter panel. / DaxOnline)

This is the first thing I'd try to do.

Was this reply helpful? Yes No
Shooowtek 843 on at

Like (1)

Report

Hello Jonas,

It seems to me that the problem is about something else.

Was this reply helpful? Yes No
Jonas "Jones" Melgaard 4,985 Most Valuable Professional on at

Like (2)

Report

Next thing I’d try is flushing the AOD cache. I’ve seen it being quite stubborn, although I’d expect it to be flushed during deployments…

https://erconsult.eu/blog/sysflushaod-refresh-sysextension-cache-in-d365fo/

Was this reply helpful? Yes No
Waed Ayyad 9,039 Super User 2025 Season 2 on at

Like (1)

Report

Hi,

Try to open the XML of the report and search for the SuppressDepreciationOfPaymentSection1, and delete it, build the Project and deploy the report, then reset the Usage data, restart reporting service and then run the report.

Thanks,

Waed Ayyad

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Suggested answer

Syed Amir Ali 179 on at

Like (0)

Report

Hey,

I encountered the same issue today. I removed every instance of SuppressDepreciationOfPaymentSection1 from the SSRS report XML, then rebuilt the project and redeployed the report design. It worked fine for me—give it a try

Regards,
Amir.

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

DAnny3211 11,397 on at

Like (0)

Report

Hi,

The error message indicates that the SSRS report is referencing a parameter (`SuppressDepreciationOfPaymentSection1`) that is either duplicated or not properly defined in the report definition. This often happens when there are mismatches between the report’s RDL file and the deployed version, or if parameters are manually edited outside of Visual Studio.

Here are some steps to resolve the issue:

1. **Synchronize the RDL Files**
Ensure that the RDL file in your UAT environment matches the one in DEV, where the report works correctly. Redeploy the report from DEV to UAT to eliminate discrepancies.

2. **Remove Duplicate Parameters**
Open the report in Visual Studio, check the **Report Parameters** section, and ensure that `SuppressDepreciationOfPaymentSection1` appears only once. Remove any duplicates and save the report.

3. **Clean Deployment**
Before redeploying, delete the existing report from the UAT environment to avoid conflicts with old parameter definitions. Then deploy the cleaned report.

4. **Check for Customizations**
If the report is customized, verify that any custom code or extensions referencing this parameter are consistent across environments.

5. **Validate Data Sources and Datasets**
Make sure all datasets and data sources are correctly configured and do not reference parameters that have been removed.

You can find more details in the official documentation on Deploying and Troubleshooting SSRS Reports in Dynamics 365 Finance.

Please verify if this helps resolve your issue.

Thanks and best regards,
Daniele
*Note: This response was prepared with support from Copilot to ensure clarity and completeness.*

Was this reply helpful? Yes No