topic Re: Design Assistant 2023 - Sub-folders not shows and changes made save to top level of project in Inventor Forum

Design Assistant 2023 - Sub-folders not shows and changes made save to top level of project

pa_caffrey — Mon, 04 Apr 2022 08:32:12 GMT

The title is pretty self explanatory, when I open an assembly in design assistant, the sub folders aren't showing so if I copy a part for instance, it won't save in the same place as the original part and will instead save in the top level project folder.

Re: Design Assistant 2023 - Sub-folders not shows and changes made save to top level of project

johnsonshiue — Mon, 04 Apr 2022 22:52:37 GMT

Hi! Are you using the Default project or a custom project?

Many thanks!

Re: Design Assistant 2023 - Sub-folders not shows and changes made save to top level of project

pa_caffrey — Tue, 05 Apr 2022 08:47:39 GMT

Hi I'm using a custom project, and I've selected that project folder (see attached). When I choose an assembly in a sub-folder of this project it doesn't show a sub-folder on any of the files (see attached). So when I try copy any, I also have to fill in the sub-folder info. Where this becomes irritating is when I'm not sure where the original part is filed. I haven't tried this through the vault because I much prefer design assistant.

Re: Design Assistant 2023 - Sub-folders not shows and changes made save to top level of project

ssadler3FVF5 — Thu, 21 Apr 2022 08:41:52 GMT

I have exactly the same problem. When I change my project to default the sub folders are showing.

Re: Design Assistant 2023 - Sub-folders not shows and changes made save to top level of project

johnsonshiue — Sat, 30 Apr 2022 00:56:15 GMT

Hi Folks,

I am sorry this does look like yet another bug in 2023.0. I need to work with the project team to understand it better. If there is any meaningful update, I will share with you.

Many thanks!

Re: Design Assistant 2023 - Sub-folders not shows and changes made save to top level of project

johnsonshiue — Tue, 17 May 2022 16:56:24 GMT

Hi! The issue has been reported as INVGEN-61522. The project team is still investigating the issue. Hopefully it will be fixed in the coming 2023.1 update.

Many thanks!