Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

Before migrating, the user should be prepared to let their customers know 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:

  1. On the Chrome browser, hit the F12 key on the keyboard (opens up the Developer tools)

    1. If F12 doesn't work, they can go to browser Settings (top right corner)

    2. Select "More tools"

    3. Then select "Developer tools"

  2. Then right-click on the browser refresh icon

  3. Select "Empty Cache and Hard Reload"

  4. Once the page reloads, they can close the Developer tools window

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

...

Here you can find possible folio migration errors we have come across Migration Errors.

7) Migration Complete

Once that is done, the migration is complete and the command prompt should return back to the bin folder. If there are errors, the user can scroll up to see them. Common ones might be weather-related which is ok ignore those. The user can now start the FIN Stack 5.0 service and log in to the project.

...

Here you can find possible DB migration errors we have come across Migration Errors.

8) Important Funcs

Once manual migration is complete, the user will have to run the below funcs per project to help update a lot of filters/tags with the correct id's, as well as update the bacnetServer tags if used. The id format has changed in FIN 5.0 from something like id==@1eeaf23d-b2ddf0f3 to something like id==@p:demo:r:1eeaf23d-b2ddf0f3

...