Forum Discussion
User input parameters for direct query
This doesn't really truly answer the question. For Example:
- In terms of datetime user inputs, I would essentially have to build a table with all necessary dates and TIMES possible to allow for it to be selected from a list rather than typed or entered via calendar control? Remember there are potential time components to this, and no one wants to scroll down at a bare minimum 90 records if they just want to get data for the last 90 days because they're forced to use a pick list instead of typing in the date or calendar control.
- This doesn't address input of things in text fields (alphanumeric work order "numbers", email addresses, other various things that would be letters and numbers) it seems to me. This appears to be all based around strictly list based selection. If you have millions or even thousands of things to pick from this presents an impossible user experience.
I would essentially have to build a table with all necessary dates and TIMES possible to allow for it to be selected from a list rather than typed or entered via calendar control?
correct. That's how it is designed. If you want a different design please consider voting for an existing idea or raising a new one at https://ideas.fabric.microsoft.com
Remember that instead of using parameters report users can make extensive use of the filter pane which has all these capabilities.
Thanks, yes I'll head over there and make that suggestion.
In regard to the filter pane. It seems to me filtration is done after data retrieval (not pushed down or "folded" into query execution as a condition on the data source). I don't think anything done in that filters panel seems to be pushed down to the data source as conditions which is contrary to my entire intent. At least if I go to "view native query" it doesn't show any of the filter criteria. I think all that happens after retrieval.
See my earlier link for Dynamic M Query parameters - but that requires your data source to be in Direct Query mode.