topic Re: Custom door leafs and handles not populating the list for selection when Migrating to Global Lib in Libraries & objects

Custom door leafs and handles not populating the list for selection when Migrating to Global Libary

Roderick_Anderson — Thu, 02 Jan 2025 14:30:11 GMT

I have discovered a potentially serious problem with the handling of the Door Objects (maybe this happens also with windows) when migrating over to the Global Library usage for our template. We currently have 4 new projects down the pipe, so it makes sense for us to invest the time now in migrating our template to be compatible with the new Global Library, so that we are now ready for the changes and updates going forward.

However, I have hit a potentially serious problem, that if I can't fix now I will have to make the decision to stop this migration and keep working with the "legacy libraries", but it doesn't make sense to put this off.

The problem is that when using the doors (an example below is with a garage door, however it happens with most of the door objects too) from the new Global Library, our custom door leafs that we have created for our projects no longer populate on the custom door leafs list. The same happens with the custom handles. The list is empty!

In this first screen shot, you can see that I am selecting the garage door from the Global Library garage doors and the custom door leaf list is empty. It should display our custom door leafs that we have in our company library which is loaded onto the file.

The screen shot above shows my library manager, where we have our company library loaded, as well as the libpacks of the new Global Library. This condition corresponds to the status of the behavior of the previous screenshot.

So now I add the "legacy library" to the library manager.

Still the custom door leafs list is empty. The garage door object selected is still the one from the new Global Library.

Now, if I select the garage door from the "legacy library" then the custom door leafs list populates correctly and I can select from the list of our custom door leafs.

So I am trying to figure out if this is something that we are doing incorrectly, or if it is a bug in the current global libraries somehow? Has anybody run into this? I need to make a decision if we keep working on the transition of our template to the new Global Library or if we keep the old legacy library for now, however, since Graphisoft announced that moving forward only the Global libraries will receive updates, it seems to make sense to make the transition as soon as possible.

Any insight into this is greatly appreciated!

Operating system used: Mac Apple Silicon 15.1.1 Sequoia

Betreff: Custom door leafs and handles not populating the list for selection when Migrating to Globa

runxel — Fri, 06 Dec 2024 18:54:29 GMT

@Roderick_Anderson schrieb:

So I am trying to figure out if this is something that we are doing incorrectly, or if it is a bug in the current global libraries somehow?

It is neither.

You would need to recreate your custom panels/leafs (or just open them, change the subtype, save it, then last but not least make one new leaf from scratch which will trigger the build of custom leaf list, and that should be it – from the top of my head).

Reason is the technology change of the Global Library; all the GUIDs have changed and so your old leafs are not recognized anymore.

Betreff: Custom door leafs and handles not populating the list for selection when Migrating to Globa

Roderick_Anderson — Fri, 06 Dec 2024 22:48:17 GMT

Thank you for the reply, however this does not seem to be working (the subtype option). Even though I change the subtype to "Custom Door Leaf" and then I create a new Custom Door Leaf from scratch, then only one that populates in the list is the new one I did from scratch. So still something does not quite work.

At least I may have found a workaround (by accident). If I drag and drop the gsm file of the custom door leaf or the custom door handle that I need onto the floor plan view, it will insert it as an object, which I can then turn into a morph and then save it again as a custom door panel or custom handle using Archicad 28, at least saving the time to model everything again.... Not ideal but it will have to do, although now we found another problem related to the surfaces and language that I will need to solve first, but I will create a separate post for this.

Re: Custom door leafs and handles not populating the list for selection when Migrating to Global Lib

JaimeSA — Sat, 16 Aug 2025 20:59:42 GMT

Hello Andersem.

Today I came across the problem you described and began researching to find a suitable solution.
Did you find anything more than what you described?

Re: Custom door leafs and handles not populating the list for selection when Migrating to Global Lib

Roderick Anderson — Sun, 17 Aug 2025 03:11:41 GMT

Not really, this was a few months ago, but I believe we ultimately used the technique I described on my previous reply and we re-created the custom door leafs and custom handles from scratch.

Re: Custom door leafs and handles not populating the list for selection when Migrating to Global Lib

Barry Kelly — Sun, 17 Aug 2025 03:22:02 GMT

Maybe this will help?

https://community.graphisoft.com/t5/Libraries-objects/Migrating-Custom-Components-for-Compatibility-with-Library/ta-p/631545

Barry.

Re: Custom door leafs and handles not populating the list for selection when Migrating to Global Lib

Lingwisyer — Wed, 10 Sep 2025 05:59:40 GMT

There really should be a converter provided to make these custom components compatible en masse... unlike the whole GS macro mess, this should be easy for them to provide...

Re: Custom door leafs and handles not populating the list for selection when Migrating to Global Lib

Bernart — Mon, 17 Nov 2025 10:55:42 GMT

We have the same issue in AC28 Build6100 on BimCloud project. All of our custom door leafs disappeared for all bimcloud project users. All those were built in AC28 with global libraries installed. Contacted Support and hopefully they will have a fix. I believe this is a persistent issue, but unsure how this fault is triggered.