Create Environment Variables for User Folder and Defaults Folder

You can create AVEVA_DESIGN_USER and AVEVA_DESIGN_DFLTS Windows user environment variables to modify the location of the user folder and defaults folder. For more information, see Setup Environment Variables for AVEVA Unified Engineering.

For all MSIX installations of AVEVA Unified Engineering, a semicolon is automatically added to the end of the AVEVA_DESIGN_USER and AVEVA_DESIGN_DFLTS Windows user environment variables. This is to ensure there is no dependency for shortpaths on the machine. This can lead to issues in addins and other folder locations, which can be resolved.

C#/C++

In C# the following example is used to get folder paths, as this has not been checked for semicolon delimiters, a new folder is created.

Environment.GetEnvironmentVariable

Environment.ExpandEnvironmentVariables

AVEVA recommends to use the PDMSApplication interface in the Aveva.Core namespace. This expands and normalises paths from environment variables, including splitting semicolon delimiters and removing them as required.

Alternatively, you can check for semicolons and trim them if present.

For example, you could use the following syntax:

PdmsApplication.GetPdmsFilePaths("AVEVA_DESIGN_USER")

PML

Environment variables are frequently used in PML. Use !!evarsplit to parse out delimiters.

For example,you could use the following syntax to get the folder or path:

!folders = !!evarSplit('AVEVA_DESIGN_USER')

!file = !folders[1]

Batch files and other scripts

Folder paths can be set using environment variables as a base, for this the following environment variables have been created for MSIX only:

• AVEVA_DESIGN_USER_NOSC

• AVEVA_DESIGN_DFLTS_NOSC

You can set these environment variables against batch files, or other languages, if they are being used.