Move/Duplicate doesn't pass Symbol changes

[abra100pro]

I made a symbol then duplicated it with the new Move/Duplicate and then changed the symbol afterwards – that's how it looks like after that (the selected one is the simbol original, the others are instances):

the "M/D"ed elements do not all take over the changes. the pattern of which do and which don't is always the same.

file is attached, too.

AD symbols and MD.afdesign

[walt.farrell]

The ones that are different from the original aren't Symbols; they're simply Groups.

Can you say more about what you started with, how you made the initial Symbol, and how you used Move/Duplicate?

[Hangman]

Hi @abra100pro,

You need to group the three initial instances of your symbol prior to applying the Move/Duplicate settings though whether this is expected behaviour or a bug I'm unsure since one of the three symbols is being duplicated in each instance when ungrouped...

Without Prior Grouping

With Prior Grouping

[abra100pro]

OK, I see, grouping is the solution. Thanks for the info.

However: can we agree on this being if not a bug then a very weird behaviour? There is no situation in which the ungrouped behaviour makes sense, no?

To me it's a bug.

[Hangman]

I agree, to me this appears to be a bug as I can't see any logical reason why one of the three symbols correctly moves/duplicates but the other two don't.

Hopefully, someone from the moderation team can confirm and log if appropriate.

[Frozen Death Knight]

Regular duplication of symbols keeps the symbol status of the group, so I would consider this a bug as well.

[EmT]

Thanks @abra100pro, I've passed this over to the devs for investigation.

[Affinity Info Bot]

The issue "Move Data Entry duplicates secondary instances of a symbol as a Group" (REF: AF-653) has been fixed by the developers in internal build "2.3.0.2100".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.