Mapping values don't always work properly (or I'm missing something)

[etterdtamas]

Hi!

We created our own attribute system (reindexing & modifying existing attributes, creating new ones) in our company template file, which ended in chaos regarding the value mapping of the library parts.

For example for the index for the backgorund fill is 20 and the original index (65) was assigned to the hexagonal fill, which caused that everything that had it's fill set to background before, is new the hex fill.

I was really hopeful when i saw that we can easily remap the default values, and started immediately to do so. For most library parts it works, but there are a few exceptions.

The problem what i'm fighting with is, that if I search for that specific library part (2D Tree Texture Top View and all its other versions) and parameter (FillPattern) in the customized JSON file, it shows me that the value is set to the desired value (20 - Background), but when I import the JSON To AC29 and open that object it still shows as it has the original FillPattern value (65) which is as a result of our new attribute system is linked to hexagonal.

We don't want to change our attribute system, and according to the JSON file there should be no problem with the fills.

Is this a bug? Did I do something wrong or ther's a limitation that I don't know about?

I attached three images, hope you can help me! Thanks

   

 

Operating system used: Windows 25H2

   

[Barry Kelly · Accepted solution]

The parameters of some objects are hidden and can not be altered by the user when placing th object.

I believe if they are hidden in the object script, then the mapping table has no effect.

I have asked Graphisoft on a few occasions to please fix this.

Here is one of them ... https://community.graphisoft.com/t5/Libraries-objects/Library-updates/m-p/662019

Not all of us use the default Graphisoft template attributes.

Seems to me that the promise that the new Global Libraries would be easier to update more often just isn't happening.

Barry.

[etterdtamas]

Thank you for the info @Barry Kelly , it explains a lot!

Also @Magdolna Marosvari Can you please add these fixes to the next library update? It would be a huge help, as it makes these objects unusable for us.

Thanks,

Tamás