Archicad 29 Template Migration – Door Tags & Library Issues

[Shir_2025]

Hello Everyone,

I have recently migrated my Archicad 28 template to Archicad 29 using the Central Innovation Migration Launchpad.

The migration process appeared to complete successfully with no reported errors; however, I have noticed that the door tags and door labels are no longer functioning correctly within the migrated template. The tags either do not display the expected information or are not reading the door data properly.

Has anyone experienced a similar issue when migrating from Archicad 28 to 29? If so, could you please advise what may be causing this and the best way to resolve it?

I am also interested in hearing about any other issues or items that users should be aware of when migrating templates to the new Archicad 29 library packages. With the transition from the previous Australian library setup to the new global library packages system, I want to make sure I haven't overlooked anything that could create problems later on.

Some specific questions I have are:

• Are there known issues with door/window labels after migration?
• Do old favourites need to be recreated or updated?
• Are there common attribute mapping issues to watch out for?
• Have any schedules, classifications, properties, or expressions been affected by the new library structure?
• Are there any Australian-specific library components or workflows that require additional setup in Archicad 29?

Any advice, experiences, or recommendations would be greatly appreciated.

Thank you in advance for your help.

    

[Lingwisyer]

I would assume some macro is missing. What are the library warnings? Are there missing objects?

[Shir_2025]

How would you go about fixing that?

There are no missing parts that have anything to do with the doors. I have included a screenshot of the door setting not showing the option Tags and Labels compared to default Archicad template which shows it

[Shir_2025]

Is there anyone that maybe able to help as I have tried looking everywhere to find a solution?

[Lingwisyer]

What are those warnings?

[Shir_2025]

@Barry Kelly

[Barry Kelly]

I'm with Ling.

Check the warnings in the Library Manager.

The 'Tags & Labels' in the door settings is controlled by the library object and macros.

I suspect something is missing or maybe something is doubling up with old and new libraries and causing this issue.

Don't be using the 28/29 Global libraries together with the old 27 or before monolith libraries.

Confusingly the old monolith library in 28 was called 'Library 28', but it is actually the old 27 library.

It will use the old macros and may conflict with the new macros in the global libpacks.

But expand the warnings to see what that tells you.

Barry.

[Shir_2025]

These are just missing Attributes and objects which shouldn't affect it 

[Shir_2025]

Hi Barry 

I have review the warning signs and it is only attributes and objects missing but nothing to do with Library objects or macros missing ! 

[Barry Kelly]

Lots of duplicate library parts.

There ideally should be none.

And lots of MASTER_GDL objects, these can have strange effects on library parts.

Not knowing your project, it is hard for me to say what you need to delete to clean this up.

You can expand those further and they will give you a path to where they are located.

They are probably in your embedded library.

If you start a new file from a clean Graphisoft template in 29 and have no issues, then that leads me to believe it is a problem with the loaded libraries.

Experiment a little and start deleting objects from your embedded library.

When you select them you will see if they have been used or not in the project.

Especially delete the MASTER_GDL files.

See if that makes a difference.

Don't save the project (or play with a copy), unless you are happy with the outcome.

Maybe create a backup copy of the original file so you have something to come back to if it all goes pear shaped.

Barry..

[Lingwisyer]

And the library screenshot in the file that does work is not reporting any library issues.