Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Hello,
i noticed that the 'find anomalies' option gives out below error when i use a custom date hierarchy created via the Calendar function (whose year, quarter, month and date were also created via dax and the table was marked as date table):
This is what the visual looks like:
However, if i pull the default date hierarchy, the find anomalies option works--->below a similar visual as the one above but with default date:
Can we confirm that the 'find anomalies' option only work with a default date hierarchy?
Solved! Go to Solution.
We only support the default date hierarchy (with date as a scalar key), because anomaly detection requires a date at backend, unfortunately arbitrary custom date hierarchy or custom format etc is not supported, because PowerBI infra cannot figure out these fields' date-type scalar key.
I reproduced what you saw, and expect it is related to going from a continuous X axis to a categorical one (Date Hierarchy). I also tried it with a hierarchy made from EOM and EOY columns with custom format strings (mmmm and yyyy). Same error.
Pat
To learn more about Power BI, follow me on Twitter or subscribe on YouTube.
We only support the default date hierarchy (with date as a scalar key), because anomaly detection requires a date at backend, unfortunately arbitrary custom date hierarchy or custom format etc is not supported, because PowerBI infra cannot figure out these fields' date-type scalar key.
User | Count |
---|---|
136 | |
73 | |
72 | |
56 | |
55 |
User | Count |
---|---|
199 | |
95 | |
63 | |
62 | |
51 |