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 13 Next »

Migrating To FIN 5.0

Below we'll be covering the migrating process from FIN 4.5 to FIN 5.0. A FIN 4.5 project cannot just be loaded to FIN 5.0 and vice versa. Once migrated to FIN 5.0, a project can no longer be reverted back to FIN 4.5. The only way to have a project running back in FIN 4.5 is the backup made prior to migrating, which if the user does do this will lose any historical data and other stuff from the time it was down and using the FIN 5.0 project version. (WIP - FIN 4.5 graphics, programs, schedules etc saved on a server can be uploaded to FIN 5.0, but not the other way around. Made an issue in Jira for Minh to see if he can modify backup and restore funcs to make them work. Will need to update ids if Minh can't do it.)

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. The user will first want to go through the Prepping Project for FIN 5.0 documentation.

Migrating Project To FIN 5.0

Once the user has prepped the project and ready to migrate to FIN 5.0, they can begin the Migration Process.

Manual Migration

If the user wants to manually migrate the project, they can do so following our Manual Migration steps.

After Migration

After the migration of a project using the finmigrate tool, the user can check the project out in the browser after logging in. The migration should have ran three important functions below that update the ids and filters on certain records and some bacnet stuff.

  • finMigrateFilterIds() - this would update the id's on certain filters such as graphicOn, programOn etc because the id format in FIN 5.0 has changed. If not updated, those records wouldn't appear or function without proper id format. For example a floor graphic usually only runs on a single floor so its graphicOn would be an id of a floor. The id would look something like "id==@1eeaf23d-b2ddf0f3" instead of something like "id==@p:demo:r:1eeaf23d-b2ddf0f3". They would have to be updated manually or using the function. If the user notices that the id's weren't updated, then can run the function in folio to update them. Then check to see if it worked. If not, contact us at support@j2inn.com.
  • finMigrateFinFile() - this would update the id's on virtualPoints, bindings, query tags inside graphics, programs etc because of the id format mentioned above. This however may not update id's in a program/event inside a graphic. Those would have to be updated manually if there are any hardcoded in there. This can also be ran in folio if they weren't updated.
  • bacnetServerMigrate() - this would update the bacnet funcs. (WIP - update later)
  • No labels