Create Version is not supported for this (configured) design

[Waitangi]

Hello!
I tried to create versions manually in my design files, as versions and milestones disappeared after the switch to the new collaborative editing hub.

In the details of my file in the data panel I click the History button to view the history window. Here I tried to create a new milestone (now Version). However, the button is gray/non active. When hovering over the button it says: Create Version is not supported for this design.

 
How so? Is it not possible to create Versions for configured designs?

Any ideas and explanations are much appreciated!

[gautham_kattethota]

@Waitangi 

Yes, it is not possible to create Versions on Configured Designs in the new collaborative editing hubs.  We disabled it in favor of creating Versions on configurations directly.  This is more granular and moves us away from the 'big hammer' approach we had in the past where Versioning/Milestoning the Configured Design would propagate the Milestone to all the configurations.  

That said, we currently do not allow Versioning configurations directly, in the context of the Configured Designs.  We however do allow configurations to be Versioned where they are consumed.  For eg., if you insert a configuration into another assembly, you can Version the inserted configuration in that assembly.  

We will be supporting the functionality to allow Versioning of individual configurations in Configured Designs in the future.

Hope this helps.

Regards,

Gautham

[joecamisa]

This is the part that helps "We will be supporting the functionality to allow Versioning of individual configurations in Configured Designs in the future."

WHEN WILL THIS BE ADDED BACK?

Thanks!

[gautham_kattethota]

Cannot give you a firm timeframe for you right now unfortunately.

Can you describe your workflow to show us how you use this functionality and if the workaround that we have right now is not sufficient for you to make progress temporarily.

Gautham

[joecamisa]

My workaround is a sad joke. 

I am creating a NEW PROJECT for EVERY DESIGN (didn't need to do this before CE Hubs!)

I no longer use SAVE (at all) I now must use SAVE AS and append my version number to the Design Name.

For example:

New Ring v1

New Ring v2 Face inc 1 mm

New Ring v3 Decrease Deboss 0-5 mm 

New Ring v4 Add Band graphics

New Ring v5 etc etc etc

All because I need Configured Design and need Version to associate my designs with "AS PRINTED" products.

Using History and updating Descriptions does nothing to help with our workflows.

[joecamisa]

I should also mention this is day 4 of the CE Hub nightmare for me.

This loss of functionality should have need communicated in advance.

[gautham_kattethota]

@joecamisa 

I know it is an extra step to create a version on a configuration (by inserting it into another design and adding version on the referenced configuration), but will that workaround not help you temporarily until we restore the functionality?  And adding description on save points in the History dialog does not help?  We apologize for the issues you are facing with the switch to CE hub.  

Gautham

[Waitangi]

I can only relate and totally agree! All our drawings and file versions were related to production, also my descriptions when saving were linked to certain versions. As they do not exist anymore the entire traceability that we have established is gone! I wish there would be a way to get the versioning back!

[Waitangi]

This is also what I thought of, but did not find the motivation to go down this road yet

[gautham_kattethota]

@Waitangi What Versions and Descriptions you had before should have migrated properly when you moved to a CE hub.  Is that not the case?  For eg., when you look at the history of a design that had Versions on it before, you dont see those Versions anymore?

Gautham

[Waitangi]

@gautham_kattethota As far as I remember, all files/designs had a version, starting at V1 when being created or saved. I had an automatic versioning with every save. This was sometimes annoying when I just activated and deactivated something or moved back and forth in the timeline, without any real change. As Fusion asked if I wanted to save changes, I rather did to be sure. So my versions in some parts were very high. Nevertheless I could reference to them. Milestones provided an additional layer, for example moving through design phases (e.g. draft, final design, in production at supplier A, ...). Now I almost do not see any file with a version attached. What I do see is the dates and times in the History dialog. However, identifying version 156 would be very cumbersome.

[gautham_kattethota]

@Waitangi can you send me a snapshot of the History dialog showing all the saves.  And did you have Versions/Milestones that you had created during previous saves that are not showing up in the History dialog?  

Gautham

[joecamisa]

Gautham, there are now TWO MAJOR ISSUES identified.

(1) LOSS OF CREATE VERSION for Configured Designs: Users (including me) have already documented the loss of Create Version for Configured Designs which we need restored as soon as possible.

(2) LOST VERSION HISTORY: In Design History now all we can see are the Changes.  There are no Version Numbers associated.  Why is this critical?  

Version numbers are how we track the Design to the Finished Product.

For example, I have a Superstar Ring that has 56 versions.  I printed sterling silver 925 versions as follows:

v17: May 2023

v30: June 2024

v45: October 2025

It is now April 2026 and a customer wants a variation on version of v30.  Before the CE Hub migration I would open v30 and work from there.

Now I don't know which version from June 2024 (there could be 20 or more) is v30.

Please see the attached screenshot. 

Please restore the Version information that we can no longer access via History.

Thank you.

[Waitangi]

Maybe it would be easier for you to implement the following:

 

-> Add a column that shows the save number in the history window, either as 
a) s13 instead of v13

