Migration limitations
- Last UpdatedNov 14, 2022
- 7 minute read
When migrating from PI ProcessBook to AVEVA PI Vision 2020, some functionality and some symbols may appear differently or may not appear in the display, altogether.
Functional limitations
The following table lists general functionality of PI ProcessBook that is not supported or differs in PI Vision:
|
Function |
Migration impact |
Issue Flag |
Migration Limitation Description |
|---|---|---|---|
|
Element relative display (ERD) |
|
|
The migration tool must be able to connect to the AF server. If no connection established, the ERD context may migrate incorrectly. |
|
Font |
|
Migrated PI ProcessBook content uses the standard AVEVA PI Vision font, Arial. |
|
|
Font style |
|
Font style (for example, bold, italic, underline) cannot be configured in AVEVA PI Vision and displays as unformatted Arial font. |
|
|
Layers |
|
AVEVA PI Vision does not use the concept of layers within displays, so layers is not preserved after migration from PI ProcessBook. |
|
|
Multi-State |
|
|
Multi-State limits for PI points and attributes are migrated correctly if there is a connection to the Data Archive or PI AF server. If a connection cannot be established at the time of migration, an attempt to migrate the Multi-State limits is made, but the limit values may migrate incorrectly. Multi-State symbols using PI Calculation data sets always cause a warning regardless of a connection to the Data Archive because the limits must be estimated. |
|
Number formatting |
|
AVEVA PI Vision supports various number formatting options but does not support %, absolute value, and certain custom number formats. In these cases, the number format in AVEVA PI Vision uses the same number of decimal places as those specified in PI ProcessBook. |
|
|
Symbol visibility |
|
AVEVA PI Vision does not support hiding a symbol as part of its configuration. You can hide a symbol as a multi-state behavior. |
|
|
Unit of Measure (UOM) conversion |
|
AVEVA PI Vision does not support converting the UOM for AF attributes. Symbols that are configured for UOM conversion are displayed using the units specified on the AF attribute. |
|
|
VBA |
|
|
VBA code is not supported in AVEVA PI Vision displays. PI ProcessBook displays that contain VBA code are migrated without the VBA code stored in them. |
Symbol limitations
Symbol limitations are listed in the following table:
|
Symbol |
Migration Impact |
Issue Flag |
Migration Limitation Description |
|---|---|---|---|
|
Bar |
|
There are a few bar symbol options in PI ProcessBook that are not supported in AVEVA PI Vision:
|
|
|
BatchView |
|
|
This symbol cannot be migrated because there is no BatchView symbol in AVEVA PI Vision. |
|
Button |
|
Since there is no button symbol in AVEVA PI Vision, buttons are converted to gray rectangles with the button text inside. Additionally, they are configured with a navigation link, as long as the link is not to a third-party application. Displays that contain buttons that link to other displays must be migrated at the same time as the target display(s). |
|
|
|
|
Buttons that link to an application or action not supported in PI Vision will not be migrated with an action. |
|
|
|
Buttons that link to an associated display that cannot be resolved during the migration will not be migrated with an action. Displays that contain buttons that link to other displays must be migrated at the same time as the target display(s). |
||
|
Control |
|
|
Control (ActiveX) is not supported in modern browsers and, therefore, cannot be migrated to AVEVA PI Vision. |
|
OLE Object |
|
|
OLE Objects are not supported in AVEVA PI Vision. |
|
SQC Chart |
|
|
This symbol cannot be migrated because there is no SQC Chart equivalent in AVEVA PI Vision. |
|
Symbol Library |
|
Symbol library symbols are migrated provided the corresponding symbol exists in AVEVA PI Vision. AVEVA PI Vision uses an updated version of the symbol library, which does not contain all of the same symbols that exist in PI ProcessBook. Some of the symbols that do exist in both versions have slightly different appearances and default colors and may display differently in AVEVA PI Vision. |
|
|
Trend |
|
A few options on the trend symbol in PI ProcessBook are not supported in AVEVA PI Vision:
|
|
|
|
|
The following options are not supported in PI Vision and the data is presented differently on the trend after migration:
|
|
|
Value |
|
Value symbols in PI ProcessBook can be configured to have the timestamp and data item name on the left, right, top, or bottom of the data item value. AVEVA PI Vision does not support these options. When migrated to AVEVA PI Vision, value symbols that are configured to show the timestamp or data item name have the timestamp below the value and the data item name above the value. Because of this, the relative location of value symbols may be different in AVEVA PI Vision compared to PI ProcessBook. |
|
|
XYPlot |
|
A few options on the XYPlot symbol in PI ProcessBook are not supported in AVEVA PI Vision:
|