copy / paste new not affected by roll back history and update original component

[Anonymous]

Sequence of operations :

Copy component 1 , Paste new to create component 2 , roll back history to before copy , update component 1 ( sketch and holes ) , move history back to end.

Component 2 is not updated.   Why not ?

[HughesTooling]

Paste New creates a new totally independent copy with no history back to the original. What you're seeing is by design.

Mark

[Anonymous]

How do I get an independently movable copy of a component with history ?

[etfrench]

That doesn't add up.  When you roll the timeline earlier than when the copy was made, the copy should have any edits made to the original.  That's the whole purpose of the timeline.

[TrippyLighting]

---

@etfrench wrote:

That doesn't add up.  When you roll the timeline earlier than when the copy was made, the copy should have any edits made to the original.  That's the whole purpose of the timeline.

---

A copy/paste-new component is truly independent.

[jeff_strater]

Paste New is not a feature, it is an operation.  When you Paste New, there is not a Paste New feature in the timeline, the features that contribute to that component are just copied into the timeline.  

Before:

[jhackney1972]

---

@Anonymous wrote:
How do I get an independently movable copy of a component with history ?

---

You can get a MOVEABLE, as in drag around the screen,  copy of a component with history simply by selecting a component in the Browser and select Copy and the Paste it into the assembly.  It will update to match an changes in the original component and you can move it anywhere you desire.

[Anonymous]

That is what I expected but when I copied and pasted an assembly of two
joined components , one of them did not move correctly.

[HughesTooling]

When you copy a component with joints then paste new joints referencing other components are converted into capture positions. Personally would like to keep the joints and if they lose reference just show a warning but unfortunately doesn't work like that.

Here's an example where the first joint references the main component, after paste new the joint is converted into a capture position. The second joint is between the 2 components in the subassembly and is maintained after the paste new.

Mark

[TrippyLighting]

Share your model and I’ll tell your what the problem is. 
Export as a .f3d file and attach to next post.

[Anonymous · Accepted solution]

I started again using a different sequence of operations and got copy / paste to operate as expected.

[Anonymous]

I understand that copy/paste new is independent. But it should take a copy of the component at a specific time in the timeline. When you roll back beyond this point and change the original component, the copy command should than see the changed component and copy that. It also generates a base feature.
Why does it take the status of the component at the time "copy/paste new" was executed and not the status it has according to the timeline?

Copy/paste new is somewhat usable. But when you recognize an error in the base component on which the copy is based and you have already done a lot of work, you are screwed. Because a simple changeof the base component in the timeline before the copy/paste new is intended does not follow into the new component.

[jhackney1972]

I accomplish your workflow you described in your post, I suggest you change your workflow.  In the Screencast I demonstrate using the Boundary Fill command instead of the Copy/Paste New command sequence.  This method will allow you to move your timeline back, add features to the original and then have them propagate to the copied (boundary filled) component when you drag the timeline back.

[Anonymous]

Hej John,

Thank you for that great and helpful post, appreciate! From looking at your screencast, this does exactly what I wanted. I will give it a try tomorrow, as it is already 20:00 o'clock in Austria.

I will let you know if that workflow does the job.

Thank you!

Kind regards, Norbert

[jlarsonLP454]

Wish I had realized this before I spent a day working on the "paste new" part. It's very unintuitive that Paste New creates a dumb solid rather than taking the history into account. To anyone at Fusion reading this, I'd propose a UI change to fix this:

There should be three paste options:

• Paste (with some helpful hover text to explain this creates a dependent copy of the part, what my previous CAD called a "Share")
• Paste as Base Feature (with text, "WARNING - ALL HISTORY AND PREVIOUS ASSOCIATIVITY WILL BE LOST!")
• Paste a Divergent/Derived copy (with explanation to the effect that all history is captured up to this point but changes to the new part moving forward will not affect the old) - this would behave exactly as John demo'd in his video using the Boundary Fill command.

Those names and explanations need a bit of cleanup, but this would be very helpful.

John, thank you for the video showing the workaround. I'll be using that a lot.