Forum Discussion
Creating date slicer removes data
v-hashadapu Thanks for your help.
I would consider this resolved. I can transform the data that is pulled into the model from DirectQuery as well. This is suitable for my needs.
v-hashadapu I would say that I have found a workaround for my issue.
I am still uncertain as to why my date table, when generated in the short date format, still pushes a query with a time stamp. What this seems to cause is selecting exact date + time combinations, where I do not care what time of day items were processed.
I am uncertain if this is a SQL or PowerBI-based issue that I am dealing with.
With that, I am uncertain if I would consider the core issue resolved, but I can move forward with my project.
Hi raschdieek , Thank you for reaching out to the Microsoft Community Forum.
The behaviour you arere seeing is expected because the Orders column is a datetime at the source, not because of the slicer or the Date table. Power BI always evaluates filters using the underlying data type, not the display format. Setting a column to Short Date only changes how it looks, it does not remove the time component or change how queries are generated.
So Power BI is not adding a timestamp or intentionally filtering by exact date time values. The timestamp already exists in the source data and becomes visible when slicer filters are pushed down. Transforming the column to a true Date during ingestion removes that time component, which is why your workaround works and is the correct fix when time is not relevant.
v-hashadapu Thanks for your help.
I would consider this resolved. I can transform the data that is pulled into the model from DirectQuery as well. This is suitable for my needs.
Hi raschdieek , thanks for the update. If you have any other queries, please feel free to create a new post here in the community. We are always happy to help.