Forum Discussion
Facing one issue while binding M Query parameter in Slicer
Dear v-karpudapur
Thank you for the reply. For workaround purpose I created one solution where I made a relationship with my main view with selector table so that when Name is selected from main visual (main view) the child and selector visual is showing the ID which is bound to parameter. Now I made ID field background color and text color as Blue so that ID is not visible and when user click on the record then target visual shows data target visual is based on Power M-Query and where condition is the kept as ID=p_Bind_param. But htis is a work around because the selector table is showing one record from visual but when click that record due to filter context the selector table get populated. All though I made selector table tiny so that always one record is displayed but scroll is coming here. I can say it is just a workaround not a concrete solution as per professional look. However actual problem has been taken care with drill through features also alternate introducing buttons in the page can control the execution of the visuals for optimumperformance. But I was exploring the pushdown technique with M-Parameter which is very strong but have a hard limitation. If Microsoft fill this gap that the parameter then most of the users have a huge benefit in direct query performance perspective.
I mean to explain inlittle detail that ID is bind with parameter , ID and Name are kept in selector table so if any facility will be provided that field associated with bind parameter can use the associate name column in slicer whe slicer is selected internally it captures the ID and passed it to M-Parameter to do dynamic push down more efficiently.
Again Thank you very much for your support .
Regards
Jishnu Bhattacharya
Hello jishnubhattacha
Thank you for the additional details.
The scenario you described is a bit different from the original parameter-binding limitation. Here, it's important to check if selecting a Name in the table visual creates a valid single-value filter context on the parameter-bound ID column.
It would be recommended to verify whether the table visual interaction is propagating the required filter context to the bound ID field. If the ID column receives a valid filter context through the visual interaction, Dynamic M Query Parameters should be able to react to that change and trigger query pushdown automatically.
As this behavior depends on how the filter context is applied to the parameter-bound column, further testing is needed to see if the visual interaction provides the filter context required for parameter evaluation and query pushdown.
If you have any further questions, please let us know. we can assist you further.
Regards,
Microsoft Fabric Community Support Team.
Thank you Team,
If I will provide you the situation would you please like to help me. My intention is to get almost alternatives which can cater the business scenario if any performance are reported. So far I explored this feature has a potential to serve performance related affairs which we find in different queries regarding Direct Query related matters.
Regards
Jishnu Bhattacharya
Absolutely. If you can share the business scenario, data volume, model design, DirectQuery source, number of visuals, filters/slicers, and the specific performance challenges you are observing, it would be easier to understand the requirements and discuss possible approaches.
As you have already demonstrated through your testing, Dynamic M Query Parameters can be a powerful option in certain DirectQuery scenarios. However, depending on the requirements, there may be other approaches worth considering as well, such as drillthrough, composite
models, aggregations, query optimization, visual interaction control, or report design changes.Feel free to share the details of your scenario, and we can discuss which options might best fit your requirements.
Regards,
Microsoft Fabric Community Support Team.
Hi jishnubhattacha
Just checking in as we haven't received a response to our previous message. If you have any further questions, please let us know. We can assist you further.Regards,
Microsoft Fabric Community Support Team.
We were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank You.