Forum Discussion
Report Builder - Issue with line chart average
- 10 months ago
Hi Danny2020 ,
Thanks for reaching out to the Microsoft fabric community forum.Firstly to fix the error, In Report Builder and make sure the Name matches the DAX variable name exactly for example, use @Part_Number instead of PartNumber. Then, in the Parameter Value field, link it to your report parameter by setting it to =Parameters!PartNumber.Value. This ensures that the DAX query recognizes and correctly applies the parameter value passed from the report.
Additionally, make sure the parameter data type matches the column type in your model. If 'Database'[Part Number] is a text field, the report parameter should also be defined as text, if it’s numeric, then the parameter type must be numeric as well. Mismatched data types can prevent the filter from applying correctly and cause the query to fail.
I hope this information helps. Please do let us know if you have any further queries.
Thank you
Thank you GrowthNatives . I modified the main Database query to include other columns. The idea is to have 4 line charts, each with the actual of the test, and the spec given from a third table "Specs". I could get an average of the actual in a calculated series in each chart. The parameter Part_Number should filter each chart.
EVALUATE SUMMARIZECOLUMNS('Database'[Date], 'Database'[Part Number], 'Specs'[Test1Spec)], 'Specs'[Test2Spec], 'Specs'[Test3Spec)],'Specs'[Test4Spec)],'Database'[Test1], 'Database'[Test2],'Database'[Test3],'Database'[Test4],
FILTER('Database', 'Database'[Part Number]=@Part_Number))
Validating the query, it has an error: "The query contains the 'Part_Number' parameter, which is not declared".
In the Dataset properties menu, I added the parameter PartNumber as a name, and in parameter value @Part_Number, from the second query:
EVALUATE SUMMARIZECOLUMNS('Database'[Part Number])
Any idea of what is causing the error?
Hi Danny2020 ,
Thanks for reaching out to the Microsoft fabric community forum.
Firstly to fix the error, In Report Builder and make sure the Name matches the DAX variable name exactly for example, use @Part_Number instead of PartNumber. Then, in the Parameter Value field, link it to your report parameter by setting it to =Parameters!PartNumber.Value. This ensures that the DAX query recognizes and correctly applies the parameter value passed from the report.
Additionally, make sure the parameter data type matches the column type in your model. If 'Database'[Part Number] is a text field, the report parameter should also be defined as text, if it’s numeric, then the parameter type must be numeric as well. Mismatched data types can prevent the filter from applying correctly and cause the query to fail.
I hope this information helps. Please do let us know if you have any further queries.
Thank you