Problem:
Currently, Power BI does not provide a native option to define a custom Fiscal Year (e.g., April–March). Users have to manually create DAX logic or custom date tables in every report, which leads to:
- Inconsistent fiscal definitions across reports
- Repetitive development effort
- Increased chances of errors
Proposed Solution:
Introduce a built-in Fiscal Year configuration option where users can:
- Define fiscal start month (e.g., April, July, etc.)
- Automatically generate Fiscal Year, Quarter, and Month fields
- Use these fields seamlessly with time intelligence functions
Expected Benefits:
Standardized fiscal reporting across datasets
Reduced dependency on custom DAX / date tables
Improved governance and consistency
Faster development and onboarding
Use Case:
Organizations working with non-calendar financial years (common in India, UK, etc.) can directly leverage fiscal calculations without additional modeling effort.
lbendlin
on:
Fabric Copy Activity Upsert Needs Native Audit Col...
on:
Power BI Subscriptions enhancements sorely needed
on:
Ragged Hierarchy Display options in Matrix Visual
miguel
on:
Personalized Source List in Get Data