Bring back the Version Number

[Webdad]

I've worked with Fusion 360 for 8 years, and developed workflows and SOPs that were heavily dependent on the version number in both the view as well as saving STL meshes.  The recent decision to not only stop adding the version number to mesh saves but also remove the visibility of the version number completely within Fusion 360 has severely crippled by ability to be productive with this software.

What recourse, besides moving to another CAD solution, is there for regaining lost / crippled functionality?

[RajkumarIlanchelian]

@Webdad Its now saved as date and time and you can see it in History. 

[Webdad]

That's really not acceptable.  The date/time is buried further in the UI and is not brought forth at time of export/save as mesh for the target file name (really, it would be an even bigger mess if it was). 

Now I'm forced to have a directory window open outside of fusion in order to maintain the version sequence. 

1. I have to open windows file manager

2. Navigate to the target directory outside of fusion

3. Sift through the directory contents to find the previous file

4. note the previous version

5. Come back to fusion

6. manually enter the incremented version. 

All before I can save the new version.

Previously, when the version number was present and carried through, once I selected the target directory at the start of my editing session, I never had to go back to selecting or opening that target directory from within Fusion.  It was basically a set and forget operation.  Since you don't use windows standard save dialogs, since you want to offer save to cloud as well as save locally, I'm forced into this workflow-breaking sequence that:

A. takes additional time

B.  Opens up the opportunity for user error

C. Requires additional information tracking and typing

Truly a degradation in the usability of this software.  Meanwhile, you're throwing in AI slop with obscure, specific sequences required to deactivate it. 

Really a step back for Fusion.

[RajkumarIlanchelian]

@Webdad I have passed on this feedback to our product management team. Thank you for providing us with your experience. 

[Webdad]

One additional point to pass along, I am literally stunned that, what I thought was a foundational tool in an industry requiring extreme precision for design and development projects large and small, would take a decision that essentially cuts their users off at the knees by removing functionality that seems essential to managing project development.

Was there even a shred of discussion about how this change in a product that has been around as long as Fusion has would impact a user base that prides itself on precision and accuracy?  

As the team to look up the term "jump the shark".

[lance.carocci]

We have years of feedback on the old versioning system, complaints among them that file version has more weight and significance in their organization than merely how many times the save button has been clicked. This is why we moved to dates and revisions - because version is something that many choose to increment manually as part of revisions and independently of date-based file saves. This change was not made in isolation - there is an entire section of Fusion file metadata dedicated to Product Lifecycle Management, and appending version to a filename associated with save count was often confused with internal product revision.

Having said that, I understand the significance of wanting to differentiate file exports - it would be ideal to have some sort of configurable filename export syntax.

[Webdad]

Ok, I get that.  Understand that not everyone views version through the same lens.  That being said, there are people like me and I'm sure others, that do place value on and depend on the original versioning system.  I'm curious why this couldn't be an enterprise level flag that would hide or reveal the version?

Adding a capability to configure the export with version would definitely be a step in the right direction, but without an easy way to see that version in Fusion it would be a disappointment.  One of my workflows, for better or for worse, is to validate my directory contents of STL files and the designs in Fusion are all on matching versions, so that when I go to production to print the files for jobs, I know that I'm printing current versions.  Previously this was a very simple exercise to bring up the directory list alongside the list of project designs and visually compare STL version numbers against the version that was clearly shown on each design.

The same workflow now is:

For each design:

1. click the drop down to open the "uses / drawings / etc" table

2. Click the "history" button

3. Note the latest version, somehow

4. Compare to the corresponding file in file explorer

5. back out of that design

6. rinse and repeat

I was starting to use the "flag", can't recall the previous terminology, "major version"?, and that appears to have been discontinued or absorbed into the history panel.

The current drop down from the data panel for a particular design has very little value for me, compared to the previous version that contained the versions and the "flag".  

[Webdad]

I'm hearing that this version change only applies to Team Hubs with Collaborative editing.

Can I get out of the team hub and collaborative editing somehow?  Roll back to whatever is the configuration for not a team hub?  I looked on the web settings, saw the collaborative editing but no way to deactivate it or downgrade the team hub.

[RajkumarIlanchelian]

@Webdad Going back from a CE hub is not an option. We are migrating all the hubs to a CE hub at this time. 

[joecamisa]

This loss of functionality is completely UNACCEPTABLE.   

I use ONLY Configured Designs and have ALWAYS used Versioning.

The History Changes functionality is NO REPLACEMENT AT ALL for Versioning - please don't tell anyone that it is.

Disgusted that we have to ask that this basic functionality be restored.

The arguments for the change are ludicrous - it comes down to the cost of implementing Versioning for Configured Designs under the new CE Hubs.

Exceedingly frustrating for users who will never use Collaborative Editing and ALL USERS who need Configured Designs.

[joecamisa]

Please add me to the list of disgusted users for the Product Management Team.

If the Product Management Team understands how Versioning is used how could they approve this loss of functionality?

Please tell us why Versioning cannot be restored for Configured Designs under the CE Hubs.

Thank you.

[joecamisa]

I completely agree.  When I noticed I could not Create Version for a Configured Design I was at first sure it must be a CE Hub bug.

Guess the joke was on me as I created a Case for this issue only to hear it is a "feature" of the new CE hubs - such a joke.

[joecamisa]

"appending version to a filename associated with save count was often confused with internal product revision"  Are you serious? 

[joecamisa]

I asked the same question - afraid we are stuck.  My workflow just got MUCH more complex.

[joecamisa]

There are no good workarounds for this loss of functionality.  We are just stuck with a terrible feature deprecation decision.

[joecamisa]

That is no substitute AT ALL for Create Version and Create Milestone as you must we aware.

Please don't users it is.  Thanks.

[joecamisa]

How does a group of users lobby for lost functionality to be restored?

Until we join together we will be ignored. 

I know we will probably be ignored anyway but at least we will have tried.

[austinengineering1]

Is there a way to automatically append the date and time (which has now replaced the old versions paradigm) for an exported model (e.g. STEP or STL) to the file's name? Previously when exporting to STL for example, I could easily know which version was which (e.g. file_name_v7.stl), which I found helpful.

[joecamisa]

Hi Austin, I completely agree that the Version number was helpful.

In my Fusion workflow the Version number is how I associate a Fusion Design with a 3D printed product so it is a requirement.

Two issues are:

(1) how do we associate years of Fusion Design versions with printed products if the Version number is no longer available. 

I haven't heard an answer to this question so it remains an issue for my use of Fusion.

(2) when can we get Version numbering restored for Configured Designs?

I think the Fusion Team is going to do this (?) but I haven't seen a timeline.

[lawrenceWDVL5]

The old versioning may not have been optimal, but it at least worked. The new way to version which I kinda get, still doesn't show up in the data panel. All that shows is an icon which indicates the project file has been versioned. To find out what version it is we're expected to open that pop-up history sub menu which is ridiculous since it also locks out the rest of the UI. As another mentioned their work around was to have the browser account open just to view/maintain the version changes.

And before someone says, "well just mouse hover over the icon". Hey guess what, in the data panel mode it only outputs "Version" no number. One has to be on the new Home mode to have that mouse over the version icon work properly. On top of that even the new detail panel doesn't show the Version. Heck there's no option in the new Home mode to access the history. I've only found access from the Data panel mode and web page "Now" drop down. Can these at least be consistently named? Did someone plan to salt the earth for version control?

Just show the version number with the project file and save us all the hassle, please.

Anyway these UI updates have been quite frustrating. Please Fusion team if your going to make major changes at least make sure it works before rolling out to production.