Set Default Path for iPart Member Files with CUSTOM Property

[arkelec]

This was a previous idea by @SharkDesign.  It didn't get any support but I think it's a good idea.

The problem with using iPart files with a Custom property is that all of the member files generated are stored in the Workplace root folder.  This can lead to hundreds of files, which I'm sure you can appreciate is a right pain in the nads.

There was a suggestion that setting up a library location & adding a proxy folder would solve the issue but I've tried that & it doesn't work.  Both James & myself have tried to find a current solution to this problem but it doesn't seem to exist.

So please Autodesk, have a look at giving the option to store the multitude of files generated in a single, definable location, or even the same for standard iPart member files (in a sub-folder local to the iPart file location.

Hopefully, this will get some support.

[SharkDesign]

I want to be able to set a default path for custom iParts.

Currently, standard length iPart members are put in a folder where the original iPart is saved.

But for some inexplicable reason, custom length iParts are saved in the project files root directory.

This just clutters up the root directory for no purpose.

For instance if my project file workspace is c:\inventor

and I have an iPart in c:\inventor\folder\ipart.ipt

If I choose a length from a table of set lengths, it creates the parts in the same place as the iPart, for instance: c:\inventor\folder\ipart\Part01-01.ipt

However, if I have a custom parameter in my iPart, when I insert the ipart and type my length, instead of creating the new member in the same place as the ipart, as shown above, it actually puts all the new members in the root of the project file workspace. It doesn't even create a new folder, it just chucks them all in c:\inventor and clutters it up.

I know that you can click the 'browse' button to save the custom iPart members where you want them, but this defaults to the workspace for every new instance of that iPart which is really laborious.

[inv.ideareview]

Thanks for sharing your Idea. We use this forum to guide product development and help users in the best way we can based on voting. We occasionally merge Ideas or archive old ones to keep the forum working properly - it ensures there is room for people to review new Ideas and that the most relevant and meaningful ones can gain votes. We’re archiving this Idea because it's been on the board for well over a year and hasn't received many votes from the community. If you want to raise it again and try to gain more support, you're welcome to do so. We’ve found that pictures and mock-ups can help get concepts across and win more votes from other users. If you have questions or see a connection between this Idea and others, let us know. - Inventor product team (Inv.idea review)

[SharkDesign]

Yeah, they had a massive purge on archiving things whether they were a good idea or not. 

This idea seems obvious because the current system simply doesn't work. 

[bryantsonnier]

Up voting this.  I have a million (slight exaggeration) ipart and each with their own sub-folder.  I dont use the member for things i use the factory and the member gets referenced, so i have to scroll passed a million folders just to get to the file i need.  The library/proxy method would be great but you can't edit library parts or even check that as an option.  The alternative "FlatStructure" registry edit fix would be 10 times worse because each of my iparts has a million members.  This definitely needs fixing.

[Anonymous]

This would save so much daily frustration.

Get it Done!

[arkelec]

How many votes do we need for some action on this?

[SharkDesign]

A million? They're too involved in making the hole command unusable to bother changing anything that might improve the software. 

[rhenstenburg]

I strongly concur that this is a problem that should be addressed.

My root folder is getting clogged and getting worse. 

To make matters worse, the child files from these factories cannot be simply moved in Vault to their correct locations ... even with admin privileges.  I am assuming that the only way to relocate these files which are dumped in the root will be to delete them and recreate them in the correct location.  Tedious.  Then the parent assemblies will all have to be repaired.  More tedium.

This is a huge problem getting bigger every time someone uses these iPart factories.

PLEASE address this Autodesk!!!

[dan_szymanski]

Idea added to backlog for future consideration [27239]. Thanks!

[rhenstenburg]

Thanks for changing the status on this issue.  I believe it is an important one. 

It should be expected that iPart factories, with or without a custom parameter, should act similarly by storing children in a sub-folder.  I don't understand why factories with custom parameters were programmed to dump children to the root folder.  I look forward to this fix.

[arkelec]

Looking good @SharkDesign 

[matt.jamieson]

I really hope this is being worked on. It is insane this hasn't been sorted out yet!

[isaacsEYWUN]

Can you please get this done?  The way it is currently structured makes no sense at all.