topic Re: Editing zones within schedules in Project data & BIM

Editing zones within schedules

GG_rakurs — Fri, 16 Oct 2026 18:12:36 GMT

I have an issue in a (relatively) large project with editing zones directly from schedules.

In this project, I have iceberg stories containing different hotel room types, and above them, several hotel stories. The issue is that when I schedule all the zones in the project, I can easily edit those that are in iceberg stories which are very simple and small. But when I try to edit non-hotlink zone placed on a "normal" story, it's a nightmare because after every edit (and even without pressing enter - as you know, Archicad updates values a second or so after you stop typing) Archicad starts jumping from schedule to floor plan to limbo to floor plan to schedule and then settles. So, every single change becomes a ten or so second job. I have not encountered this before. We all know that schedules are not as fast as excel is, and we've learned to live with that. But to have ten seconds between editing two IDs that need changing? Not acceptable. I had to redo IDs (and names, and numbers) for hundreds of zones because we decided on a different format for them. It was faster to do it on the floor plan, and then check if I missed any on the schedule. Truly an awful waste of architect's time.

Has anyone encountered a similar problem?

Operating system used: Windows W10Pro 22H2

Re: Editing zones within schedules

BrunoH — Sat, 17 Oct 2026 09:15:11 GMT

Hi GG_rakurs,

"I had to redo IDs (and names, and numbers) for hundreds of zones" can't you use the ID manager for that ?

Re: Editing zones within schedules

GG_rakurs — Sun, 18 Oct 2026 14:08:40 GMT

Thank you for your suggestion. I tried playing around with the tool but I don't find it too intuitive. I will spend more time getting used to it.

To further expand on the issue, I've saved the project as a 29 pln and opened it with Archicad 29, and, lo and behold, editing zones in schedules works as expected.

Conclusion: it's a bug in Archicad 30.

Re: Editing zones within schedules

runxel — Sun, 18 Oct 2026 14:58:04 GMT

@GG_rakurs schrieb:
Conclusion: it's a bug in Archicad 30.

Please open a ticket with support so it can be fixed, if it's indeed one.

I understand that you did this with a migrated file; did you test it with a new file as well?

Re: Editing zones within schedules

Stefan L_ — Thu, 22 Oct 2026 00:00:47 GMT

@GG_rakurs schrieb:

.. as you know, Archicad updates values a second or so after you stop typing...

There's only one valid value for:

Options > Work Environment > Dialog Boxes and Palettes > Dialog Box Auto-Update Delay

Betreff: Editing zones within schedules

GG_rakurs — Mon, 19 Oct 2026 08:36:03 GMT

This genuinely made me laugh. Thanks!

Re: Editing zones within schedules

GG_rakurs — Mon, 19 Oct 2026 09:02:24 GMT

I did open a ticket. I would need more extensive testing because even in my file this works with "simple" (iceberg) stories that only have one zone. I will try out if it happens in a new file.

Betreff: Editing zones within schedules

Stefan L_ — Mon, 19 Oct 2026 09:21:09 GMT

@GG_rakurs schrieb:

... made me laugh...

😊

Apart from the real problem (unusable slow schedules&editing), I'd kick the Element ID and go for expression based properties.

Re: Editing zones within schedules

GG_rakurs — Thu, 22 Oct 2026 00:07:18 GMT

Oof. It happens in a brand new file with a default template. When I created a few zones, and I tried to edit them, it showed the same behaviour, although it was much faster since it's an almost empty file. But loss of focus when pressing enter remains and it's a process measurable in seconds, not tenths of a second as it should.

Floor plan:

Schedule:

Re: Editing zones within schedules

GG_rakurs — Fri, 23 Oct 2026 12:06:37 GMT

It seems that the culprit is Windows 10. I still haven't tried to see if the same issue occurs on 11, but I will in the coming days.

It is very disappointing that Windows 10 machines (that are not Windows 11 compatible) are being turned into e-waste. I'm not blaming Graphisoft for that - it is very strictly Microsoft's decision. Graphisoft has the following system requirements regarding the OS:

If Microsoft decides that Windows 10 is in End-of-Life stage, Graphisoft's decision to de-prioritize their software's accessibility on Windows 10 is perfectly logical and expected. It doesn't make it less unfortunate, though, especially since there is no Linux version and that means there is no future for those same machines for the same tasks.

I will explore this thread's issue in further detail in the following days, when I get some time to try it on my only Windows 11 machine, a laptop.