Please confirm - no date heirarchy for live connection to semantic models?

[pborah]

I think I already know the answer but since I have not been able to find anything conclusive in official documentation to convince my manager, I was hoping someone here can confirm (provided they have already verified this on their end) -

In a "Live" connection to a published semantic model in service using PBI desktop, the built-in date heirarchy feature is not available, correct?

Please note that I'm asking specifically about the "Live" type of connection and not "Direct Query" where I know date-heirarchy is not available. The semantic model was built entirely inside Fabric (to the extent possible) using a Fabric SQL db and not a dataflow or anything else. 

Additionally if someone can point me to the detailed list of limitations for "Live" connections, I'd greatly appreciate it, thank you. 🙏

[lbendlin · Accepted solution]

The auto date hierarchy mandates the use of a local model, something that is not possible in Live Mode.

What do you need it for, though?  General guidance is to switch that off as soon as possible, and to use the actual columns from the calendar table instead.

[Poojara_D12 · Accepted solution]

Hi @pborah 

You're absolutely right to seek clarity, especially when communicating technical limitations to stakeholders. In Power BI, when you connect to a published semantic model using a "Live connection", the auto-generated date hierarchy (also known as the built-in or implicit date hierarchy) is not available. This limitation applies regardless of whether the underlying semantic model is built on a Fabric SQL Database or any other source. The built-in date hierarchy feature in Power BI Desktop is automatically created for Date columns only when the model is imported or created within the same .pbix file—Power BI generates hidden date tables behind the scenes to enable this. However, once you connect live to a published semantic model, you're only consuming what has been explicitly defined in that model; Power BI Desktop no longer auto-generates anything additional, including hierarchies. Therefore, if the date hierarchy is needed in your visuals, it must be explicitly created in the original semantic model—either as a calculated table or as a defined hierarchy within a Date dimension. Microsoft does not prominently highlight this behavior in documentation, but it’s a long-standing known limitation of live connections.

As for a comprehensive list of limitations for Live connections, Microsoft provides general guidance in this documentation page, which mentions that implicit measures, quick measures, calculated columns, and date hierarchies are not available in live connections. However, the documentation often focuses more on composite models, so clear separation between "Live" vs "DirectQuery" limitations can be fuzzy. In your case, you’re correct—and it would be best to design your semantic model with explicit hierarchies and date logic built in if your users depend on that functionality.

[pborah]

@lbendlin @Poojara_D12 @rohit1991 @v-priyankata Thank you all for your responses and I truly appreciate you making the time. I was able to obtain confirmation from Microsoft support. 

@lbendlin we recently started rolling out semantic models to some of our data-skilled users for them to do their own reporting in the workspaces of their respective departments. It kinda slipped under my radar during my own testing and was brought forward by one such user. We are now going with either a calendar built into a model or having a master calendar as a separate model depending on the use-case.

Once again, thank you all.

[v-priyankata]

Thank you for letting us know. If you have any other issues, please reach out to the community.

[v-priyankata]

Hi @pborah 
@rohit1991 @Poojara_D12 Thanks for the inputs.

I hope the information provided was helpful. If you still have questions, please don't hesitate to reach out to the community.

[v-priyankata]

Hi @pborah 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

[v-priyankata]

Hi @pborah 

Hope everything’s going smoothly on your end. We haven’t heard back from you, so I wanted to check if the issue got sorted  If yes, marking the relevant solution would be awesome for others who might run into the same thing.

[rohit1991 · Accepted solution]

Hi @pborah,

When using a Live connection to a Power BI semantic model (dataset) in the Service, the built-in auto-generated date hierarchy (Year > Quarter > Month > Day) is not available in Power BI Desktop.

**Confirmed Behavior:

• Auto date/time hierarchies are only created for models built directly in Import mode within Power BI Desktop. In a Live connection, Power BI Desktop is just a thin client it reflects only what’s defined in the published semantic model. As a result, you will only see what has been explicitly modeled, such as calculated date columns or manually created date hierarchies in the dataset itself.

** Why It Happens:

• Auto date/time is a modeling feature, and Live connections do not allow local model changes.

• You are consuming a published dataset the metadata is fixed, and no new calculated hierarchies can be generated locally.

**Official Documentation:

While not always clearly stated in one place, you can piece this together from Microsoft docs:

• Auto date/time for new files – shows that this only works for new models in Desktop.

• Live connection limitations

**Workaround:

If you need date hierarchies:

1. Create them explicitly in the semantic model (in Power BI Desktop or Fabric Model View).

2. Consider building a proper Date dimension table with pre-defined hierarchy columns (Year, Month, etc.).

3. Alternatively, use DirectQuery for Power BI datasets if you need some modeling flexibility though that comes with trade-offs.

[Poojara_D12 · Accepted solution]

Hi @pborah 

You're absolutely right to seek clarity, especially when communicating technical limitations to stakeholders. In Power BI, when you connect to a published semantic model using a "Live connection", the auto-generated date hierarchy (also known as the built-in or implicit date hierarchy) is not available. This limitation applies regardless of whether the underlying semantic model is built on a Fabric SQL Database or any other source. The built-in date hierarchy feature in Power BI Desktop is automatically created for Date columns only when the model is imported or created within the same .pbix file—Power BI generates hidden date tables behind the scenes to enable this. However, once you connect live to a published semantic model, you're only consuming what has been explicitly defined in that model; Power BI Desktop no longer auto-generates anything additional, including hierarchies. Therefore, if the date hierarchy is needed in your visuals, it must be explicitly created in the original semantic model—either as a calculated table or as a defined hierarchy within a Date dimension. Microsoft does not prominently highlight this behavior in documentation, but it’s a long-standing known limitation of live connections.

As for a comprehensive list of limitations for Live connections, Microsoft provides general guidance in this documentation page, which mentions that implicit measures, quick measures, calculated columns, and date hierarchies are not available in live connections. However, the documentation often focuses more on composite models, so clear separation between "Live" vs "DirectQuery" limitations can be fuzzy. In your case, you’re correct—and it would be best to design your semantic model with explicit hierarchies and date logic built in if your users depend on that functionality.

[v-priyankata]

Hi @pborah 

Thank you for reaching out to the Microsoft Fabric Forum Community.

@lbendlin Thanks for the inputs.
As said by @lbendlin, When working with a live connection to a semantic model, the auto date hierarchy feature isn't available. This is due to the fact that auto date hierarchy depends on a local data model, which Live mode does not use.

Here is the document outlining the limitations for Live connections. Please review it.
Connect to semantic models in Power BI - Power BI | Microsoft Learn

Thanks.

[lbendlin · Accepted solution]

The auto date hierarchy mandates the use of a local model, something that is not possible in Live Mode.

What do you need it for, though?  General guidance is to switch that off as soon as possible, and to use the actual columns from the calendar table instead.