AutoCAD P&ID

[#1]

Is it possible to define tag format with unique number depend on all of the tag format property?
For example: tag format for line [Diameter – Spec – Flow material – NNN]
The number NNN must be unique for same Diameter & Spec .
Flow material is not part of this setting so 1"-c1-water-001 & 1"-c3-water-001 can be legitimate.

[#2]

I assume you are using P&ID 2008, if you are, the short answer is, no, as we had the same problem, this is also known to Autodesk. It is supposedly fixed in 2009, but our IT department have still to install 2009 for us so I can't confirm or deny as yet.

[#3]

I am using P&ID 2009 , so I assumed that this issue has not been fixed yet

[#4]

I forwarded your questions to Lynn, a member of the team very familiar with
the implementation details and below is her response:

I’m not quite understanding the question.

ALL tags, with the exception of Pipe Segment tags, are already unique based
upon *all* the subparts.

So, his example is already legitimate. 1"-c1-water-001 & 1"-c3-water-001
are different (unique) values, so both of these tag values can be assigned.

Is he asking to have a sub part NOT contribute to the uniqueness? In other
words, if he is asking for FlowMaterial to be ignored, then the two examples
above would be thrown out as duplicates. If so, no, we don’t support that.

The idea of the tag feature, as implemented in P&ID, is to provide a
mechanism for creating a unique identifier. Having some parts of that
identifier not be part of the uniqueness would be confusing.

If the issue is that he would like to see all four values, but only base
uniqueness on 3 values, then he should create a Tag format of
[Diameter-Spec-NNN] and an ANNOTATION format of
[Diameter-Spec-FlowMaterial-NNN]. In this way he can create unique tags but
still show the non-contributing values in his drawing.

Pipe Segment “Tags” are a horrible exception and aren’t really tags, as
there is no uniqueness checking at all.

Ooooohhh… wait, his example below probably *is* a Pipe Line Segment “tag”,
and that’s causing the confusion.

PipeLineGroup tags are real tags (unique). By default, the PipeLineGroup
tag that we ship is only the $(PipeLineGroup.LineNumber), so yeah, that
would be thrown out as a duplicate.

****
What he’ll probably want to do is make Flow Material a property of the
PipeLineGroup, rather than of the PipeLineSegment, and make the
PipeLineGroup tag format be [PipeLineGroup.FlowMaterial-NNN].

Then, he probably will want to make the PipeLineSegment’s FlowMaterial
property be an acquisition property (a Cork feature) that usually gets its
value from the PipeLineGroup.
****

That should provide what I think he wants.

The confusion is that the Pipe Line Segment “tag” (which is not really a
tag) sets the line number property in the Pipe Line Group tag (which *is*
really a tag), given the out-of-the-box tag format.

So, based on a lot of guesses about what the problem may actually be,
hopefully one of these responses will help. The portion in bold is probably
the real issue.

Best,
Lynn



"meir_w" wrote in message news:5947347@discussion.autodesk.com...
Is it possible to define tag format with unique number depend on all of the
tag format property?
For example: tag format for line [Diameter – Spec – Flow material – NNN]
The number NNN must be unique for same Diameter & Spec .
Flow material is not part of this setting so 1"-c1-water-001 &
1"-c3-water-001 can be legitimate.

[#5]

To make short and simple, the line number store in Pipe line group setting.
Therefore to define uniqueness line number by other pipe line group property, do as follow:
Under pipe edit Tag Format :Line Number. Add required property from Pipe line group.
For example "NominalSpec" .
Under Pipe line segment create/add new Tag format.
For example : PipeLineGroup.NominalSize , PipeLineGroup.NominalSpec , PipeLineGroup.Service, PipeLineGroup.LineNumber[NNN]
The line number will be generate by the setting of Tag Format: Line Number from pipe line group
See attached picture.