Versions Compared

Key

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

History

Prior to version 2.16.7.0 of Vision, the application required that they are also users of Aeros ERP. With this release, this is no longer a requirement.

...

For 2.16.7.0+, this is no longer required.

 

Upgrade Step 1 - Database

  1. Run the scripts to upgrade the Vision database and infrastructure.
    New tables: VisionUser, VisionPermission, UserListSource 
    Modified tables: VisionSetting 

  2. Ensure that the VisionSetting table column of DBVersion is 6 (or greater if going to an even newer version)
    When Vision opens, it checks to make sure that the DBVersion is at least 6 to ensure that the database has been upgraded.

  3. Ensure that the VisionSetting table column of UserListSourceID = 1
    This sets it to use ERP for authentication.
    At the time of this writing, ALL Aeros Vision users are authenticating against Aeros ERP. This maintains that configuration.

  4. Ensure that the VisionSetting table column of UserListSourceConnectionString = a valid ERP database connection string.
    Example: SERVER=SQLServer;UID=ERP_AppUser;PWD=WhateverPassword;DATABASE=ERP; 

  5. Ensure that the VisionSetting table column of AerosERPConnectionString = a valid ERP database connection string.
    Example: SERVER=SQLServer;UID=ERP_AppUser;PWD=WhateverPassword;DATABASE=ERP;  

Upgrade Step 2 - Application Install

  1. Using the standard installer, install Aeros Vision v2.16.7.0+.

  2. Modify the AerosVisionConnections.xml file to now directly point to the Vision database INSTEAD of the ERP database (as previously configured) 

    Image Modified
  3. You should now be able to launch Vision either directly through Aeros ERP or through the Aeros Vision executable.