Question

Instances disconnecting when components are moved from one file to another in same project

Forum|Forum|2 years ago
February 28, 2024
15 replies
1619 views

I have been experiencing an issue lately that I have never had before. I have 2 files within the same team project, one used for components and one with the main designs. Sometimes, I like to create components in the design file and then move them to the component file once they have been approved. However, lately, when I cut and paste them into the component file, then publish them, the instances in my designs disconnect, and when I click on the instance it says “restore component”. I know to avoid this, I can publish the design file and then move the components, but I swear I have never had to do this in the past. Was this an update? Is it a bug?

Ask the community

This topic has been closed for replies.

Show previous replies

Thanapat_Hongpaisanvivat

I have the same problem when I relocate the master to my design system file.

And when I click instance to go to main component it’s say “Restore component”

Gayani_S

Community Support

Hey @Thanapat_Hongpaisanvivat, thank you for reaching out!

I had a look at the support ticket of the user who flagged this post and there were some interesting findings.

Our support team took the following steps to reproduce the issue:

```
  Create new file
```
```
  Create new component 
```
```
  Create 2 instances of that component
```
```
  Cut main component 
```
```
  Open new file
```
```
  Paste main component 
```
```
  Publish library
```
```
  Return to original file
```

  Instances now have "Restore component" in the design panel

They’ve confirmed that this is currently expected behavior for copy/paste, as well as cut/paste of an unpublished component.

When we cut a component from fileA, we delete the component in fileA. If the component is pasted in another fileB and republished, two things can happen:

if the component was originally published from fileA, the server will see that the component has been “moved” to fileB, so once it is republished in fileB, fileA will see it has updates to accept to relink the instances to the new published version from fileB
if the component was not published in fileA (which is the case I was describing), pasting in fileB will not count as a “move” and the instances won’t receive updates and the backing component will remain deleted.

I hope this information helps clarify, but please let me know if you have taken different steps or if you habe any other questions!

Thanks,
Gayani

I

Isabelle_Langlois

Hello,
I am experiencing the same issue in 2 of my projects, but after moving my master component from one page to another in the same files. What can cause that and how can I resolve it? Thank you

Gayani_S

Community Support

Hey @Isabelle_Langlois, sorry for the issues!
Could you try opening your working file and running a Quick Action called “Repair Component Connections”? This command has a similar affect to fetching the most updated version of the main component, without you having to manually change and re-publish the main component and accept updates in subscribed files.
I’ve included some instructions on running the command below.

Open the affected file
From the main dropdown menu in the top left, navigate to the “Quick Actions” search bar.
Search for “Repair component connections”
Run this command

Please let me know how it goes.