Forum Discussion

HamidBee's avatar
HamidBee
Icon for Power Participant rankPower Participant
4 years ago
Solved

Cascading Report in Power BI Report Builder Causing Errors

Hi,

 

I have been trying to create a report on Power BI Report Builder with three cascading parameters. It has three parameters in this order: Nationality, Team and Name. When I run the report I keep getting an error which reads 'Failed to preview report'. Here is a link to the file:

 

https://www.mediafire.com/file/eodvxa55lmzk1o2/Cascading_Problem.rdl/file

 

Any help would be greatly appreciated. 

 

Thank you,

  • You cannot have NAME as parameter. It is a reserved word.  

     

    Try changing to "Param_Name" or "NAME1" or "NameParam" and keep the prompt as "Name"

     

    Apply to the dataset filter the same change and see if it works!

4 Replies

  • You cannot have NAME as parameter. It is a reserved word.  

     

    Try changing to "Param_Name" or "NAME1" or "NameParam" and keep the prompt as "Name"

     

    Apply to the dataset filter the same change and see if it works!

    • HamidBee's avatar
      HamidBee
      Icon for Power Participant rankPower Participant

      Thanks for the help. I had no idea reserved words existed. Thanks for mentioning it. Would these words fall under SQL reserved words or Power BI Report Builder?. 

      Also, I wonder should I be posting my questions in the 'Report Server' forum or is 'Desktop' more appropriate?.

      • sevenhills's avatar
        sevenhills
        Icon for Super User rankSuper User

        You are right, preferred to post is in the Report Server forum, as that is more appropriate.

         

        In any language, the usage of syntax words or collection of objects are reserved and similary I believe it is in Power BI Report builder / SSRS aka RESERVED word. Examples: Name, Value, Parameters, Globals ...

  • The immediate error is the following:

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

    The quickest solution is to change the parameter to uppercase NAME (rather than Name).