Announcements

Announcement: We’re aware of an issue affecting starting a new topic from category pages and creating new blog posts. New topics can still be started directly from the relevant board. Learn more here.

OPC - Referencing Connected P&ID properties in Active P&ID OPC

OPC - Referencing Connected P&ID properties in Active P&ID OPC

andy.cornelius
Explorer Explorer
730 Views
1 Reply
Message 1 of 2

OPC - Referencing Connected P&ID properties in Active P&ID OPC

andy.cornelius
Explorer
Explorer

Within OPCs, I am wondering if there is a way to display connected drawing data other than the "DWG Number" property--via #(=Drawing.General.PnID)--on the Active P&ID OPC once it's been connected to another drawing OPC.

 

Specifically, the client uses a DWG prefix "XX-" that varies so we do no include this in the "DWG Number" property, primarily so that the drawings show up in numbered order in the Project Manager. As a result, when we use the standard reference to connected "DWG Number" (stated above) the drawing number on the OPC lacks the required prefix from the connected drawing (see Model Space OPC Snip.jpg). We can't put this prefix in as static text in the OPC because it varies drawing to drawing.

 

I have tried a couple of things with no luck:

 

  1. Within the existing OPC block attribute that contains the "#(=Drawing.General.PnID)", I preceded this text with "#(=Drawing.Title Block.Prefix)-". This was rejected due to a syntax error--specifically, the space between Title and Block, which is interesting because that is how it was autogenerated using the tag generator interface (except for the "=").
  2. I created a separate block attribute and entered "#(=Drawing.Title Block.Prefix)-". This was also rejected due to a syntax error.
0 Likes
731 Views
1 Reply
  • OPC
Reply (1)
Message 2 of 2

Michiel.Valcke
Advisor
Advisor

Have you tried removing the space from the property category? There are other places as well where Plant 3D seems to be able to function when referring a property with a space or special character in the name (or in this case the category) but then doesn't. the solution is always to remove the space/ special character. 

I tried it with a custom category with no spaces #(=drawing.test.test1) and it works fine.

MichielValcke_0-1717944961494.pngMichielValcke_0-1717944961494.png

 

0 Likes