You must take a BIS database back up before you start this process.
You will need to ensure you update the tags for the MODULE_YEAR_CRM_C/P Tags and PROCESSING_YEAR_C/P to be 2024 for the Current year and 2023 for the Previous year.
All other MODULE_YEAR and PROCESSING_YEAR tags relate to other views.
Once the view is rolled over, and should not take long, you will need to run the refresh the data for the current year. 'Refresh CRM Task View CY' is the rule.
Steps
Open Authority - Admin Mode - BIS
Data Extraction - Tags
Update tags - Save
EOY Rollover tab
Select CRM Task (ONLY)
No. of years for CRM is 3
Select Run Rollover Now
Check that there are no Static Years on this list. If there are, update.
Select Next
Check that tags are updated..
Click Finish..
Ensure you have a database back up - tick the box then Yes
---------------------------------------------------------------------------------------------------------------
->Below EOY BIS report error occured- During the patch upgrade, the BIS API upgrade is typically performed automatically. However, in this case, the BIS API upgrade was skipped. As a result, CIVICA had to manually update the BIS API from the backend.
After that: As per CIVICA's request I have manually restored the backup in the BIS module in LIVE
- I have completed the restored backup for BIS successfully after business hours in LIVE.
- The first few times came with errors because some process was running behind. After the third attempt, it's done successfully,
- I've attached screenshots for you to look over.
- For safety, I did a BIS backup before restoring this BIS at 8.58 PM. (restored BIS backup which I took this morning at 9.28 am before rollover one)