...

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 two important functions below that update the ids and filters on certain records.

• 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)