Labels with Properties become unavailable when relinking hotlink in teamwork.

[Rafael Sangareau]

Hi there!

So we've been having this issue often at the office. When we share a file to teamwork and relink the hotlink to the teamwork file (we work in "iceberg") some of the labels we have placed get messed up. We used to have the "Text/Auto Text" label (the first time this happened a colleague spent half a day's work retyping the auto text in every label! I thought it was crazy and thought to change it) now I changed to the "Classifications and Properties" label, I thought that would fix it since it's a label for properties but the problem persists, although now fixing it is as easy as reselecting the correct property from the drop down menu and it only takes a few seconds.

Any clues? Cheers!

[Xandros]

Hi @Rafael Sangareau 

properties do have a (hidden) ID. If they dont sync you might be getting this problem.

there are 2 approaches that I'd try in this context:

1. since your property is an expression, it should be no problem to delete the property in your hotlinked module. then go to your main file and export your property from there and import the freshly exported *.xml-file in your hotlink.

2. you could do a detour to ifc-mapping. in both your files. add this property to a ifcWall in a property-set of your choice. when this is set up the labels should be relinked to display this ifc property instead. advantage here, that your ifc property is ignoring the internal ID in a way and the label is looking in both files for the path instead (for example: ifcWall > PSet_WallCommon > Automatic_Composition)

[Rafael Sangareau]

Thank you very much for your help @Xandros . I'll try the second option since we work in "iceberg", meaning the main file is also the hotlink file so changing anything in one "file" changes "both" of them.

[Jonah Tan]

@Rafael Sangareau Did this work for you? 

I've having the exact same issue on my end, but when exploding the hotlink to edit for a specific job. 

I've got a combination of property labels and autotext labels that both link to properties in our mod file. When I've placed it in my job file (teamwork) and explode it, the autotext labels change from "undefined" to "#" and the property labels say that the properties can't be found. 

I thought it was a property issue too so I reexported the properties from the mod file and then I imported them into the job file and it still didn't work. 

You figure anything out?

[Rafael Sangareau]

Hello there! It’s our policy not to explode things as it tends to break all kinds of links, we usually duplicate the .mod, apply the changes and reinsert, if we are just using the .mod for parts then we know we’ll have to sift thru all the elements for those cut links. As for the auto text problem, I have not found any solution, once it’s broken the only way to get it back is by retyping the auto text. As for the labels of the classification and properties type, I have tested the ifc approach a couple of times and have not encountered this problem anymore, but mind you I haven’t deployed it to the office standards as it “changes internal practices” so I don’t know how it performs in normal office operations, it’s quite interesting to watch something break because someone else used it in a different way from what you designed it. Best wishes.