b)  just an ascending number that matches the previous versioning numbers.

This should not be to complicated to implement and would kind of restore the previous versioning system, without affecting the new.

[cyan_perry]

Hi @joecamisa 

Thanks for calling this out- your history is still there, but we get that losing visible version numbers makes it harder to quickly find things like “v30.” The new experience leans more on timestamps and descriptions, which doesn’t always map cleanly to how some designs were tracked before. We’re looking into ways to make this easier to navigate and interpret for existing designs, and really appreciate you taking the time to share your workflow with us.

[joecamisa]

Thanks for the reply. Some clarifications:

(1) Losing Version numbers makes it IMPOSSIBLE for me to know which version was v30.  We need the original Version numbers back.

If you want Fusion to be used in Manufacturing you need to incorporate improved traceability, not remove a feature that provided it.

(2) You should have kept version numbers and added timestamps. 

(3) We already had descriptions with each Version we created and we were prompted to enter a Description which was excellent.

The requests remain the same:

(1) Restore the preexisting Version numbers removed during migration.   Adding Timestamps for each Version created would be a great build. 

(2) Enable Create Version for Configured Designs.

(3) Prompt for Description during each "Create Version".

Hope we can get back to where we were before the CE Hub migration.

Thanks.

[joecamisa]

Agree Fusion needs to have Version or Sequence Number automatically incremented for each Create Version. 

Having Timestamps in addition to Version numbers is great.

Create Version also needs to prompt for Version description as it did before whenever we did a "File Save".

Unfortunately my workflow requires the original version numbers I have been using for years, not new numbers.

I can't determine which version is which from the currently History table.

[hayley_burrows]

Hello all,

Thank you for your feedback.

---

@joecamisa wrote:

Gautham, there are now TWO MAJOR ISSUES identified.

(1) LOSS OF CREATE VERSION for Configured Designs: Users (including me) have already documented the loss of Create Version for Configured Designs which we need restored as soon as possible.

(2) LOST VERSION HISTORY: In Design History now all we can see are the Changes.  There are no Version Numbers associated.  Why is this critical?  

Version numbers are how we track the Design to the Finished Product.

For example, I have a Superstar Ring that has 56 versions.  I printed sterling silver 925 versions as follows:

v17: May 2023

v30: June 2024

v45: October 2025

It is now April 2026 and a customer wants a variation on version of v30.  Before the CE Hub migration I would open v30 and work from there.

Now I don't know which version from June 2024 (there could be 20 or more) is v30.

Please see the attached screenshot. 

Please restore the Version information that we can no longer access via History.

Thank you.

---

@cyan_perry has responded on (2) 

For (1), we are exploring enabling ‘Create Version’ for Configured Designs, as it was previously available in non-CE hubs.

Kind regards,

Hayley

[joecamisa]

Hayley, thanks for the reply.

For (1) great to hear you are going to enable 'Create Version' for Configured Designs which was previously available.

For (2), the cyan_perry response does not address the issue of not having the Version numbers we relied on in our daily workflows.

Removing Version Number is deleting user data - we need the data restored. 

Thanks.

[Webdad]

For me personally, I have over 2,000 STL files that have become untethered from their Fusion designs due to the removal of Versions.  My estimate is that it will take me approximately 30 hours of mistake prone hand work to reestablish these links.  After that, I'm faced with modifying my existing workflows in order to accommodate the loss of automated version numbers carrying through to STL exports.

Is there an update on when the product management team will provide information on the path forward?