Forum Discussion
Super UserUsing a Variable to filter CALCULATETABLE and SUMMARIZECOLUMNS
Sorry mark_endicott, I think we are confusing Direct Query and Dynamic M Parameters documentation. When you connect to an Oracle Database - direct query is available. In this scenario the slicer selections would be included in the Query sent to the Oracle DB (as the data is not imported).
The scenario you are referring is when Direct Query is not available but default (hence is suggest that SQL is not supported). This new feature allows you to bind parameters from the slicer into the M script required to pull the data from an API for example. I have not personally tried this approach though.
Super UserRight ok, I see where my confusion was. The reason I was trying to create a Summarized DAX table filtered on a value from a slicer (from a Direct Query table) was because the DQ table will have duplication in a relationship column that the slicer removes - hence I could remove a many to one join that needs to go in both directions as the summarized table would make this one to one.
I dont think a Power Query Parameter will help here.
Making the slicer on the Direct Query table single select effectively makes the relationship one to one in any case, we were probably just trying to over engineer it in the name of perfection.