I have been exploring the new Enhanced DAX Time Intelligence feature (Preview), and I find it very promising. However, I was surprised to see that the functionality does not account for tertials.
For those unfamiliar, a tertial is a four-month period (3 × 4 months = 12 months). This way of dividing the year is commonly used in several organizations, especially in Europe, for planning, reporting, and performance management. It strikes a balance between the granularity of quarters and the broader perspective of halves.
Being able to analyze data by tertial is valuable because:
Many companies structure their budgets and forecasts around 4-month periods.
It provides a natural cadence for performance reviews and business follow-ups.
It helps align reporting cycles with internal business practices, rather than forcing the data to fit quarters or halves.
At the moment, achieving this requires custom calculations and workarounds. Including tertial support directly in Enhanced Time Intelligence would make the feature far more flexible and aligned with real business needs.
I strongly suggest considering tertials as a supported period type in future updates. It would be a relatively small addition with a significant impact for organizations that rely on this reporting structure.
makromer
on:
Fabric Data Pipeline should be able to execute dbt...
on:
Customers should ereceive notifications for all th...
miguel
on:
Recent Data and Recent Connections