Skip to main content
Infoaxon
Infoaxon
Participating Frequently
May 7, 2020
Answered

Copying components revert them to master state

  • May 7, 2020
  • 16 replies
  • 13914 views

Hi Adobe, 


Attaching the video file for reference will be a lot easier to understand but I'm trying to explain the whole scenario.

 

While working on a project I usually create a design system and the XD file is used as a library by other members of my team. Since the Co-Editing feature is still in beta and not reliable (might be because of network issues) my team divides parts of a project.

Recently, we've been using components and nested components extensively. When we want to combine the project let's say 5 screens from member A 5 from member B, the copying doesn't work properly.


Any edits made to the components lets say the change in a text is reverted to master state when the file is artboard is pasted in the original file. 

please find the next points to clearly follow my process.

  1. Create a New File A
  2. Create a master Component X (rectangle+text+icon) in File A
  3. Create a New File B
  4. Use File A as a library for File B.
  5. Use Component X in the File B and change the text.
  6. Copy the Component X from File B to File A.

 

You'll notice any changes you've done to the Component X in file B will be lost in File A.

I'm attaching the video, for the sake of forum I've reduced the quality because the video was long so that it just gets understood but if you cannot see because of the quality please reply I'll post the higher quality version.

 

 

Adobe XD version -  28.8.12.1
Creative Cloud Sync - 4.3.42.4

      This topic has been closed for replies.
      Correct answer Randy Edmunds 2

      I just tried this in v44.1 and it seems to work as expected. Note that there is a new step in recipe:

       

        2b. Publish Library

       

      With that said, what's the goal of copying a linked component in a consuming document and pasting it back in the source ("master") document: Update original component? Add a new component? Create an overridden instance? Something else?

       

      Hope this helps,

      Randy

      16 replies

      A
      AdbUser5E7C
      Participant
      March 3, 2023

      The problem continues. This is making it impossible to use components in XD.

      R
      RCarruth
      Participant
      March 17, 2023

      March 17th, 2023, and still persists. You are killing me. Please fix this. Happy to hear I am not the only one, but also this is ridiculous Adobe.

      D
      Denis5F95
      Participant
      May 19, 2022

      Hey, this bug popped up recently for me, can't say which version introduced it.

      When I copy a modified version of a component from one cloud document to another, it reverts back to the original component. It wasn't like this some weeks ago. If I paste the same asset into a new document, it keeps the modifications made.

      Following this thread this issue popped up every now and then over the years.

       

      Could somebody from the Adobe team confirm?

      D
      Denis5F95
      Participant
      June 28, 2022

      Hey again, since there hasn't been a response yet and it definitely isn't solved, I wanted to ask if this is even on the radar of the XD Team?

      @HARSHIKA_VERMA @Rishabh_Tiwari 

      marias25498642
      marias25498642
      Participating Frequently
      June 28, 2022

      @Denis5F95 I just couldn't work with this bug anymore so our team switched to Figma, and it works soooo much better!! if you can I advise you to - none of these problems with reverting to master and changing the text when you switch the instance.. 

      I
      ispypaulspies
      Participant
      December 3, 2021

      Hi all

       

      I just had the same issue on a local document I was working on (File B): I'd mistakenly updated a component on a copy of my original document (File A) and wanted to put the original component back in to the new file (File B), but when I pasted it in, it became the new component. I'd even tried renaming the 'new' component in the new file (File B) and tried copy and pasting the original component back in. Still didn't work.

       

      However, then I wondered what would happen if I put that original component in to a brand new document (File C) and try pasting it in. So I gave it a try. I copied the artboard the original component I needed was on in to a brand new, named and unsaved document (File C), then copied the component from that document into my new updated version of the original file (File B)...and to my relief it pasted in the original component with all its original states! I also tested just copying the component to a new file too, and that worked as well. I don't know if renaming the new component made any difference, I'd not tested that out, but in terms of good proactise and making sure I know which component was which, it made sense.

      So for me, problem solved.

      Just for clarity my steps where:

       

      1. Rename your latest version of your component in the file you want to copy to (or the other way round if naming structure makes sense)
      2. Make a copy of the component from the file you need. These components should now be differently named
      3. Copy that component in to a blank artboard on a brand new file (File C)
      4. Then copy that component from File C to the copied file you want it to be in
      5. Fingers crossed, you should be able to now have both components existing on the same document with all their states in tact!

        I hope this helps some of you.
        H
        Hudson5C1B
        Participant
        September 30, 2021

        This issue was first reported in May 07, 2020. Adobe took over 2 months to respond (Jul 30, 2020). Now, nearly 1.5 years later and over 10 releases, there is still no fix. What gives?

         

        The last monthly release focused on Adobe Cloud libraries. Depriorized such features until this issue is resolved and closed. Right? Give me a thumbs up/like if you agree. 

          radekj
          radekj
          Known Participant
          November 18, 2021

          It's mid November 2021, I'm running the newest version of Adobe XD (45.1.62), and the issue still persists.

          Randy Edmunds 2
          Adobe Employee
          Randy Edmunds 2Correct answer
          Adobe Employee
          November 18, 2021

          I just tried this in v44.1 and it seems to work as expected. Note that there is a new step in recipe:

           

            2b. Publish Library

           

          With that said, what's the goal of copying a linked component in a consuming document and pasting it back in the source ("master") document: Update original component? Add a new component? Create an overridden instance? Something else?

           

          Hope this helps,

          Randy

            B
            bhopkin
            Participating Frequently
            April 10, 2021

            It's really a shame. I'm in a position to choose the tool for our product, and I've been a user of the adobe ecosystem for ... lets just say a very long time. I can't in good conscience recommenend we go with Xd over Figma. It's just not an enterprise ready product 😞

            T
            thediscussive
            Participant
            April 9, 2021

            This is still an issue in version 38.1.12.2!!! Why hasn't this been priortized? My team is churning hours rebuilding components when they bring their work from separate files into our main file. 

            H
            hulmerous
            Known Participant
            February 24, 2021

            Am still experiencing this bug. What is the solution?

            H
            hulmerous
            Known Participant
            February 24, 2021

            For some reason I'm unable to edit comments. Anyway, for me the solution was to make sure the original document had all its components updated. Of course you have to be careful and make sure you actually want that. You can have some nasty surprises if you realize you were working on an instance rather than a main, and have everything reset! Luckily that didn't happen to me this time.

            shaner90351087
            shaner90351087
            Inspiring
            November 20, 2020

            This is still an issue in 35.0.12.14 . I have many layouts with lists/tables housing components that are repeated in other documents and they revert to master on copy/paste to another document. What is the resolution for this work flow killing bug?

            shaner90351087
            shaner90351087
            Inspiring
            November 20, 2020

            Correction. There appears to be a strange bug where components will revert to master on paste to another document if the linked components have NOT been updated. After updating the linked library, pasting seems to work properly.

            S
            Sushant Sawal
            Participating Frequently
            September 6, 2020

            This didn't fix the bug.. It's very difficult to work with this because you literally have to redo your work every time you need to change things from one document to another. 

            Are you looking into this bug? When can we expect news on it? 

              HARSHIKA_VERMA
              Community Manager
              HARSHIKA_VERMACommunity Manager
              Community Manager
              September 7, 2020

              Hi Sushant,

               

              Sorry to hear you are still experiencing the issue. Would you mind telling us the OS and XD version of your machine? The bug status shows that the bug is fixed with XD 32 version. Could you please check on XD 32.2 version and share the results with us?

               

              We will try our best to investigate on it.

               

              Thanks,

              Harshika

                Vivesh Ingle
                Vivesh Ingle
                Participating Frequently
                September 8, 2020

                Hi Harshika,

                bug is fix XD 32.2 but letest update XD 32.2.22.2 it's comeback.

                I'm useing macOS High Sierra and  XD 32.2.22.2

                 

                Thanks

                Vivesh

                B
                bhopkin
                Participating Frequently
                August 18, 2020

                Same here. Are there people who don't have this issue? 

                Show more replies
                Terms & ConditionsAccessibility statement
                Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices