3 of 3 people found this helpful
If you are referring to migrating these displays to PI Vision, then it's not possible to migrate these. The actual standard display elements (trends and other built-in visual symbols) are fine, but there is no support for VBA functionality in PI Vision.
Depends what you mean by migration, if under migration you only mean changing links to another location then existing VBA code in PDI will work (this refers to Sharepoint).
If convert graphics from PDI to SVG, VBA in SVG is not supported.
John's correct in that the standard elements will migrate without a problem, but VBA, as well as ActiveX OLE objects and a few other symbol types will not migrate. VBA and ActiveX are no longer supported by Microsoft (ActiveX support ended with IE, for example, and is not supported in Edge) and they will not be incorporated into Vision.
ProcessBook displays that contain these will be stripped of them when migrated, so the remainder of the display will be functional in Vision.
I would recommend going through the PI Vision uservoice page and adding, upvoting, or commenting on enhancement requests pertaining to the individual functionality that your VBA was delivering so that we can try to support it natively in Vision. For other custom functionality, Vision allows for the building of custom symbols, although this is using Angular and the PI Web API.
As mentioned in the above thread, you cannot able to migrate the Processbook with VBA code to PI Vision. This is application limitation, already many raised this concern in PI Vision uservoice page
But I would recommend you an another option, if your display count is very less means, whatever logic you used in VBA code you can create in PI Analyses calculations and remap your display with PI AF attributes and then migrate your displays to PI Vision.