| Table of Contents |
|---|
...
First, the user will have to have FIN Stack 5.0 installed on the machine. Look at Windows Installation (FIN Stack 5.0 Windows Installation) for how to install FIN 5.0.
...
Thats it, the whole migration process has been completed and can check out the project(s).
The funcs that were executed while migrating were below. If for some reason, things look off, they can be executed manually in folio with bacnetServerMigrate being optional if being used in 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 us at support@j2inn.com.
- 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 or program).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()
Thats it, the project(s) should be good to go.