Hi guys . I am having an issue with a Financial report in D365 F&O. Its for budgets for 2024: when i run the report in the front end i get this error :
When I open the designer i notice that the base year is set for 2023, when i try to change it , it will not switch to 2024. I changed it and hit save, but the report defaults back to 2023:
any idea why this is happening and how do i fix it ?
I would try a Data mart reset if you haven't done that yet. It's likely not an issue with the way 2024 was setup or users would be seeing odd behavior in transaction processing.
@Hana Xue i have checked these and can find no issues at all. The one thing i noticed is that if I run the same date range across the other financial reports for 2024/12/31 i'm now getting the same issue/error. So it seems to be linked to what can only be the financial periods. All the reports run perfectly for the 2023 period, but when run for 2024 I get this error.
@Frank I did make the change you suggested and it returned the same error shown above. I'm concerned that it may have something to do with the way the finance department created the 2024 financial and ledger periods, but I can not find any issues with the creation or setups. i must be missing something here
Hi, Have you checked according to the prompt information? What does the fiscal year look like in your column definition? In addition,what makes Base Period and Base Year exceptional is that you can run a report over them right before the report is rendered and it is not saved within the report definition.The Default Base Period setting determines the initial settings for the Base Year and Base Period. This is the only setting that is saved with the report definition.
Hi team , the fiscal periods are created and are open . As for the default base period, I do not have an S period, but I do have an S+1 which I changed it to, re-ran the report, and still the same error is being generated . Any other ideas will be greatly welcomed
Can you please try after to change the default base period to S
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.