Model Calendar update
I have one model where we have 5 years of Past and Future period set up. The year roll over happens on 1st Feb. (Feb to Jan year rollover)
Now at the latest year rollover on 1st Feb 25, I have increased the current fiscal year by 1 year so that the new year will be available for the data load. (The Calendar year has ended on 31st Jan25). Hence the past 5 year has also moved ahead by 1 year.
Now the users said they want to keep the old Current fiscal year and didnt want the past year to move ahead. What approach should I follow to move back.
1. I have kept the back up model of 31st Jan 25 in test sandbox environment. Should I make that production model and run the data load for last 8 days of Feb in that model.
2. Should I restore the main production model to the stage where I made the year change.
Please help
Answers
-
Hello,
It sounds like restoring the main production model to the stage before the year change would be the most straightforward approach. This way, you maintain the continuity and avoid any discrepancies. Wakeid portal loginRestoring the backup model from the sandbox and running the data load for the last 8 days is also an option, but it could involve additional steps and verification.
Option 2 is simpler and cleaner.
Best Regards,
Peter Philip0 -
Provided not many changes have been made by users since the roll (or extracts are taken in advance), Option 2 is the better approach, if possible.
The risk of Option 1 is that you'll also lose all audit/change history as model copies & backups do not retain history. Also, depending on your integration methodology, you may also need to update model IDs and source model references as the copy will have a different ID (assume it'll be in the same workspace).
0 -
Thanks for your advice. I will go with the 2nd option and then load the data for last 8 days in Prod model.
0 -
In these cases, I think it's safer to recover the old historical data from the 6th mising year.
I would also check these steps:
- Change and add in time-settings the old year in the current model. the old year will not contain any data.
- go in the copy model and export data of the year that is missing
- go in the current model and import data of the missing old year
It's also need to consider of how many modules you need to export and recover data for the missing old year…
Not sure what's easier… recover and arrive at the same results of the last x days modifications in the current model (for which I think it's more usefult to maintain the history log)…or recover the old data of 1 old year.
Hope it helps,
Alex
0 -
Thanks for your response. I am following this step to resolve this
0