Migrating from Vision v2.16.6.0 to v2.16.7.0+

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.

In 2.16.6.0 and older, the AerosVisionConnections.XML file has to point to the ERP database. Then, within the ImportExportConnections table, there was a record (Type=5) that provided the connection string to the Vision database.

For 2.16.7.0+, this is no longer required.

Upgrade Step 1 - Database

1. Run the scripts to upgrade the Vision database.
   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 - Create First Admin User

The VisionUser table will have no records in it. This means that when a user logs in, even if they authenticate against ERP, they will have no permissions to any options. In this step, you need to create the first user within Aeros Vision.

1. Determine what user you want to create first.
   This may be the Agrisoft account, or the Admin user, or the Customer's primary username.
   
   
   

2. Determine the UserProfileID from the ERP database:
   SELECT UserProfileID, userid From ERP.dbo.UserProfile where userid like '%admin%' or userid like '%agrisoft%' 
   
   
   

3. Insert a new record into the Vision database.
   INSERT INTO dbo.VisionUser (IsActive, IsAdmin, CanEditSecurity, ExternalUserKeyID, UserName) VALUES (1, 1, 1, XXXX, 'admin') 
   Replace the blue/green values with the actual values from the ERP query. 
   
   
   

4. Now, when accessing Vision, you should be able to see all existing Queries/Reports/Dashboards/Financials and then use the Manage Security options to setup other users. 
   
   
   

5.  Another option is to give ALL users access into Vision... this will be the LEAST restrictive, but is the same way it was before Vision Security was enabled.

   This command will get all users in ERP and create records in the VisionUser table that gives them access to Create Reports/Queries/Dashboards/Financials by default.

   INSERT INTO VisionUser (IsActive, UserName, ExternalUserKeyID, CanCreateQuery, CanCreateReport, CanCreateDashboard, CanCreateFinancialsLineGroup, CanCreateFinancialsColumnGroup, CanCreateFinancialsReportGroup, CanEditDataModels, CanEditConnections, CanEditCategories, CanMigrateFromReporter, CanAccessRepository, CanPublishToAerosERP, CanEditSecurity, IsAdmin, IsForceResetPassword)
   SELECT 1, UserId, UserProfileID, 1, 1, 1, 1, 1, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0 FROM ERP_3_5_Dev.dbo.UserProfile WHERE UserId NOT IN (SELECT UserName FROM VisionUser) AND status = 'A'

    

Upgrade Step 3 - 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) 
   
   
   

   Open

   

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