Forum Discussion
User input parameters for direct query
Did you find a way to make this work? Having the same problem to solve.
- Anonymous1 year agoNot applicable
Not the way I really needed/wanted it to no.
It seems I need to have reference data tables existing for all possible directquery input parameter values so I can bind a column in those tables to the parameter value when one is selected (can't simply use a datetime picker to supply any value as nearly all other tools it would seem support for parameter inputs to queries).
It would also appear that limitation applies to any sort of text box input you might want to use in directquery queries (search pattern strings, etc). Basically you're picking values from a reference data table only, so it doesn't seem to me you can do any of that with Dynamic DirectQuery M parameters since in effect all of them are really based upon picking a value for a parameter bound to reference data columns.
- lbendlin1 year agoSuper User
Keep in mind that a user interacting with a slicer for a Direct Query sourced column will do this anyway - they can enter advanced search terms like "contains" and most of the time this will result in a folded query back into the data source.