How to Dynamically update M Query Parameter based on SLICER or FILTERS in POWER BI || Bind Parameter

[@ibmyyc]

This tutorial was super helpful. Thank you so much. Upvoted and saved.

[@LearnDataAnalytics-11]

Glad it helped you!

[@learnwithkamran1149]

Nice

[@kebincui]

Brilliant tutoraial. Thanks for sharing ❤🌹👍

[@LearnDataAnalytics-11]

Thanks so much 😊

[@sanjanak9409]

one question... why not use country column directly as a filter? and set up interaction

[@nagagannamaneni]

thanks for the great video. My fact table in Kusto has more than 1 Million records, so it is failing during the source connection even in direct query mode. I am thinking to write a query to get the data for one person during the source connection query and then change it later with a different person name dynamically by passing parameter as in your video. Can you please let me know how we can achieve this ? thanks

[@rajaboyangari6076]

I have a matrix visualisation and date picker with slicer (slicer is using Calendar dates from current date to past 2 years). Now for my use-case upon selecting a particular date that date value needs to be passed to a power query parameter. This parameter is used inside my power query to filter the data for the matrix widget from the selected date on date picker. I have loaded the data into powerbi ftom snowflake and it’s not direct query. Can you suggest how to do the mapping from Dashboard slicer widget to power query parameter

[@sowjanyap3267]

Looking for the same.

[@SandipanSarkar-c8v]

finished watching

[@nickhalden4759]

firstly, thank you. This is the first time I’ve ever seen parameters in use. However, question: why would you do this? Isn’t it quicker/more efficient to just link the Dim and Fact tables together and create a slicer based on the Country column in the Dim table? I’ve never seen how Parameters can be used for any practical reason.

[@danlschmenkeman9462]

Makes sense for Direct Query.

[@sotork]

A Dim Table can have a list of unique values under scenario one, and another under scenario two. Instead of filtering and duplicating the query to preserve many-to-one cardinality, you can create a parameter and bind it to a slicer.

[@nagendrareddypeddireddy4577]

How can I use the parameters as prompts at Power BI Service report interface?

[@zugya5938]

Can this solution work on power bi server

[@jatothveeresh2381]

could please mention data in description

[@jeissondavidsuesca]

hi from bogota

[@UnlimitedNovelty]

I am doing same process but i am getting step results in a query that is not supported in direct querymode

[@johnkiziah8704]

I am getting the same errror. Is there a way around that?

[@galiceanugratziela9335]

same here. can we have an answer on that ?