User wants to extend the Tag Number property uniqueness check so that the component tagging will have the Number property as part of the Service and Type. This article will help the user in customizing the component tag and show how the schema can be modified to achieve this requirement for different classes.
In the OpenPlant_PID_Supplemental schema a STRING_LIST custom attribute needs to be added to the property that has the ExtendType custom attribute GetNextValue. In most cases this is the NUMBER property. In the STRING_LIST custom attribute add the properties that will be used to check for uniqueness.
1. In Class Editor load the current OpenPlant_PID schema. Supplement this schema with the OpenPlant_PID_Supplemental_Imperial schema. 2. Locate the required class and then the NUMBER property. 3. Override the property if not already overridden. 4. On the NUMBER property add a String List custom attribute and fill it in as shown below – for example we have added SERVICE as a new item.
5. Open OpenPlant_Supplemental_Tagging, locate required class and then the NAME property 6. Override the property if not already overridden and edit Calculated ECPropertySpecification custom attribute as shown below8. Create two Associated Item values for Service (S1 and S2.)9. Place few pipelines with default SERVICE S1 and you will see, that number is suggested correctly10. Change the default SERVICE to S2 in P&ID Document dialog11. Place few pipelines with default SERVICE S2 and you will see, that number is suggested correctly Now you can change SERVICE's, place pipelines and always have correctly suggested number.
If you need to use same tagging method in different models, then for each new drawing use different AREA and using same workaround add PLANT_AREA in String List custom attribute.
If PLANT_AREA is not needed in TAG, leave ECExpression in OpenPlant_Suplemental_Tagging schema as it was, but then you will have to select the drop-down on the number property and pick on the Maximum button EVERY time you change the SERVICE.
Same workaround can be used for other classes.Add DEVICE_TYPE_CODE in String List custom attribute to extend the Tag Number property uniqueness check with component Type and test
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!