The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
So I've been out of PowerBI for a while and am just getting back. I'm now getting a behavior that I can't quite figure out.
So, baseline.
Create a Calendar table with
So now the issue. In the past I've been able to throw any old date field in and be able to create a slicer from it. Tried that today and get nothing. I get a slicer based on the heiarchy, just not a date slicer.
Data type is set as a date:
Shows in the fields as a date:
Shows in the table as a date:
To make it even wierder, I have a date slicer from another date that was already in the PowerBI, that works as I expect. If I drop that same date field into the PBI again, and try to set it up as a date slicer, it doesn't work.
So like I said, I've been out of PowerBI for a while so don't know if this was an update that changed the way they work or what? I'm sure I'm just missing something stupid and small. Any help here is appreciated.
Solved! Go to Solution.
HI @Telenar,
Did you mean to add a date field to your 'between' mode slicer and it will switch to hierarchy mode instead of common date slicers?
If that is the case, I think it may be related to the date hierarchy. Power bi may add optimization with this scenario(add the same date field multiple times to the same slicer) and will try to analyze and convert them to the different granularity of hierarchy levels.
You can also right-click on the current hierarchy slicer date field to convert date field to common mode to restore the default slicer.
Regards,
Xiaoxin Sheng
Please check if you have selected Hierarchy or the Date field. If you have selected the date hierarchy then it is not allowing to change the style to between. If you see the screen shot below the date field has date hierarchy below.
Ok so confused but found a work around. If I drop the date in and then change it to a slicer I get the above behavior. If on the other hand I create an empty slicer and then drop the date on it, it works just fine. So I have a work around, but still would love to know why the old way (drop date in and change to slicer) no longer seems to work.
HI @Telenar,
Did you mean to add a date field to your 'between' mode slicer and it will switch to hierarchy mode instead of common date slicers?
If that is the case, I think it may be related to the date hierarchy. Power bi may add optimization with this scenario(add the same date field multiple times to the same slicer) and will try to analyze and convert them to the different granularity of hierarchy levels.
You can also right-click on the current hierarchy slicer date field to convert date field to common mode to restore the default slicer.
Regards,
Xiaoxin Sheng
User | Count |
---|---|
78 | |
74 | |
43 | |
32 | |
28 |
User | Count |
---|---|
104 | |
95 | |
51 | |
50 | |
46 |