Line ID No Longer Linked To Process Line

[HybridAWD]

I guess I am keeping the P&ID forum going with all of the small little bugs I am coming across in the P&ID's.

So has anyone else come about with this issue? I have been noticing on more and more lines that the Line ID is no longer "attached" to the Process line. Where you should be able to CATT on the line ID, you are not able to do that anymore when they lose their link. Also, I want to mention that if you CATT on the line and change something such as insulation, it may not update afterwards.

I find this to be a huge glitch with something. I can't pin point exactly what is causing it nor can I even suggest something. Has anyone else run across this issue? Is there a quick fix? I will be calling tech support shortly.

[PeterJ]

Line id's loose the link to the line after placing a reduction or spec break. The id is linked to the run and these items insert a new run. The id's can be re-attached to the correct run with the 'reattach object' command.

[HybridAWD]

Line id's loose the link to the line after placing a reduction or spec break. The id is linked to the run and these items insert a new run. The id's can be re-attached to the correct run with the 'reattach object' command.

In that situation they turn red which points out that they have lost their link and need to be reattached. However, in my situation, this doesn't involve spec breaks or reducers. I mean, it could be possible that someone placed a spec break and or reducer on a separate P&ID, but that shouldn't cause a line ID on a separate P&ID to lose it's link, correct?

[dave]

If it was linked it sure would.

I have had trouble with lines and line numbers since I started using the package. I have developed work arounds and quick fixes but thses take extra time. I have found the single greatest source of pain on all of our projects are related somehow to lines.

[PeterJ]

Process lines is indeed the most complex part of the software. I always put a lot of effort in teaching it to new users because you can do so many manipulations on them that ruin the data, while the graphics don't change.
I'll try to assemble some information and additional tools to post on this site, but that might take a while since I'm very busy at the moment.
tools are :
-a special catt command for lines that updates all visible info on the line (including valves) after a change
-a 'change line type' function that runs over multiple drawings
-some reports
- ... (I must search all custoizatios I've ever done ...)

[Data Wrangler]

I would be interested in getting your information, Peter.

To me the piping has alway been the "last frontier" of this program. You can do good work with maintaining instrument lists, keeping track of pieces of equipment, etc. but the piping is fustrating. Actually, right now we don't rely on it for much - the pipers do their line list manually - but we are hoping to change this.

Derek

[HybridAWD]

Between myself and another guy here, we actually do very good work. The problem is we're always having to "clean" up the database. Now I'm not in any way or shape saying Bentley P&ID is a bad program. I actually find it to be a very very good program. It just has it's bugs and glitches, but that is why we're here. To help solve those problems and work through them together. Live, Learn and grow from everything.

I think there is just a learning gap between the developers and the users. I am really surprised Bentley hasn't come out with a really well put together user manual. The training books help, but they leave a lot of open ended topics unanswered.

Peter, whenever you get time, please inform us all. Thanks for all of your input you have been sharing with us, it's nice to know you care about helping us!

[HybridAWD]

One more note about relinking it. If you run the command 'WW', this is what you get:
Command: WW
Select object: ERROR Argument must be ename or keytag..

nil

[PeterJ]

Hybrid,

That would be logic on an item without link
Try the command Q
that should retutn something like
((-1 . <Entity name: 7efaae80>) (0 . "TEXT") (330 . <Entity
name: 7efa7cd0>) (5 . "6C0") (100 . "AcDbEntity") (67 . 0) (410 . "Model") (8 .
"text") (100 . "AcDbText") (10 728.679 196.5 0.0) (40 . 3.0) (1 .
"50-L012-P0S") (50 . 0.0) (41 . 0.75) (51 . 0.0) (7 . "STANDARD") (71 . 0) (72
. 4) (11 741.0 198.0 0.0) (210 0.0 0.0 1.0) (100 . "AcDbText") (73 . 0)

which is the autoCAD entity info
and it would be followed by
(-3
("PE_URL" (1000 . "projid=0034&linktab=PROC_LNK&linkid=0000000073&")) ("AT_"
(1070 . -17000) (1005 . "594") (1070 . -16006) (1000 . "(LINEMARK )"))))
which is the Extended Entity data that we use to store the links between objects and from their linkpoint to the database.
The QQQ command returns the infor from that linkpoite.
The WW shows part of the extended entity info on the linkpoint.
if an object has lost its connection to the linkpoint, it's normal that no info can be retreived from it.