Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Description:
I created 2 parameters and 2 date tables in the power query. Then I created a between-date slicer and use one of the date-tables. Before binding the table and the parameters together in the model, I notice that the slicer options look like this . After binding the table with the parameters, the slicer option changes to this . Then it gives me this error . The error disappeared when I changed the slicer type to list or dropdown. Then my options reduce to .
Issue:
My problem is that I am working with a large data set and the user does not want to scroll through the dates of the years options to select a date. It will be okay if the user can type in the date but neither the list more the dropdown option allows such interaction. What can I do to improve user experience in this case?
Your help is appreciated. Thank you in advance.
Solved! Go to Solution.
Hi @adegokeopeoluwa ,
According to your description, slicer does not support direct user filtering by manual input.
Usually for date fields, it comes in a variety of formats, so you can't control which date format the user's input is in that powerbi can recognize.
My suggestion is that you can create a hierarchical structure by using a combination of multiple slicers in a way that reduces the user's scrolling to find them.
If the problem is still not resolved, please provide detailed error information and let me know immediately. Looking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @adegokeopeoluwa ,
According to your description, slicer does not support direct user filtering by manual input.
Usually for date fields, it comes in a variety of formats, so you can't control which date format the user's input is in that powerbi can recognize.
My suggestion is that you can create a hierarchical structure by using a combination of multiple slicers in a way that reduces the user's scrolling to find them.
If the problem is still not resolved, please provide detailed error information and let me know immediately. Looking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
User | Count |
---|---|
84 | |
69 | |
69 | |
65 | |
54 |
User | Count |
---|---|
93 | |
93 | |
91 | |
76 | |
69 |