Anomaly detection and date hierarchies

[PowerfulBi]

Please correct me if I am wrong regarding the below, and/or advise the correct methodology.  

For the purposes of this question, assume:  

1.  I have a date table  (and it is marked as a date table).    I also have one fact table (with a ship date column).  Relationship is between date and ship date.

2.  In the date table, I have created via DAX the columns for month, year, quarter and day.   And created a hierarchy.  

I have auto date time turned off  (but see below).   

Using a line graph,  I can ONLY invoke anomaly detection using the "Date" field or the Ship Date field.   If I try to use the date table hiearchy, anomaly detection is not able to be selected.

HOWEVER.   If I turn off auto date time, and use the hiearchy that gets automatically created for the ship date in my fact table, then I can use this hiearchy.   

But is it not indeed best practice to NOT use auto date time?   And in doing so, you lose the automatic hiearchy that gets created when this option is switched on.   And if there is no date hiearchy, you just have a "date" on the X axis, and there is no ability to drill down to different date hiearchies (whether using the date table "date" field or the fact table's ship date field).

This seems a bit counterinturtive and confusing.   

[grazitti_sapna]

Hi @PowerfulBi, 
I hope these pointers mentioned below would help you.

• Yes, it’s best practice to turn off Auto Date/Time and use a custom Date table.
• For anomaly detection, use a single Date column rather than a hierarchy.
• Manually add hierarchy levels to visuals to maintain drill-down functionality without enabling Auto Date/Time.

This balances best practices with the specific needs of anomaly detection and hierarchy functionality. Let me know if you'd like a walkthrough on setting up the hierarchy manually!

🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.

💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.

🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.

🔗 Curious to explore more? [Discover here].

Let’s keep building smarter solutions together!

[Ilya_K · Accepted solution]

Hi,

Indeed "Drilling down to go to the next level in the hierarchy isn't supported."

https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-anomaly-detection#consider...

If you know why it is the best practice to turn off auto date time, than you can asses your priorities.

Convinient visualization, possible reduction in performance and increase in the size of model or vice versa.

You can keep auto date time off and use several visualizations to detect anomalies with diffeerent value on axis X (Year, Month etc). You can also think about making a Bookmark for example, to switch between of them if necessary.