...

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. We recommend to migrate the project(s) manually as it is a lot quicker and provides logging information like errors and other useful information that occurred during migration.

Manual Migration

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

...

After the migration of a project, the user can check the project out in the browser after logging in. Then follow and do the below steps to complete the migration process. 

1) Funcs to execute

Funcs to execute in folio with bacnetServerMigrate being optional if being used in the project:

• finMigrateFilterIds() - this would update the id's on certain filters such as graphicOn, programOn etc. 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. 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 your distributor.
  • Example use: finMigrateFilterIds()
• finMigrateFinFile() - this would update the id's on virtualPoints, bindings, query tags inside graphics, programs etc. 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.
  • Example use: readAll(fin5).each x => x.finMigrateFinFile() OR finMigrateFinFile(@record_Id)
• bacnetServerMigrate() - this would update the below bacnet tag names to the new tag names in FIN 5.0. This would be for projects using bacnetServer in FIN 4.5. The ext needs to be enabled.
  • bacnetNetwork → bacnetServerNetwork
  • bacnetLocalAddress → bacnetServerLocalAddress
  • bacnetMacAddress → bacnetServerMacAddress
  • bacnetDevice → bacnetServerDevice
  • bacnetInstance → bacnetServerInstance
  • bacnetCovIncrement → bacnetServerCovIncrement
    • Example use: bacnetServerMigrate()

...

1. Go to DB Builder and select the Tuning Policies tree
2. Select the tuning policy that is applied to the Bacnet connectors (this is assuming the Bacnet connector(s) already have one. If not, create one and apply it to them)
3. Then click on the 'i' icon next to it on the left side under the Essentials column
4. Add the "bacnetDisableCov" marker tag and save it
5. Then disable the Bacnet Connectors
6. After disabling, re-enable a handful of Bacnet connectors at a time

Thats it, the project(s) should be good to go.