Keynotes ghost conflicts

[Lucian Laculeanu]

So... We are in the second (basic number) iteration of the software using native Keynotes tool.

When are we going to not have the issue of ghost conflicts?

Why do we have to still go through endless maneuvers of deleting, exporting, updating hotlinks, saving, re-mapping and re-importing to clear this issue?

Is this going to be solved by the time I see 4 in the beginning of the AC issue, or should I hope retirement will make this issue dissapear for me?

Operating system used: Mac Intel-based Tahoe 26.5.2

[Barry Kelly]

Are there other posts here that describe this issue?

Have you reported it to your local support?

Barry.

[Ignacio Azpiazu]

[I never used Keynotes, but:] I asked GPT and it says the Keynote database can be brought from one file into another, similar to attributes with Attribute Manager, but through the Keynotes palette.

Is it then any different from attributes in multi-file projects, where you want to have one file that is the master for attribute management, in which you create new attributes or into which you bring in any intentionally or accidentally created in the other files, and from which you overwrite all the other files whenever there is a conflict (and yes, republish and update modules)?

https://chatgpt.com/share/6aa74e34-0898-83e9-b5ab-12533b513749

[Lucian Laculeanu]

@Barry Kelly It is a bit worrisome that my post is the first one on this issue, since it is not isolated to my project(s) and environment.
A shortcut that works most of the times is exporting the set you want, import in all hotlinks if used, close hotlinks, delete keynotes from "central", update hotlinks and then re-import... But the remaining "sometimes does not work" are the frustrating happenstances.

@Ignacio Azpiazu Nice to see you around here my friend! All other bases are covered 🙂 Thank GPT for me

[Barry Kelly]

@Lucian Laculeanu 

The reason I asked if there were other posts is so I could merge this one to them.

Keep it all tidy.

A quick search of "+keynote +module" didn't seem to find anything interesting.

I am sure I have read something somewhere, I just can't remember where.

But if this is the first time it has been talked about here, then could you provide more detail on what a 'keynote ghost conflict' is and maybe show some examples.

I know how keynotes work, but I have never had the need to use them.

Especially not with modules.

I would assume like attributes. the keynotes in both the master file and module file should be the same, otherwise conflicts can be expected.

Barry.

[Lucian Laculeanu]

@Barry Kelly 
Sorry for the late reply. Had some firs to put out and this one still burns me.... Here's the story:

In my BIMcloud basic I am hosting a file that has another one hotlinked into it.

Main file contains a "main house" and the hotlink an ADU.
I am using the keynotes for Elevations and Sections in this case, and since we are using common keynotes for both objectives as they will use same mats and construction methods, both files have the same set of keynotes.
If I choose to modify a keynote in the hotlink, in the main I will get a notification that there is a conflict in that specific keynote with the one in the hotlink. That is awesome because I am counting on ArchiCAD to detect stuff like that.
The part that is not awesome about it, is that the Keynote disappears form the legend until resolved. You can imagine the problems that can rise from here...

EDIT:

END of EDIT

I forgot to mention. To add assault to injury, those ghost conflicts are not necessarily the same when you look form the hotlink side in cade you have the main hotlinked back into the "module" for some reason...

I am continuing the edits, and with the risk of remapping a ton of keynotes, but with the intent of having the same text and callouts without missing any characters or rogues spaces, I am exporting all Keynotes from the file I've just edit and import them in the one I am detecting the conflicts too.

Well... even after multiple methods of doing that, that tend to be more like fishermen superstitions than a BIM management items, I am still getting conflicts reported, although the keynotes are the same in every way.
I tried every combination of import, save, send and receive, update hotlinks and scented aromatherapy stiks that I could imagine and still get these "ghost conflicts"
The method I just revealed earlier in my previous post was the one that worked...once. Attn! When doing the update, you should not have the hotlinks open!

I can't shake those at all now... 
Here is how they look like when you expand. The black ones are form your active file and the ones shown in gray are from the hotlinked.

I am buffeled.

I like keynotes. I think they are the best automation tool ever, shortening unnecessary edits in drawings by many many hours, but this is beyond frustrating.

It should be just a simple task/tool of text comparison, but there is something that makes the file remember that it had those conflicts and permanently mark those particular keynotes as such regardless if they are absolutely the same.

  

[Lucian Laculeanu]

OK...So... Here is the absolute B O M B (in case national security is scanning this)....

If you get these conflicts, DO NOT DELETE and reimport, especially when you have a ton of keynotes mapped, before you do this:
(sounds like a bad tick-tok but stay with me)

In your current file, with the keynotes reserved, open one that has "Conflict with hotlink" displayed.

If you will click in the Description field like you would edit the text there, but then just click out on something else, the program will probably reevaluate the key with the hotlinked one and will see that is the same and cancel the conflict.

MIND BLOWN!!!!!!!

That simple!
this does NOT solve the question - why ghost conflicts appear?, but don't be like me and try this before you panic.

If this does not sole it for you, then you are back to my original problem
I need to go now and remap keynotes in 4 elevations and 9 sections. A 6-pack will not be enough today