Attribute manager critical bug AC23 [LOST DATA]

[runxel]

Beware! There is a critical bug in the attribute manager which will lead to LOST DATA if you do not realize this on the spot.
Let's say you want to exchange your layers:
Easy enough, you might think, just go into the AM and get the layers you want from the left into the right pane. However: "append" and "by name" are broken commands. Only "by index" works reliable.
If you use the others, the first layer will always be converted to the ARCHICAD-layer. If you realize there is some f*ckery going on and try to get the missing layer in again, you will notice that the name gets an "(1)" slapped on, meaning there is already an item with the same name (you can't rename this one back btw!).
But if you try to append the ARCHICAD layer back to the left, you will notice, it does not retain the original name – it's in some kind of limbo state where it does not have that name anymore but also doesn't allow to have another item bearing it.

The workaround is either:
- only using "by index"
- always selecting the ARCHICAD layer as well, if you appending from left to right

Hopefully Graphisoft notices and fixes this horrible bug.

[Barry Kelly]

I haven't tried this but it does look like it is a bug.
The problem with 'Append' is it will use the next available index number, so if there is nothing on the right the next number is "1".
The problem with this is that layer number "1" is always the "Archicad Layer", so that must be why it is changing name.
So when appending layers, the Attribute manager should always include layer "1" automatically or when appending start with "2" if nothing is there.

The work arounds you mention will work.
Include the 'Archicad Layer' yourself when appending or use 'By Index' (which is always my preferred option anyway).

Barry.

[Ghaleb Khadra · Accepted solution]

Hi All,

Thanks for pointing this out to us! I agree completely that this is indeed a serious issue! Thank you very much for sharing it with everyone here! Sincerely, thank you!

I have forwarded this issue to the development team, and they will investigate this as soon as possible!

Once more, thank you so much!

I wish you a great day.
Kind regards,
Ghaleb

[Barry Kelly]

Ghaleb wrote:
I have forwarded this issue to the development team, and they will investigate this as soon as possible!

Once more, thank you so much!

Thank you Ghaleb for picking up the problem and passing it on.

Barry.

[Ghaleb Khadra]

Hi All,

Just a quick update on this issue:

I have taken this up with the development team and we confirmed the seriousness of this defect.
We have added this into our defect database, and we prioritized this accordingly.

For the time being, I would like to recommend to avoid using "Append >>" and "By Name >>" and instead use "By Index >>" if applicable to your workflow.

I extend my thanks to @runxel for posting and pointing this issue out so that everyone can be aware of it.

I hope we will see this fixed as soon as possible.

Once more, thank you all and I wish you a fantastic day!
[Stay Active. Stay Awesome everyone!]

Kind regards,
Ghaleb

[runxel]

Thank you so much for taking notes and passing that one on! ♥
Have a great day as well, Ghaleb! 🙂

Ghaleb wrote:

I extend my thanks to @runxel for posting and pointing this issue out so that everyone can be aware of it.

I hope we will see this fixed as soon as possible.

Once more, thank you all and I wish you a fantastic day!

[runxel]

@Ghaleb
By the way: some users are missing the layer extension as its own column in the Attribute Manager.
(I know that the extension is there, appended in the format "layer-name.extension", but you can't sort by extension)

[Ghaleb Khadra]

Hi runxel,

Thanks for your answer!

Actually, we already have such a wish (Sorting Layers by Extension) in our system so I added your entry into it, which gives it more weight.
(For reference, the Wish number is 2244)

I hope this will get implemented in the future!

Have a great day!

Kind regards,
Ghaleb