topic Re: Understanding the saving a file process in Fusion Design, Validate & Document Forum

Understanding the saving a file process

Anonymous — Mon, 19 Mar 2018 16:36:20 GMT

I'm confused on saving a file, yeah shoot me, cause I ran out of ammo.

So I'm working on a single model for days and let's say I am on my 10th save. I see it shows the part as 'testpart v10'. Then if I make a quick change and save it again, it will save it as v11 and will ask me via a pop up box to enter a version description.

Questions:

1) Is the v10 just to let me know how freaking hard of a worker I am or is there somehow a v9,v8,etc saved somewhere in the cloud?

2) What does entering a 'version description' do. When I enter one I don't see that description anywhere?

3) Creating a 'New Project' is basically creating a new FOLDER isn't it? It shows the 'New Project' as some type of triangle but to me, a layman, I just see it as a first folder from the root directory.

Thanks....

Re: Understanding the saving a file process

jeff_strater — Mon, 19 Mar 2018 16:37:59 GMT

Yes, absolutely, old versions are kept on the cloud. You can see them in the Data Panel, if you click on the version number. The version description will be shown for each version:

Re: Understanding the saving a file process

I_Forge_KC — Mon, 19 Mar 2018 16:46:59 GMT

Jeff answered you on versions, I'll take a stab at number 3...

Technically speaking, you're right - each new project is a new folder at the root level. There is, however, a difference in functionality between projects and the folders within them. That difference manifests itself as the ability to link or not.

If you have an assembly in a project and you want to add a component from that same project, the file is linked. Any changes made to the component, outside of the assembly, are brought forward into the assembly. If you bring in a component from a different project entirely, the file is NOT linked. This means that the component can change (external to the assembly), but those changes WON'T make it back to the assembly. This, in essence, forks the design of that component.

Re: Understanding the saving a file process

laughingcreek — Mon, 19 Mar 2018 16:48:27 GMT

1: yes, all those versions are there, and you can open any of them up at any time via the Data panel on the left (click the waffle at the top left if you closed it)

2:the description will show in the list of your versions in the data panel. I usually put milestone info there, or maybe "version approved by so-in-so" in it. Or I'll make a note if I'm about to embark on an activity that I think may royally screw up my file, so I know where to drop back to.

3:That's pretty much it in terms of how it works. I'm sure there's more to it under the hood. The main thing is you can share an entire project with someone else, so you can both work on the same files/folders, but they can't get to the "root" directory and get into your other projects. I usually have a project for each client.

Re: Understanding the saving a file process

Anonymous — Mon, 19 Mar 2018 17:04:15 GMT

Thanks. Last question, b/c I just completely deleted an entire model by trying to delete a single version #...How do you delete a single version #? There are times when I go down an evil path and don't want to re watch the carnage develop or anyone else to see the path I went down.

I went into the online file browser thingy and clicked the v2 model I wanted to delete then in the upper right I chose delete which removed the whole model, lol.

Thanks.

Re: Understanding the saving a file process

davebYYPCU — Mon, 19 Mar 2018 20:34:31 GMT

When in the version list, you can promote any earlier version, above the royally screwed up current one.

so v11 is royally screwed up, but but v9 and v10 are ok, you don't want v10 for other reasons, you promote v9 and when doing that it becomes v12.

Might help...