Forum Discussion
Dynamic M query with arbitrary values
Hi rnola16,
Thank you for reaching out to the Microsoft Fabric Community Forum.
You're on the right path using dynamic M query parameters in DirectQuery mode. Since you're passing values like birth_dt and ssn, here are a few ideas that might help troubleshoot:- Make sure both parameters are correctly linked to slicers using dummy dimension tables. This is essential for dynamic input from the report UI.
- Double-check that the names of the parameters you're using throughout the query are consistent mismatched names can cause unexpected behaviour.
- Confirm that Power BI can fold the filters back to the source system. If the filtering isn't being pushed down to the database, the dynamic behaviour may not work as expected.
- It's generally recommended to avoid directly embedding parameter values into custom SQL strings for both security and performance reasons. Power BI handles parameters more effectively when they’re passed and processed using native filtering.
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
Hi rnola16,
Thank you for reaching out to the Microsoft Fabric Community Forum.
You're on the right path using dynamic M query parameters in DirectQuery mode. Since you're passing values like birth_dt and ssn, here are a few ideas that might help troubleshoot:
- Make sure both parameters are correctly linked to slicers using dummy dimension tables. This is essential for dynamic input from the report UI.
- Double-check that the names of the parameters you're using throughout the query are consistent mismatched names can cause unexpected behaviour.
- Confirm that Power BI can fold the filters back to the source system. If the filtering isn't being pushed down to the database, the dynamic behaviour may not work as expected.
- It's generally recommended to avoid directly embedding parameter values into custom SQL strings for both security and performance reasons. Power BI handles parameters more effectively when they’re passed and processed using native filtering.
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
Hi rnola16,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please accept it as a solution and give it a 'Kudos' so other community members with similar problems can find a solution faster.
Thank you.