The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I've enabled the "Field parameters" preview feature in settings. I've followed the instructions to modify an M-based Power Query of a Table to work with a Parameter - which I can set by hand and works perfectly. I then create a one column table of string values which i'd like to bind to that text parameter. When I select the field in the text values table and select Properties > Advanced, no bind options are surfaced. Steps taken:
String parameter VendorSKU set. Queries work for any value I put in the parameter.
Table of string values created to act as slicer.
Now to bind the slicer to the parameter - oh, where has the field to achieve this gone?
Any ideas how I can get the bind section in Advanced to show, in order that I can bind the slicer to the parameter?
Solved! Go to Solution.
Hi @IanWaring ,
If you want to use dynamic M query parameters, then make sure that the data source you are referencing the parameters from (i.e. table InvoiceFocus) is using Direct Query mode.
For more information, please refer to: Dynamic M query parameters in Power BI Desktop
If the problem is still not resolved, please provide detailed error information or the expected result you expect. Let me know immediately, looking forward to your reply.
Best Regards,
Winniz
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @IanWaring ,
If you want to use dynamic M query parameters, then make sure that the data source you are referencing the parameters from (i.e. table InvoiceFocus) is using Direct Query mode.
For more information, please refer to: Dynamic M query parameters in Power BI Desktop
If the problem is still not resolved, please provide detailed error information or the expected result you expect. Let me know immediately, looking forward to your reply.
Best Regards,
Winniz
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I was Importing the data rather than leaving the connection open in DirectQuery mode. Sum result is i've accepted defeat in my quest to use different length part number prefixes used as slicers in a report; I can't issue a query on slicers "HEXHEX21", "SASSAS20" and "ESRIESRI20" on an imported data source. So i've given folks 3 separate reports, one prefix each.
If it makes a material difference, the data source is a Synapse SQL table from a Microsoft Data Lake fed from Dynamics 365 Finance.