You are here:
Custom Fiscal Years Inheritance Troubleshooting and Considerations
When you inherit custom fiscal year settings from Salesforce to CRM Analytics, use these tips for troubleshooting and keep these considerations in mind.
Troubleshoot Custom Fiscal Years in CRM Analytics
Why don’t my datasets have custom fiscal year support?
If your datasets don’t support fiscal periods after you inherit custom fiscal years from Salesforce, run the dataset’s dataflow or recipe. Support begins after the dataflow finishes running.
Why doesn’t my dashboard filter have custom fiscal year options?
If your dashboard filter doesn’t give you the option of filtering by fiscal periods, run the dataflow for each dataset in the dashboard. Support begins after each dataflow finishes running.
It’s a new fiscal year, and suddenly CRM Analytics returns null for all dates?
If a date is out of range of a defined fiscal year inherited from Salesforce, CRM Analytics returns null. Define a custom fiscal year in Salesforce, then have CRM Analytics inherit it. Finally, run each dataset’s dataflow. After the dataflows finish running, CRM Analytics once again returns data instead of null values.
Considerations and Limitations
- Custom Fiscal Years are not compatible with these SAQL Statements:
- fill
- timeseries
