Forum Discussion
Concerns about understanding parameters in Report Builder
Hello,
I am contacting you because I keep getting an error message when I click “Run” in Report Builder.
Here is how my parameters are defined in my dataset query.
These settings are also recorded in the Settings folder.
Here is the complete configuration of the SliderT1Code parameter
In the canvas, I have a matrix in which a cell uses the expression =CDec(IIf(Parameters!SliderT1Code.Value<>0,Parameters!SliderT1Code.Value/100,0))
which calls on this parameter.
However, when I run it, I get the following error message (perhaps this error message is not even related to the expression used above, I'll let you confirm that):
I would like to point out that no other dataset uses this parameter. It is used in a single dataset query.
Do you know why I am getting this error?
Thank you very much in advance for your answers.
Hi Egks
Thank you for contacting the Microsoft Fabric community forum.This error occurs when SliderT1Code is visible in the interface, but Report Builder cannot locate it in the internal Parameters collection during dataset execution. This usually happens if the parameter has been renamed, recreated, or if there’s a mismatch between its type and default value, such as setting it as a Float but storing the default as a string. In these cases, Report Builder might keep an outdated version of the parameter, so one dataset works while another encounters the “parameter does not exist” error.
To fix this, remove the parameter from both the main Parameters panel and the dataset’s Parameters tab, then recreate it with the same name and correct data type, making sure the default value is numeric. After adding it back and saving the report, Report Builder should update its internal XML, allowing the dataset to run without errors. If problems persist, check the report’s XML code for any missing or inconsistent parameter definitions and correct them as needed.
I hope this information is helpful. If you have any further questions, please let us know. we can assist you further.Regards,
Microsoft Fabric Community Support Team.
4 Replies
- mh2587
Super User
check the parameter ordering, particularly the dependent ones.
refer you to this
https://stackoverflow.com/questions/50393389/the-expression-references-the-parameter-which-does-not-exist-in-the-parameters 
v-karpurapudCommunity Support
Hi Egks
Thank you for contacting the Microsoft Fabric community forum.This error occurs when SliderT1Code is visible in the interface, but Report Builder cannot locate it in the internal Parameters collection during dataset execution. This usually happens if the parameter has been renamed, recreated, or if there’s a mismatch between its type and default value, such as setting it as a Float but storing the default as a string. In these cases, Report Builder might keep an outdated version of the parameter, so one dataset works while another encounters the “parameter does not exist” error.
To fix this, remove the parameter from both the main Parameters panel and the dataset’s Parameters tab, then recreate it with the same name and correct data type, making sure the default value is numeric. After adding it back and saving the report, Report Builder should update its internal XML, allowing the dataset to run without errors. If problems persist, check the report’s XML code for any missing or inconsistent parameter definitions and correct them as needed.
I hope this information is helpful. If you have any further questions, please let us know. we can assist you further.Regards,
Microsoft Fabric Community Support Team.
- v-karpurapud
Hi Egks
I wanted to check if you’ve had a chance to review the information provided. If you have any further questions, please let us know. Has your issue been resolved? If not, please share more details so we can assist you further.
Thank You. - v-karpurapud
Hi Egks
We have not received a response from you regarding the query and were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank You.
