Applies To Product(s): OpenPlant PID Version(s): 08.11.10.xxx (SS5) | 08.11.11.xxx (SS6) Environment: Windows 7/8.1/10 (64 Bit) Area: Customization Subarea: Original Author: Harpreet Singh, Bentley Product Advantage Group Background Generally, properties are cascaded from Source to Target class using relationship expression but user was expecting this to work in reverse manner i.e. from target to source. User modifies the size of pipe run and expect this to cascade back to pipeline automatically so that tag and annotation are updated. This article will explain how can we cascade size property from pipe run to pipeline. Steps to Accomplish Open class editor and load OpenPlant schema from \\Workspace\OPPID\Schemas folder. Supplement it with OpenPlant_Supplemental_Tagging schema. Go to PIPING_NETWORK_SYSTEM class and add new property SIZE. Go to NAME property and update the EC Expression as well as Parser expression. Now load OpenPlant_PID schema and supplement it with OpenPlant_PID_Supplemental_Imperial schema. Go to PIPING_NETWORK_SYSTEM class and switch to properties tab. Select SIZE property and click Override button. Add new custom attribute 'Calculated ECProperty Specification' on this property. Add below EC Expression in the EC Expression field. this.GetRelatedInstance("PIPELINE_HAS_SEGMENT:0:PIPING_NETWORK_SEGMENT").SIZE Add Category custom attribute and add values as shown in the picture. Save the changes in schema and verify the result. Change the Size of pipe run to 150mm. You will see not only the annotation but tag and SIZE property is updated as well on PIPELINE. NOTE: Above procedure will ONLY update the tag of pipeline if SIZE is part of the tag format. It will not update the DESIGN_SIZE of pipeline. Comments or Corrections? Bentley's Product Advantage Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!
↧