Limitations of Custom Fiscal Year Support in CRM Analytics

Known Limitations

Custom Quarter Names are not supported.
In the Advanced Customization section of the Fiscal Year setup in Salesforce, the "Choose Quarter Name Scheme" setting must be set to "Numbered By Year". Select a Prefix from the available options. Using a custom quarter naming scheme is not recognized by CRM Analytics.
For guidance on configuring fiscal year labels, see Customize the Fiscal Year Labels.
Custom Period Names are not supported.
Similarly, the "Choose Period Name Scheme" setting must be set to either "Numbered By Year" or "Numbered by Quarter" with a supported Prefix. Custom period names defined in Advanced Customization are not recognized by CRM Analytics.
"fiscalMonthOffset" and "isYearEndFiscalYear" metadata overrides are ignored.
When Custom Fiscal Year support is enabled in CRM Analytics, any metadata overrides related to fiscal date handling in Dataflows (specifically the fiscalMonthOffset and isYearEndFiscalYear properties) are no longer applied to ingested data. If your org previously relied on these overrides to align fiscal dates, enabling Custom Fiscal Year support will change how fiscal date data is calculated in datasets.
Recommended action: Before enabling Custom Fiscal Year support in CRM Analytics, audit your existing Dataflow metadata overrides for fiscalMonthOffset and isYearEndFiscalYear. If these overrides are in use, test the impact of enabling CFY in a sandbox before applying it to production.