OneLake data hub, data source not recognizing date columns and building hierarchies

[Gabe_Weathers]

Hi, I am creating a power BI report using the new features that allow you to use microsoft data lakes as a data source using the desktop app version: 2.128.751.0 32-bit (April 2024). With the data lake connection the semantic model and relationships between tables is also imported but unable to be edited after the fact. In my previous power BI reports with simpler data source such as an excel file I would build a date matrix or table inside of the report using DAX code and use this table for all time series plots or YTD measures and it worked beautifully. My issue is that when importing a data lake dataset into Power BI it does not recognize any of my date columns like it used to. They are all properly declared as date column in the model, yet it does not generate a date hierarchy for me. If I try to build the hierarchy on my own in the semantic model it cannot recognize string names of the months, quarters, or days of the week as a time series, so I tried integers which works but I have to sort every graph because it still does not recognize a time series.

Another functionality I have lost with this cluncky infrastructure is the ability to dynamically adjust the date range of my contiguos calendar to match the max and min dates of my data that has duplicate dates and holes in the time series. This means I can no longer do YTD and PYTD calculations in my measures because the contiguos calendar does not match the actual date range.

I have tried dozens of solutions to create a proper date matrix using python code and data flow gen 2 yet had no success getting the data types to be maintained when importing to Power BI. If anyone has any suggestions they would be much appreciated.

Here is the data type of my date column.

Data types when viewing the table from microsoft fabric semantic model file. 

How the integer hierarchy appears, instead of being recognized as a time series: 

[amitchandak]

@Gabe_Weathers , I have created TI(Time Intelligence) measures many times in the Lakehouse and Warehouse semantic model.  There is an option to mark the data table as a date table in the Semantic model, you can try that. Ideally for TI, I would not like the date hierarchy to work.

Is Hierarchy an issue or TI an issue?

Create Date table Dataflow Gen2, use in Lakehouse, Warehouse| Time Intelligence

https://youtu.be/g3BEVXQdk-g