Problem with UpdateCollectionStatus parameter in CustAgingReport

(0) Share

Report

Posted on by TheGoodDBA

235

I am customizing the CustAgingReport in D365 F&O and I get the following error when attempting to run my version of the report.

"An attempt was made to set a report parameter 'UpdateCollectionStatus' that is not defined in this report."

This parameter exists in the dataset and the report parameters, but did not prior to my restoring the dataset in order to add my new fields. I'm not sure where to go in order to rectify the error. It's in the report and in the dialog when running the report.

Any help would be appreciated.

Thanks,

Steve

I have the same question (0)

All responses (6)

Answers (1)

Sort by

GirishS 27,843 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi Steve Boccio,

Just delete the report paramters and restore the dataset - Report parameters will create again and try deploying the report.

Thanks,

Girish S.

Was this reply helpful? Yes No
TheGoodDBA 235 on at

Like (0)

Report
Copy link

Link copied!

Hi Girish,

Thanks for the reply. Deleting the parameter UpdateCollectionStatus and restoring the dataset only puts the parameter back in place. Deleting the parameter and NOT restoring the dataset gives an error. Both of these actions I am doing on my custom copy of the report. When I look at the original report's parameters, Updatecollectionstatus does not exist, which I believe is why the original report executes without issue. If I restore the dataset on the original report, it does bring in the new parameter, but of course I cannot save it.

So you see, I am caught between having to customize the report, which means restoring the dataset, which in turn causes the issue. This must be a bug in 10.0.28 update52?

Any other suggestions are appreciated.

Steve B.

Was this reply helpful? Yes No
Verified answer

Dinaz 115 on at

Like (0)

Report
Copy link

Link copied!

Hi Steve,

1. You have to delete the parameter from report parameters node.

2. Delete additional parameters from the xml. Please refer the below link.

daxonline.org/1708-the-number-of-defined-parameters-is-not-equal-to-the-number-of-cell-definitions-in-the-parameter-panel.html

3. Build the solution.

Was this reply helpful? Yes No
TheGoodDBA 235 on at

Like (0)

Report
Copy link

Link copied!

Dinaz,

Thanks for the reply. The manual process did work for resolving/working around the error, but the issue remains as to why this is happening on the report? And since the parameter continues to show up upon edits to the report, and deployments of other changes, it really isn't ideal for getting the report customized and tested.

thanks,

Steve

Was this reply helpful? Yes No
Megan B. 2 on at

Like (0)

Report
Copy link

Link copied!

We are having the same problem with the bill of lading report. Did you ever find a solution for this?

Was this reply helpful? Yes No
Megan B. 2 on at

Like (0)

Report
Copy link

Link copied!

We are having the same issue with the customer aging report. Did you ever find a solution?

Was this reply helpful? Yes No