Paginated Report Builder - bug showing unrelated parameter error message for various errors

[garythomannCoGC]

Parameter related error always refers to first parameter of parameters list regardless of which parameter is causing the error.

The error text:

The Value expression for the query parameter 'ParameterName' refers to a non-existing report parameter 'ParameterName'. Letters in the names of parameters must use the correct case. etc '

Report Builder - bug showing which parameter is giving name change error, always refers to the first... 

Please up vote the bug above

[garythomannCoGC · Accepted solution]

The query contains the XXXXXName parameter, which is not declared. SSRS2008/MDX query 

Add this link to remind that there is also the hidden query (ie original copy) in Query Designer which can stuff up your day :}

No changes needed just open up Query Designer from properties for the query in question and parse the QD copy.

[garythomannCoGC]

Cross link this foum title back to the forum post below where the situation arose.

Report Builder - bug showing unrelated parameter error message for various errors 

Web search on "report builder" "validate query"  does not come up with many hits hence the separate forum post.

[garythomannCoGC]

I know that the parameters are setup correctly.  And that the parameter error below is a 'furphy'.

The fix will be to make sure that all the columns and naming match the underlying query ... with no help from m$ in the error message ... Dr Watson I presume!

+ dax query works

+ check that query columns match to report query column list

+ check that parameters exist and match dax query to report parameter list

+ check that report parameter list in same order as dax query declarations  ( you never know ?)

+ check the report query dataset parameter declarations list matches and have their associated join's

+ report parameter properties are fully filled out and with matching parameter dataset query

+ parameter dataset queries do run

+ changed focus from Validate Query within the main query to running the report and fixing errors from that side

> wierd, report first gave the screenshot error above when running but now runs and the Validate Query button for the main dataset still bombs with the above screenshot error ... wtf

[garythomannCoGC]

Undocumented error.  Report will not run after this error.  Need to close down and start again.

[garythomannCoGC]

Change post title from  'Report Builder - bug showing which parameter is giving name change error, always shows first parm'  to  'Report Builder - bug showing unrelated parameter error message for various errors'  to better reflect the situation(s)

[garythomannCoGC]

Hi @v-cazheng-msft,  great timing just adding a video from yesterday that shows another similar situation.

These parameter error messages are used a lot for errors.  Is the default when a specific error path is not found perhaps?

error video 

What do you mean by 'repro' ... reproducable (error situation)? 

Note to fix

1) change query field list name first

2) then change the actual query

3) then change the matrix object reference

> very manual,  other reporting tools have the smarts to follow this through

Annual Status parameter has nothing to do with the column name change.

> add new column has same effect

Note to fix

> same story need to add the field manually

> then go Ok

> do not use the Validate Query button

> run the report, if all ok it runs otherwise error

[garythomannCoGC]

Hi @v-cazheng-msft, thanks for your reply and questions.

Report Builder.  Easy to reproduce just take any working report.  Change the name of any 2+ placed parameter ... and it works.  Showing the correct parameter name.

Just tried various ideas on how to reverse engineer to replicate and no go.  Must be something else at the time.  Was changing a lot of the code in the dax query and getting frustrated with the unhelpful error message.

Next time it happens will take a video.

Thanks

[v-cazheng-msft]

Hi @garythomannCoGC,

Thanks for  your reply! Got it and this issue couldn’t be repro now. If you encounter this issue in the future, please let me know. Thanks a lot!

Best Regards,

Community Support Team _ Caiyun

[v-cazheng-msft]

Hi @garythomannCoGC,

May I know whether this issue takes place in Report Builder or Power BI service? Could you please tell me the steps to reproduce this bug? Or if it is convenient, could you please provide a download link of a sample rdl file that contains this bug so I can investigate on it and report it internally to accelerate the fix for it? Thanks in advance!

If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly. If I misunderstand your needs or you still have problems on it, please feel free to let me know. Thanks a lot!

Best Regards,

Community Support Team _ Caiyun