Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Preparing Project For FIN 5.0

Prior to migrating, we want to prepare the project and make sure we're ready to start the migration process as smoothly as possible. There are several things to go through and complete below.

1) Syncing Point and History Time Zones (WIP - waiting for Minh to complete a func for me on this)

First, the user will have to upload the trio file called finHisTzSync. After downloading the file, the user will then go to Legacy Folio and select Import to upload the trio file.

The finHisTzSync trio file contains the following:

  • func/job - findBadTzs - this will check (probably not include. might just have them sync his no matter what)
  • func - finRewriteHisTzSync
  • func - finRewriteHisTzSyncJob
  • job - rewrite his by tz (this appears once the finRewriteHisTzSync func has been executed)

Once uploaded, the user must confirm that the site timezones are set correctly. The finRewriteHisTzSync func will then sync all the points and histories with the correct time zones in case there are any mismatches.

2) Removing Orphan Records

Then the user needs to run the Remove Orphan Records tool to make sure there are no orphan records floating around in the database.

3) Removing Duplicate Extensions

The user will want to remove any duplicate extensions if they exist. Do this only when you can restart the FIN Stack service after executing the below.

  1. Go to legacy folio and query for "ext"
  2. Then you can sort by 'ext' column to see if there are any duplicates
  3. If there are duplicates, select one of each and delete them (only do this if you can restart service after in the next step 4)
  4. Then you need to empty the trash and restart service. Look at the next step on Emptying Trash.

4) Emptying Trash

The user will have to clear the trash. They will go to Trash tab in Legacy Folio or HTML version and select Empty Trash. Another way is to run "folioEmptyTrash()" in folio and that should also clear it.

5) Compact and Backup

Fourth, while still in Legacy Folio, the user will also need to compact the database and create a new backup snapshot. Toggle to Snapshots tab in Legacy Folio and select to Compact. Once compacting database is done, create a new snapshot and download it somewhere on the server outside of FIN Stack directory.

6) Quick Run Through

Fifth, is a quick run through to make sure everything looks good. Look at a few history trends, graphics, programs, etc to make sure all looks good.

7) Custom Pods

Last thing is if there are any custom pod(s) being utilized in the project? It can be something custom we made as part of a contract deal or any that your development team might have done. If any are being used, they need to be updated to be compatible in FIN 5.0. It's best to have this done before migrating if its really important to have. It won't break the build, it just won't be visible to use in FIN 5.0 nor migrated over if not updated.


Once the user has done the above, they are ready for the Migration Process.

  • No labels