Why does my fasteners document automatically update versions, with no changes to document?
chrisjh777
Member Posts: 211 ✭✭✭✭
I have all my fasteners in a single repository (document). I use this document as the source for my fasteners to be inserted into assemblies. Works great.
However, every 3 weeks or so Onshape insists in creating a new version of the document, even though I have never changed anything in the fastener document. When I look at the version menus to see what the changes are, it shows "Automatic Update". See below image.
Why is this so? Surely, with no changes, it shouldn't be necessary to create a new version.
Link to my public fastener document here:
https://cad.onshape.com/documents/57b96f63e4b01fb4781d2a27/w/c71fcc952450fbc30e65b191/e/f7c4cf01b011bd7b0c7d76d0
However, every 3 weeks or so Onshape insists in creating a new version of the document, even though I have never changed anything in the fastener document. When I look at the version menus to see what the changes are, it shows "Automatic Update". See below image.
Why is this so? Surely, with no changes, it shouldn't be necessary to create a new version.
Link to my public fastener document here:
https://cad.onshape.com/documents/57b96f63e4b01fb4781d2a27/w/c71fcc952450fbc30e65b191/e/f7c4cf01b011bd7b0c7d76d0
0
Answers
-
I don't keep close enough tabs to be sure but I've noticed this behavior and I'm left wondering if I've made a change that I should update. I'm usually somewhat sure that I didn't and likely it's a silly auto update. Which causes me to think that If I can't trust the the update icon then why do we even have it. I now just ignore the update icon unless I know that I just changed something. +1 for fixing this irritating behavior.
0 -
That sounds like the same schedule as the Onshape product updates. Maybe the two are related.0
-
Hi All,
Whenever we make updates to Onshape (corresponding to the 'What's New' posts in the blog), we have to upgrade your documents to use the newest version of the Onshape standard Featurescript features. These changes are guaranteed to not change the geometry of your part studios and assemblies, but often come with performance updates and bug fixes. You should see these 'Automatic update' versions approximately every three weeks; hopefully they won't be as irritating with some more knowledge about their origin.
Happy Holidays!Jake Rosenfeld - Modeling Team0 -
@Jake_Rosenfeld If the updates are causing linked parts to show that there's a new version or causing my drawings to show that they need to be updated then there is no amount of knowledge that will make them less irritating. I truly hope that you are working on this and assume that you didn't actually mean to say that this is how it is and we just need to deal with it.
0 -
@_Ðave_ ,
I didn't realize that these versions were causing annoyance past just appearing in the version tree. It does sound annoying to have to update your drawings and links without any geometry changes! Have you guys submitted an improvement request? That's the best way to get bugs like this on our radar.
Best!Jake Rosenfeld - Modeling Team0 -
OK Jake,
I raised an IR here: https://forum.onshape.com/discussion/5454/version-change-only-if-document-content-changes#latest
Regards
Chris Humphris0 -
Automatic updates do not cause a new version to be created, only an entry in document history.
@crisjh777, The new version 24Dec16 must have been created by you. Did Onshape prompt you to publish a new version?
If no new version is published the linked parts will not be prompted for update. As @Jake_Rosenfeld mentioned, the reason for Automatic update is to make new FeatureScript library accessible for this document. As part of Automatic update process we synchronize all the drawings which have been in-sync with their sources before update.0 -
Hi Lana,lana said:Automatic updates do not cause a new version to be created, only an entry in document history.
@crisjh777, The new version 24Dec16 must have been created by you. Did Onshape prompt you to publish a new version?
If no new version is published the linked parts will not be prompted for update. As @Jake_Rosenfeld mentioned, the reason for Automatic update is to make new FeatureScript library accessible for this document. As part of Automatic update process we synchronize all the drawings which have been in-sync with their sources before update.
From time to time, I get prompted by OS to create a new version when I try to insert a part from my fastener library document into an assembly.
Whenever this happens I do no see any means to ignore the prompt, so I simply comply with the request to create a new version so I can get on with my design work. Otherwise I cannot continue. This would explain the new version I was forced to create on 24Dec16.
At no time have I intentionally changed the fastener document.0 -
Hey Chris
The blue message bubble indicating that the document has changes in it and needs versioning is purely informational. You can choose to ignore it and keep inserting from last version that you have saved. We will look into ignoring such automated upgrade changes.
Thanks
Raj0 -
While your working with this, please add possibility to link current version of doc.. This version creating has gotten out of hands, I think I have more than dozen versions off every document I have and there is only couple of docs where I actually have Versions - all other are just temporary states with no meaning..
I totally understand that this is for ultra robust assemblies that never brake - but come on, some responsibility can still be left for user too..
The most annoying cases are where you make change into part which is in sub-sub-sub-sub-sub-assembly (each in separate doc) and wait for change to appear into main assembly on other window - nope, you need to first create versions and update each doc into newest version to apply the change into main assembly.
If I could set links into current version and when finished / reached certain milestone I would create version of main assy and that should automatically create versions for each linked doc and keep 'main' workspace still connected to current versions.
And here is link to IR voting if you would like to have possibility to link into current version..
https://forum.onshape.com/discussion/5464/link-to-current-version-of-document
//rami1
