We've been modeling piping components with no issue using the default Named Expressions and Element Templates. These have been setting the level colour symbology based on line size. The level name created has been automatic and matching the line number created in the Pipeline Manager.
"BY_LEVEL_AND_TEMPLATE:" & PIPELINE.SERVICE_NAME & "-" & PIPELINE.NAME & ":OpenPlant\Piping\" &
IIF( OPITEM.IsOfClass( "INSTRUMENT", "OpenPlant_3D" ), "Instrument:",
IIF( OPITEM.IsOfClass( "CONTROL_VALVE", "OpenPlant_3D" ), "Instrument:",
IIF( OPITEM.NOMINAL_DIAMETER <= 4 , "DiameterRange1:",
IIF( OPITEM.NOMINAL_DIAMETER > 4 AND OPITEM.NOMINAL_DIAMETER <= 8, "DiameterRange2:",
IIF( OPITEM.NOMINAL_DIAMETER > 8 AND OPITEM.NOMINAL_DIAMETER <= 12, "DiameterRange3:",
IIF( OPITEM.NOMINAL_DIAMETER > 12 AND OPITEM.NOMINAL_DIAMETER <= 16, "DiameterRange4:",
IIF( OPITEM.NOMINAL_DIAMETER > 16 AND OPITEM.NOMINAL_DIAMETER <= 20, "DiameterRange5:",
IIF( OPITEM.NOMINAL_DIAMETER > 20, "DiameterRange6:", "Default:" ) ) ) ) ) ) ) ) & "Model"
Our client then requested that all piping on the same service be the same colour. The designer proceeded to force the colour changes at the element level. Now all piping is modeled on level Default and the same colour, regardless of service or line number. To be clear we had no idea how this was controlled. Only after exploring the issue did we find out about Named Expressions and Element Templates.
Our company admin team is developing new dgnlibs to adopt symbology based on service (as opposed to line size), however in the meantime we'd like to know how this became "broken" in the first place.
How did this get "broken"? How do we fix it?
Best Regards,
Jason Poulin
