Use Case of Dynamic M Parameters

[powerbiexpert22]

I am not clear about use case of Dynamic M Parameter, i have gone through below video however i am not clear in which sceanrio i should use it. what i understand is Dynamic M parameters are used in case of direct query and we can refer the parameter value in Query however i think if we just want to filter the data then we can use filters or slicers in report itself

https://www.youtube.com/watch?v=rFI6pc94WdM

[v-sshirivolu]

Hi @powerbiexpert22 ,
I would like to take a moment to thank @Thomaslleblanc  , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions

[v-sshirivolu]

Hi @powerbiexpert22 ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you

[Thomaslleblanc]

yes, you can just use a filter or slicer to accomplish the same thing. They are using a Direct Query example for the use of passing a parameter to the source database to only retrieve a sub-set of the data.

[Thomaslleblanc]

After diggin a little more, I think the main objective of Power Query parameters, dynamic M, is to help pass parameters from a deployment pipeline to change the servername and database name for Dev versus QA versus Prod. This example in the 2 videos I watched were shwing a table (with a unique list) passing the selected value to the parameter, thus filtering the table. 

It is just an example, to show how it can work. This is not necessary a common use of the parameter.

[Thomaslleblanc]

The video is just showing an example, using DirectQuery. That is not a requirement for using M Parameters