Property Tag disconected on re-share

[Matthew Johnson]

An existing BIMcloud basic project when saved as a solo file and re-shared loses the connection to the Properties from Property Labels. The label shows a connection to an "UNAVAILABLE VALUE" GUID and the label representation shows "---".

With hundreds of views and thousands of labels impacted, we cannot go through the file and re-link each one individually.

Anyone else have this issue?

Anyone have a solution to relink the labels?

Operating system used: Windows 11 24H2

 

[Diseno14]

Hi!

You could create a schedule in the project with the correct properties data and their respective elements listed, and an identical schedule in the file with the empty data  properties.

- Export the schedule from the correct file to a spreadsheet.

- Then import the spreadsheet into Archicad with the empty data schedule .

This allows the property to be quickly filled with the desired information.

https://helpcenter.graphisoft.com/user-guide/77258/

[scottjm]

Hey Matthew,

I’ve come across this before, but haven’t had a chance to dig deeper. When I saw it previously I recall it happening to elements that were with coming from hotlinks of an iceberg. 
It seemed that the properties from the hotlinks were creating a new property with a new GUID, hence the label can’t find the original property as the GDL parameter in the label is still looking for the old GUID. Maybe it’s related to the conflicting properties issue/bug. 
Sorry I don’t have a specific solution. 
One for the devs to advise on maybe?

Actually I was thinking about a harebrained possible solution, that would involve modifying the GDL of the parameter label. 
- add some code to store the property name into a parameter of the label. This would need to be run in the original file. 

- then some additional code that if it can’t match the GUID of a property, iterate through every properly and match the name of the property to reapply the new GUID. This would run in the new re-saved file. 
Definitely not a perfect solution, and no idea if it would actually work. You probably need to use migration script to trigger it work automatically on all labels. 

[Matthew Johnson]

Scott,

You might be onto something. The newly reshared teamwork file has around 20 hotlinked modules and while I had updated them from a new location I hadn't re-exported them from the new teamwork file yet so there is a chance the hotlinks are bringing in contaminated GUID from the old teamwork file.

I've been running a few test along that line tonight to re-export and update the hotlinks to see if that gets things back in order. So far no luck.