| Table of Contents |
|---|
...
Below is how to migrate a project using the FIN Migrate tool. If you have a FIN 4.5 project backup, but don't have FIN Stack 4.5 installed, look at step 2 below on how to migrate that without the FIN 4.5 service. It is recommended to do the O - Manual Migration over this tool as it is a lot quicker and provides logging information like errors and other useful information.
| Warning | ||
|---|---|---|
| ||
Before migrating, the user should be prepared to let their customers know a few issues they may encounter after migration and how to resolve them if they do come across them. Those issues involve browser cache, bookmarks, and/or FIN desktop shortcut. If they don't come across them, it is still recommended to clear browser cache. Browser Cache To resolve the browser cache, they would have to follow the below steps to clear browser cache:
Bookmark and FIN desktop shortcut To resolve this, they can follow this doc on how to Launch Specific Project. |
1) FIN Stack 5.0 Installed
First, the user will have to have FIN Stack 5.0 installed on the machine. Look at Windows Installation (FIN 5.0) for how to install FIN 5.0.
...
| Info | ||
|---|---|---|
| ||
| If the user doesn't have FIN 4.5 installed, they can still migrate a backup project. The user will want to unzip the project if its zipped. Also know where its located on the machine. We recommend having it on the desktop for quick find but not necessary. Make sure its the project itself with its contents, not the project inside another folder with same name. Sometimes that happens when unzipping. Then continue the rest of the steps. |
3) Navigate to bin folder in FIN Stack 5.0
Next, the user will need to navigate the 'bin' folder inside the FIN Stack 5.0 directory. It should look something like below but with your version.
...
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.comyour 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 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()
8) Program Status
Once the FIN service is running, open the project and go to Folio app. The user now needs to remove the "programStatus" tag from the program records. To do this, go to Folio app and run the below query.
- Example run this query: readAll(program).toRecList.map(r => r.diff({-programStatus})).commit
- If you get an error with previous query, run this one: readAll(program).toRecList.map(r => r.diff({-programStatus}, {transient})).commit
9) Users App Access
The users "Application Access" will need to be updated if there were restrictions to certain apps for certain users. The superuser would go to the Users and edit the users who need restrictions to certain apps and update the "Application Access" property. If they didn't have restrictions to any app, then they are fine.
10) Actions
If the user has modified their actions due to them being unique Niagara Network actions and used this doc Haystack Niagara Network Actions, then they need to update them. The change is a simple text of ".parseRef" appended after haystackWrite. You can use the Action Category Permission tool to mass update them.
11) Email SMTP Settings
The user will need to re-enter the email SMTP settings if they had that enabled for use in FIN 4.5. In the Home page after logging in to FIN 5, go to the Settings tab on the top. Then enter the email SMTP settings in the top section of that page.
12) Bacnet Connector Tag
If the user has Bacnet connectors and they have the "bacnetForcePolling" marker tag on them, then they would want to remove that tag from the connectors as its no longer supported in FIN 5. It was replaced with "bacnetDisableCov" marker tag and that goes on a tuning policy that is applied to the Bacnet connectors. If you don't have the bacnetForcePolling tag applied to the Bacnet connectors, you can skip this step.
- Go to DB Builder and select the Tuning Policies tree
- 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)
- Then click on the 'i' icon next to it on the left side under the Essentials column
- Add the "bacnetDisableCov" marker tag and save it
- Then disable the Bacnet Connectors
- After disabling, re-enable a handful of Bacnet connectors at a time
Thats it, the project(s) should be good to go.