We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hi,
I am creating a report which uses tables from Azure Data Explorer(Kusto). How do I make duration as a parameter that can be changed in my Power BI Report if this is the query in Power Query Editor. (This query is only a representative of original query)
Solved! Go to Solution.
Hi @Anonymous
The following method is for your reference:
A prerequisite for using the following methods is that there must be a valid M query that uses one or more DirectQuery tables.
1. create parameters in Power Query
2. Referencing it in an M query
3. Create a table for each parameter containing a column that provides possible values that can be set dynamically based on the filter selection.
4. Bind the field to the parameter, the field type needs to be consistent with the parameter type, otherwise the option is not visible.
5. You can reference this field in the slicer or use it as a filter.
There is a potential security risk associated with this method, and you will be alerted accordingly when you bind fields to parameters. Avoiding string concatenation of M parameter values in the query reduces this risk.
The method also has some consideration and limitations:
For more details, you can read related document link:
Dynamic M query parameters in Power BI Desktop - Power BI | Microsoft Learn
Please feel free to let me know if I have misunderstood your needs.
Best Regards,
Yulia Xu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Anonymous
The following method is for your reference:
A prerequisite for using the following methods is that there must be a valid M query that uses one or more DirectQuery tables.
1. create parameters in Power Query
2. Referencing it in an M query
3. Create a table for each parameter containing a column that provides possible values that can be set dynamically based on the filter selection.
4. Bind the field to the parameter, the field type needs to be consistent with the parameter type, otherwise the option is not visible.
5. You can reference this field in the slicer or use it as a filter.
There is a potential security risk associated with this method, and you will be alerted accordingly when you bind fields to parameters. Avoiding string concatenation of M parameter values in the query reduces this risk.
The method also has some consideration and limitations:
For more details, you can read related document link:
Dynamic M query parameters in Power BI Desktop - Power BI | Microsoft Learn
Please feel free to let me know if I have misunderstood your needs.
Best Regards,
Yulia Xu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 54 | |
| 39 | |
| 32 | |
| 17 | |
| 15 |
| User | Count |
|---|---|
| 64 | |
| 63 | |
| 37 | |
| 36 | |
| 22 |