Date Hierarchy

Hi kasun_rumesh ,

Thank you for reaching out to the Microsoft Community Forum.

In Power BI Desktop for both Import and DirectQuery, the Auto Date/Time hierarchy is generated automatically per date column. Anomaly Detection requires this auto hierarchy, custom hierarchies do NOT work.

In Power BI Semantic Models (Fabric), the below features are not supported.

1. Auto Date/Time hierarchy, Even if the global setting is ON , Fabric models ignore it.

2. Auto-Generated Hidden Date Table, Auto date table is not created, the auto hierarchy cannot exist.

3. Since the semantic model does not create it, anomaly detection cannot slice by Year/Month unless the hierarchy is the auto-generated one.

That's the reason, You see the Date Hierarchy 2. You don’t see the native auto-generated hierarchy. Anomaly detection does not work properly with custom hierarchy. The hierarchy is not visible in Model view, expected auto hierarchies are hidden.

Note: Auto Date/Time is supported only for Power BI Desktop Import or DirectQuery models, not Fabric Semantic Models.

Please try below workarounds.

1. If anomaly detection is a must, Build the model as a Power BI Desktop Import model. Publish it to a workspace not as a Semantic Model. This restores Auto Date Table, Auto Date/Time Hierarchy and Full anomaly detection support.

2. Use report-level anomaly detection in Desktop, It Works only if visual uses A Date column, A numeric measure. But the hierarchy still must be auto-generated , not supported in Semantic Model.

Note: If you need Year/Month anomaly detection, Build or duplicate your model as a Power BI Desktop Import model. Publish that version for reporting. Semantic Models simply do not support the needed auto date hierarchy.

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh