Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

The VisionSetting table contains the following columns:

ColumnDescriptionSample
VisionSettingIDUnique Identifier for the VisionSetting table. There should only ever be one record in this table.1
VisionRepositoryURLHTTP Reference to where the Vision Repository is located. This is not currently implemented.http://www.getaeros.com/vision/repository/
DBVersionThe version of the Vision database. When Vision loads, it will check this value to see if the database has been upgraded.6
FinancialsERPDatabaseThe name of the Aeros ERP Database that Vision Financials uses to extract G/L data.ERP
IsUserERPForEmailIf set to True, then when emailing Reports from Vision, the system will use the standard ERP EmailQueue tables. If set to False, the system will use the users built in E-Mail client (such as Outlook)True
UserListSourceIDConnects to the UserListSource table and must be a matching record.
1 = Aeros ERP, 2 = Aeros LIVE, 3 = Aeros Vision
When set to 1 or 2, the system will validate that the user upon login exists within Aeros ERP or LIVE before being granted access.
When set to 3, the system will require that the user exists within the Vision User configuration before being granted access. 
1
UserListSourceConnectionStringUsed only when UserListSourceID = 1 or 2.
If 1, then provide the connection string to the ERP database. If 2, provide the connection string to the LIVE database. If 3, this can be left blank. 
SERVER=SQLServer;UID=ERP_AppUser;PWD=WhateverPassword;DATABASE=ERP;
AerosERPConnectionStringProvide a connection string to the ERP database if used. This will allow the E-Mailing functions to pull out Address Book data when emailing reports.SERVER=SQLServer;UID=ERP_AppUser;PWD=WhateverPassword;DATABASE=ERP;
  • No labels