Forum Discussion

User2531's avatar
User2531
New Member
11 days ago

Automating Auto Date/Time Configuration for Semantic Model

How can one use an explicit enterprise Date table and to avoid Auto date/time in shared semantic models within Microsoft Fabric, without requiring developers to manually disable the Auto date/time feature in Power BI Desktop? The goal is to reduce unnecessary date/time tables and semantic model size while ensuring all date-related filtering and time intelligence use the central enterprise Date table. Is there a supported way to enforce or automate this configuration?

3 Replies

  • v-csrikanth's avatar
    v-csrikanth
    Icon for Community Support rankCommunity Support

    Hi User2531​ 
    There's no tenant setting, Group Policy, or registry key that disables Auto date/time organization-wide. Both Desktop options are local. Global applies only to files created afterwards, Current File only to the open file. So this has to be enforced structurally:

    1. Live connections to a shared model the only true prevention

    Report authors connecting live to your enterprise semantic model can't modify the data model, so they never generate Auto date/time tables. Grant Build permission and make thin reports the default pattern.

    1.  PBIP + Best Practice Analyzer in CI/CD, the enforcement point

    For teams who need their own models, Microsoft publishes build-pipeline guidance for Power BI projects, and the default BPA rule set includes [Performance] Remove auto-date table, which flags calculated tables named DateTableTemplate_ or LocalDateTable_. Fail the build on that rule and non-compliant models stop before deployment.

    1. Service remediation (per model)

    With write permission on the model: Model view → Switch to Editing mode → File → Options → Time intelligence → Auto date/time.

    Two caveats it's per-model with no bulk option, and republishing the PBIX from Desktop overwrites the Service values. Treat it as remediation, not enforcement. Check before flipping it on an established model: removing the hidden tables breaks reports and DAX that reference those hierarchies.

    1. A standard .pbit template

    Useful, but a convention rather than a control it only helps developers who actually start from it.

    Finally, mark the enterprise Date table as the model's Date table so time intelligence resolves against it.

    In short: central Date table + live connections to shared models + BPA validation in CI/CD + standard templates.

    References:
    https://learn.microsoft.com/power-bi/guidance/auto-date-time
    https://learn.microsoft.com/power-bi/transform-model/desktop-auto-date-time
    https://learn.microsoft.com/power-bi/transform-model/service-model-options
    https://learn.microsoft.com/power-bi/developer/projects/projects-build-pipelines
    https://github.com/microsoft/Analysis-Services/tree/master/BestPracticeRules
    https://learn.microsoft.com/power-bi/guidance/powerbi-implementation-planning-user-tools-devices

    Thanks,
    C Srikanth
    Community Support Team

  • v-csrikanth's avatar
    v-csrikanth
    Icon for Community Support rankCommunity Support

    Hi User2531​ 

    We would like to inquire whether have you got the chance to check the solutions provided by other users in community to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

  • v-csrikanth's avatar
    v-csrikanth
    Icon for Community Support rankCommunity Support

    Hi User2531​ 

    We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

    Thank you.