Bug - Editor duplicates custom component on copy/paste

[Anonymous]

Repro steps:

1. Create a custom component C
2. Create a screen S
3. Add custom component C to screen S
4. Duplicate screen S

Actual result:

Screen S_1 contains an instance of component C_1.

Component C_1 is a duplicate of C.

Expected result:

Screen S_1 should contain an instance of C.

Please note this behavior also happens when copy/pasting components from a screen A to a screen B.

[PPZL]

Same problem for me and it is *really* annoying.

[PPZL]

"The issue only occurs when there are multiple component instances in a single container."

As a workaround before this bug is fixed, we should not use components inside containers...

[windywong]

Hello I just google and found here seeing this is a bug recognised and should be fixed somehow, but I'm currently still getting this auto-duplicating issue 😞 

And I just check my version is already on 23121

Did I miss something or this is still happening today? Thanks in advance.

Edit: Alright I think this is due to the "The issue only occurs when there are multiple component instances in a single container." 

Although I found this quite silly but... well this is as described. 

[NPPlatform]

@TheHandyAndy This problem still arises. Did Microsoft resolve your second ticket as well?

[TheHandyAndy]

Sorry all - it's still an issue.  The Microsoft Product group have delayed the fix until the new year.  I have a Support Case open that I'm refusing to close until they fix the issue 🙂

[TheHandyAndy]

Hi all, I've been advised that the Microsoft Product group have fixed the component-duplication issue and my initial testing in Authoring version 3.24012.8 appears to confirm that the issue is resolved for a standard container. With further testing, the issue with Horizontal and Vertical Containers appears fixed in Authoring versions 3.24013.17 and 3.24014.7.

[NPPlatform]

@TheHandyAndy That's good news!

[aa49]

Has anyone submitted this to the feature request chain? This is definitely a bug not a "feature". A reusable component should not be duplicated on copy/paste. That defeats the whole purpose of a reusable component.

[TheHandyAndy]

@aa49 as far as I'm aware the bug has been resolved following the various support requests I've submitted (see discussion above).

[eddiel]

We are still seeing this bug when we copy components from a component library between two apps.

Scenario 1:

1. We create two separate Apps - App A and App B (created in same solution).

2. We import the same Component library into both apps.

3. We create an instance of one of our components from the library in App A.

4. We copy the the component from App A to App B.

Expected behaviour - the instance of the component is copied across to App B, with no local version of the component being created in App B.

Actual Behaviour - FAIL - the instance of the component is copied across to App B, however, a local version of the component is also created in App B, despite App B having the same component library imported.

Scenario 2:

1a. We create a single App - called App C.

1b. We create a copy of App C in same solution, called App D.

2. We import the same Component library into both apps.

3. We create an instance of one of our components from the library in App C.

4. We copy the the component from App C to App D.

Expected behaviour - the instance of the component is copied across to App D, with no local version of the component being created in App D.

Actual Behaviour - SUCCESS - the component instance is successfully copied from App C to App D without creating a local version of the component in App D.

Why is this important to us?

Because we are having more than one developer work on the Canvas App.

They each work on their own instance of the app to create screen items. They then combine their changes in a master version of the app. They do this by copying and pasting from their instance of the app to the master version of the app.