Export file name missing version number

[jpmcgillivray005]

Hello, first off let me apologize if this is not in the right place. First time on the forum here. 

Anyways, I opened fusion today and when I exported the file I was working on the v## was not auto populated in the file name. Usually it is "file_name v21" for example but today it's just "file_name". Saving then does try to overwrite the previous file so it's not as if it's just hidden in the UI but still saving the file with the version. I had a pending fusion update so I applied that and restarted and it is still the same. Is this a bug or perhaps a setting I somehow disabled?

I am on version 2605.1.18 on Windows 11

[procratstinator]

Any format is fine by me, as long as there IS some unique suffix at the end of the file name. But removing the suffix entirely before adding the new system is just a very not-user-friendly move that breaks workflows. 

[lance.carocci]

You're right. While the change was well-intentioned, it's clear that the lasting value of the version tag was underrepresented in hindsight.

[jm.10]

This is a perfect example of en****tification at work.

Lock everyone into a cloud version where the user no longer has the ability to deny updates. Then start forcing changes nobody asked for. When the customers complain, gaslight them to try to convince them they're using it wrong.

YOUR CUSTOMERS ARE NOT YOUR BETA TESTERS.

[lance.carocci]

Fusion has had regular updates since its inception. If anything, we have relaxed this over time by allowing users to defer updates temporarily, and increasing the duration of the deferral. You will never be able to defer an update indefinitely because the client will become incompatible with its ever-evolving cloud services within a matter of months. At this time, Inventor is more suitable for the update-never lifestyle.

Again, just because you did not ask for this change does not mean other users didn't. I know this isn't the point you were trying to make, but we actually do have customer beta testers. If you wish to preview these sorts of changes before the general audience, I encourage you to join the Fusion Insider program, where users regularly test and provide feedback under NDA on in-development and pre-release changes.

[lance.carocci]

Question for everyone: is it just the unique version/history identifier you wish to append, or is there other file metadata of significance that you are currently typing in manually? For example, some apps have a configurable filename syntax, and there might be other desirable information like a generated part number.

[procratstinator]

Anything showing that this is a newer iteration of the file

[infoLRDXL]

For me just the ‘Vxxx’ works fine so the relation between the exported STL and the current version of the design is clear again. 

[jm.10]

The issue here is that Autodesk is apparently paying attention to some theoretical "ideal customer" and changing core behavior of an engineering tool without any way to retain the established standard. This class of software needs to be reliable and dependable. You're not developing a video game where an arbitrary change is just an inconvenience - you're breaking real workflows in ways that have real consequences.

An NDA to be able to provide feedback is also a massive red flag. For that matter, so is the fact that Inventor (claiming to not be cloud based) is ONLY available as a subscription and has no discounted maker version. Insulting.

[jm.10]

To answer the question of the functionality we're asking for: just keep the "v###"  extension as before. There's no reason to change what works. Make the "versionless" file name an option. Eventually, it might also make sense to be able to customize the filename, but adding new features isn't really as important as not removing existing ones.

And fix the bug where the version number that's appended to the filename is wrong. I already mentioned it and others have as well. It's a bug that's been around (and reported) for years now.

[lance.carocci]

---

@jm.10 wrote:

An NDA to be able to provide feedback is also a massive red flag.

The NDA is because users test in-development content which might not reach the general audience for months, if ever. As a member of many other beta programs myself, that is extremely common.

[marcus.toepke]

I think it would be best if you could set it in the preferences, with a template such as #documentname#savenumber or
#documentname#versionnumber.

That way, everyone would be happy!

[richardcoleofficiall]

It sounds like a Fusion export setting issue, not just a bug. Usually, the version number (v##) is added automatically if “Auto-increment version on save/export” is enabled.

Check these steps:

Go to Preferences → File Handling / Save Settings.

Look for “Include version number in file name” or “Auto-increment version” and make sure it’s enabled.

Restart Fusion after changing the setting.

If it’s still missing, it might be a regression in the latest update, and reporting it to Fusion support would be a good idea.

[markleeber]

We need this as an option at least!!! Seems like it would have made more sense to leave the versioning for save files in and add an option to remove it if the user did not like it. 

@markleeber - this post has been edited due to Community Rules & Etiquette violation.

[g-andresen]

Hi,

---

@markleeber  schrieb:

We need this as an option at least!!! Seems like it would have made more sense to leave the versioning for save files in and add an option to remove it if the user did not like it.

---

Please limit yourself to presenting the facts and refrain from making offensive conclusions.

günther

@g-andresen: moderation team has edited the quoted material to remove a ground rule violation which was removed in the quote´s original post. 

[thepeltzers]

I don't see "File Handling/Save Settings" in my Preferences at all.

For me the auto-version suffix for exported files was very important to my workflow and the absence of it does disrupt the way I work. Some kind of auto suffix mechanism that iterates so I can always tell which file is the latest export would be most welcome. 

[LynxEvolve]

The proper way to resolve this, in my opinion, is to follow the lead of most software for professional use and allow default file name with system variables (macro) names. 
So allow the use of Filename, Milestone Name, Body Name,  Component Name, Version numbers or other variables in a default export file name string, i.e DefaultExportFilename="Design_$C_$M_$V" or similar. This allows full control for any user, for any workflow. 

[perryMFY2P]

".....so that users can determine this naming themselves."

Well, this has always been the case, if you did not want it you could remove it. 
Now you have to add it. 

Why remove a useful function/feature if you dont replace it with something better? 

[filcuk]

For me personally, any version is important to distinguish exported files and tie those back to Fusion version for testing & review.  
As others have mentioned, I will often print many iterations of a model. Sometimes, I may want to go back and see what I've changed.  

Configurable filename would be awesome, I would like to see which component or body is being exported, if those are individually selected.  
It should be noted that this overlaps with mesh export a little bit, as I know those are not the same thing.  
For printing, I have to use individual component mesh export to achieve higher accuracy, as this is not an option in the generic file export modal, but that's another topic.  

[walsh_brendan_m]

Bring back version numbers or date fields as an option. Just has to be two check boxes. Let them persist per user. "Add version number" and "Add export date" while exporting. Default them to off for new users if you want, but at least increase the usability of this product instead of stripping it. 

[ayearofholidays]

Just here to say that I too would like the version numbers as an option back please.