Bug - Editor duplicates custom component on copy/paste

[cchsod]

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.

[mgreiner79]

I totally agree with @cchsod . This is not expected behavior, and makes the idea of components pretty useless. The whole idea of components IMHO is the DRY (don't repeat yourself) principle. That is, define the component once. Instantiate it many places. Any time you need to update the component, you only need to change it in one place.

I have built a rather large app over the last month, not realizing that this was happening. Now I look at my components page and have hundreds of component copies. I dread the day I am going to need to make a change to one of these components.

[mikefju]

I'd like to share my Workaround / Best Practices to help minimize the frequency of the auto-duplicating components issue and correct before it becomes too far out of hand.

Issue: When copying Screens or Containers with at least 2 of the same Component in them, all of the Components beyond the first one are unexpectedly duplicated within the Components Tab and renamed with an underscore and number.  If the developer ever wants to update the original Component, unfortunately there are now many copies and no good way to re-link to the instances back to the original Component since they each are connected to their own library Component.

Best Practice: If you need to copy a Container (or Screen - going forward, I will just refer to a Container, but it is the same steps for Screens) with multiple instances of the same component, then you need to break down the steps as follows:

1. Manually create the Container without the Components
2. From within the Container, select all the Components (you can select all of them now) and press Copy
3. Select the newly created Container (from Step 1) and press Paste (Note: all of the duplicated Components will now reference back to the original Components)

Regular Checkups/How to Correct: Try to make it a habit to go to the Components tab from time to time to confirm that no duplicate Components have been made.  If it was just made, perform an Undo (Ctrl-Z) to backup your steps which will also remove the duplicated components.  The duplicated components currently show up at the bottom with an underscore so they are easier to spot.  If you end up with these duplicates and can't undo, then you can perform the following steps to re-associate with the original Component (too bad there isn't a Where Used to make this easier).

1. In the duplicated Component, add a red rectangle (or something visually obvious) on top of the other controls
2. Go through all screens to find the red rectangle (note: don't forget to go through your app's logic to confirm all components have been made visible)
3. For any Components with the red rectangle ("Red Component"), insert the correct Component and manually copy over any custom properties or inputs from the Red Component.
4. Copy the Name of the Red Component (into your clipboard is fine)
5. Delete the Red Component
6. Paste the Name into the Name of the new Component you just added (this will ensure that other controls which referenced the Red Component will now reference the new Component)

Until this bug is corrected, if anyone comes up with a better approach, please share.  Thanks!

[Pertanjang]

I agree with the author of this topic, this is a bug and is not working as expected by the definition of the feature "components" 
It is ment to be making life easier but is currently making it harder 😞
Please fix!   

[TheHandyAndy]

Just stumbled across this issue in an app I'm working on.  I'd fixed a minor issue in a component, then days later the same issue "reappeared", turns out it's a duplicate component <surprised expletive>. So then I'm left staring at my list of components wondering why I duplicated so many components!  Then wondering why I couldn't remember duplicating so many components!  Turns out I didn't, it was a present from the bug discussed here <sigh>.

I've raised a bug ticket with the Power Apps team.  Lets hope this gets resolved promptly.

[TheHandyAndy]

Bug has been acknowledged by the product group and a fix is being worked on/in their backlog.

[TheHandyAndy]

I've just received an update on the bug ticket:  The fix is complete and will likely be released into production in 2-3 weeks depending on their release schedule testing etc.

[alexsolexToo]

Fix is not released yet. I'm still facing issues with copy/pasting components.
Have you a place to check the release of this fix or not ? Thanks

[TheHandyAndy]

Ah poop, yes agreed - it's still an issue 😞
I'm raising another support case and will reference the previous case.

[J-Dodds]

@TheHandyAndy Any chance you have heard back on the fix for this?

[TheHandyAndy]

Hi, the update I received from Microsoft Support on 12 October was: 

"I have identified the issue and should have a fix in before EOW. That will put the fix on train 2310.5 which will be available in Preview on 10/30. At that point, user will be able to select the new version in the change version dialog. The mitigation remains the same as before. Delete the extra component definition to work around the issue. Additionally, user can copy and paste the component instances individually between containers and the issue will not be triggered. The issue only occurs when there are multiple component instances in a single container."

We'll see if all gets fixed this time 🙂