‘Master_GDL’ and Attribute Infection

[RileyDA]

Hello-

We are experiencing a persistent ‘Master_GDL’ pollution problem in an embedded library on 2 Teamwork projects.

1. Somehow, a bunch of unwanted master_GDL objects appear in our embedded library.
2. These master_GDL object create a ton of unwanted attributes (they are all italicized in the Attribute Manager).
3. We delete all the unwanted attributes via the attribute manager and we delete all the master_GDL objects in the library manager
4. We make sure to not copy and paste anything from other projects after we delete all the attribute/master_GDL pollution.
5. Then after a few days or so, they randomly all reappear

How can we find the source of this pollution and stop it for good?

Thank you in advance!

[DGSketcher]

I would be looking at imported libraries or objects not supplied with AC. I do know from past experience that some bimobject.com parts were very good at creating unwanted attributes, but the objects could come from anywhere. Strip down your library to match a fresh installed AC and add back bit by bit until you identify the source.

If you are adding parts from older files or hotlinks, that may also bring in the attribute pollution.

Ring fence your model and nothing from outside gets added without prior testing or checking the source. 

[Aaron Bourgoin]

some of these unwanted attribute creator macros can arrive in your embedded library via copy/paste operations. The worst one we have is from a loading dock leveler made by a company called Kling. It automatically creates 192 RAL colour Surfaces. We've been trying to kill it dead for 5 years and it persists despite our attempts at hygiene.

[Barry Kelly]

It doesn't have to be a MASTER_GDL script that creates attributes.

I found an object the other day that DEFINEed its own 'Empty' fill.

This was showing up in the attributes as well if I placed that object on plan - but only when the object is placed, unlike the MASTER_GDL that just have to be in a loaded library.

I have no idea how to track down these objects, I just found it by accident as I needed to amend it.

Barry.

[Laszlo Nagy]

---

@Barry Kelly wrote:

I have no idea how to track down these objects, I just found it by accident as I needed to amend it.

Barry.

---

If I had to track these down, I would probably use the LP_XMLConverter to convert all loaded libraries and library parts into XML, then I would search through all those XML files for "DEFINE" commands to find which Library Parts define attributes. That way I believe it would be possible to root out all those offending Library Parts.

[Barry Kelly]

I never have gotten into that LP_XML_Converter.

I probably should look into it one day.

I have all of my library objects placed in a single file.

What I have done to discover what causes the extra attributes, is to copy and paste them in groups from that file into a file I know has 'clean' attributes (i.e. my template).

I can then see what creates the unwanted attributes and can edit them so they don't.

It is pretty tedious, but it works.

Fortunately I can concentrate on the 3rd party and Graphisoft object in my custom library, as all of my objects I am familiar with as I have scripted or amended them.

But even then, there was a few of my own objects that 'defined' attributes, that I didn't remember that I had done.

Barry.