Announcements
Welcome to the Upchain Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

As saved filter should download CAD exactly as saved by user even if the child items changed status from development to Released

As saved filter should download CAD exactly as saved by user even if the child items changed status from development to Released

As saved filter in SolidWorks plugin does not always download as saved CAD.

 

CASE: Child item (B) have development versions 1,2,3,4 & released version 5.

Assembly item (A) is in development and have versions 1,2,3,4,5 created. 

 

Assembly A1 was saved with Child B1, A2 was saved with B2 and so on. 

As long as Child B is not released the as saved filter downloads correct as saved version of child. Once Child B is released as saved filter downloads only the Child B5 released version when user tries to download Assembly A1 as saved CAD.

 

This is wrong and need to be fixed. As saved means as saved and it should not behave differently when child items status is changed.

 

Note that this should be same across Upchain application (SolidWorks plugin, Webapp & Generic plugin) 

2 Comments
dbeam2AYJA
Observer

I was the initial reporter of this issue internally. This is a bug, despite insistence on the help page that it is not:

 

Note: If you release a child item and subsequently download the parent item using the As Saved filter, it downloads the released version of the child, regardless of whether the parent was saved with an older CAD file version. This is because the CAD plugin will not download a Promoted item version unless you directly download a specific version.

 

Downloading "As saved" should mean downloading all of the exact file versions present in the item when it was saved in - any other behaviour is objectively incorrect according to the name of the filter. If it's not downloading those exact file versions, it's not downloading the file as it was saved - it's just downloading a mess of the specific assembly version, and whatever the latest released child versions are, which is useless. Downloading the specific versions of individual items is not a workaround, either. Besides the obvious fact that this is an unreasonable amount of effort to download each individual file, I'm not aware of any list that shows which child item versions were present in a given parent item version, so I have no way of knowing which promoted version I should even download to get an accurate representation of how the file was saved.

 

Promoted item versions are generally much too difficult to access in Upchain Cloud - they can contain valuable information on the history of the item, and hiding them from search results, making them inaccessible in the "As saved" filter, etc. are all just adding obstacles to being able to access the information I need.

imckenzieY7CGY
Advocate

I've also recently seen and have been confused by this issue. The "As Saved" option downloaded versions of child items which I knew did not exist when the version I was trying to download was saved, and no one I asked could figure out how to make it work correctly. Good to know this is an outstanding bug and not something I was misunderstanding. 

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea