Forum Discussion
Paginated reports: getting error that parameter not declared though I properly declared it
In my paginated reports, I’m getting an error saying that a parameter has not been declared , though they have actually been (see in the attached screenshots), .
I’ve also tried several possible fixes, such as: Hardcoding some values directly in the DAX query to confirm the report runs and then replacing those hardcoded values with parameters afterward, Declaring the parameters before writing the query, and also the other way around. None of them helped.
Has anyone else run into this issue and found a working solution?
Thanks
Solved. In the dataset properties ---> parameters, I typed the parameter name as Anonymous_date and the value as [@to_date]. (This was what Chat GPT told me, unfortunately. :)). Today I luckily saw a web with a screenshot of this property and basedon that, I corrected the name to simply to_date (without the @ sign), and the value kept as before as [@to_date]. This worked.
5 Replies
That is where I posted the image from. When I click dataset properties --> parameters tab, I see Anonymous_date and in the Value (where I typed =Parameters!to_date.Value) it shows [@to_date]. when I press fx button it shows the entire expression as shown in the picture.
If I ignore the error message and still run the report, it does not run but just gives the same error message that the parameter was not declared.Solved. In the dataset properties ---> parameters, I typed the parameter name as Anonymous_date and the value as [@to_date]. (This was what Chat GPT told me, unfortunately. :)). Today I luckily saw a web with a screenshot of this property and basedon that, I corrected the name to simply to_date (without the @ sign), and the value kept as before as [@to_date]. This worked.
Hi arunbyc
Thank you for reaching out to the Microsoft Fabric Forum Community.
As you mentioned that your issue has been resolved, I'm glad to hear that. Could you please mark your solution reply as the accepted solution? This will help others who might face the same issue.
Thanks.Hi @arunbyc
I'm glad to hear that your issue has been resolved. Could you please mark your solution reply as the accepted solution? This will help others who might face the same issue.
Thanks.
