Currently any user in the PI Vision Utility Users group running the PI ProcessBook to PI Vision migration utility can select any folder as the destination folder, regardless of whether they are allowed to write to the folder in PI Vision (i.e. their AF Identity has write permissions on the PI Vision folder).

Additionally, only certain users (e.g. PI Vision admins or specific identities) should be able to specify a user other than themselves as the owner of a display.

The ProcessBook to Vision migration utility should observe PI Vision folder security.

On an architecture with Utility on a computer located on a different domain of the PI Vision server, the authentication fail.

Could it be possible to prompt a login window (as for AF)

Support Custom axis settings. to avoid this current issue

"Unsupported legend option;Custom axis settings are not supported;Scales with different max and min types are not supported.;Trends with different trace scale ranges are not supported under trend options in PI Vision"

The color of some symbol library symbols is different in PI ProcessBook and PI Vision after migrating PI ProcessBook displays to PI Vision. It would be nice if the color did not change, or if the Migration Utility allowed users to choose the destination color if the same color is not supported in PI Vision.

There are graphics in the ProcessBook graphic library that do not exist in the PI Vision graphic library. Would like for the PI ProcessBook to PI Vision Migration Utility to support the migration of displays that contain these graphics that are not part of the PI Vision graphic library.

Currently if a .PDI file contains an OLE object, which could be something as simple as an image embedded in the file using Insert > Object in ProcessBook, the OLE object can't be migrated. The Analysis Results return a warning that the "File contains OLE object" but nothing more. It would be useful if more details could be generated about the OLE object, such as whether it's embedded, how many OLE objects there are (if more than 1), and/or the object type.

In Processbook, when we draw a trend with multiple digital tag, we can set multiple scale with the number of the state. This permit to see multiple tag with the same scale on different place in the trend. When we define the trend we see only the digital state, we do not have the choice for entering a number

Currently display links are only preserved when linked PI ProcessBook displays are migrated together. Navigation links should be preserved across different batches of displays that are migrated.

Currently, when migrating PI Processbook symbols, if there are Connector symbols in display they are not moved to the back causing issues with overlapping objects in PI Vision after the migration.
A current workaround is to "Arrange > Send to Back" function on these line symbols either in PI ProcessBook or PI Vision. It would make migration easier for these connector symbols to be automatically be sent to the back.

As a PI System admin, it would be helpful if I could migrate my ProcessBook displays of SVG type to PI Vision displays. The utility currently does not accept SVG type input.

The reason I cannot just open the SVG in ProcessBook and save as a PDI is that this conversion process distorts some of my curved parts of my graphics on some of the displays.

Customer has an old PI system without an AF structure. After the migration from PI ProcessBook display (data mapped to PI Point) to PI Vision display (data mapped to PI Point), he needs a tool that can automatically replace the data (data mapped to PI Point) in PI Vision display with AF attribute data, rather than having to change the data type one by one in PI Vision display after the migration.

As an Admin looking at the Excel Migration report, I would like to see a column with the tabnames in Processbook and the items listed tabwise as it is in the online analysis report as it is difficult for large PIWs to identify which tab the display is in to fix it before trying to analyze again.

In PI Process Book it is possible to create Gantt Charts, and corresponding tag trend overlays from PI Batch data. There is no need to create event frames in PI AF to use this feature. This was my most used feature in PI Process Book, and the lack of this feature has prevented me from fully migrating all of my PI process books into PI vision.

VBA coding or some form of coding should be supported in PI Vision. One use of VBA coding was necessary in PI ProcessBook because multiple PI AF contexts are not able to be selected for similar groupings of symbols on the same display. An example is a table where each row has a pull-down menu to set each column of the row to the proper PI tags.