Applies To | |
Product(s): | OpenPlant PID CONNECT Edition |
Version(s): | 10.xx.xx.xxx |
Environment: | Windows 10/11 (64 bit) |
Area: | Properties |
Subarea: | Customizations |
Original Author: | Álvaro Melgarejo, Bentley Global Technical Support |
Overview
Working with OpenPlant PID, the user might have a design where an Instrument Loop is connected to a Pipe Run, and the requirement that one of the Instrument Loop's properties fetches and displays the value of one of the Pipe Run's properties.
In this specific example, a property named Related Pipe Run will be added to the Loop class, it will be inherited by the Instrument Loop class, and the value of that property will be the same as the value of the Name property of the Pipe Run to which the Instrument Loop is connected.
Problem Description
When a Pipe Run and an Instrument Loop are placed on the DGN and connected on some point, there is not an automatic connection established between the two entities. Please notice that there is a connection established between the Pipe Run and the Instruments that are in the Instrument Loop, but not between the Pipe Run and the Instrument Loop itself.
The usual workflow -adding a Calculated ECExpression custom attribute to the property required to fetch the value from the Pipe Run using Class Editor- is not enough, and will always yield the failure value. In order to be successful, an extra step needs to be taken from within OPPID.
This wiki shows the process that needs to be followed in order to achieve the result described above.
Steps To Resolve
Please note that if several relationships are established between the same loop and different pipe runs, the value fetched will be that of the pipe run used for the last relationship.