topic Re: How does the Default project actually work? in Inventor Forum

How does the Default project actually work?

DATUM88 — Wed, 18 Dec 2019 15:03:04 GMT

My department does not create new project paths for each separate project, instead we keep the Default project active for everything we work on.

Despite this, file relationships are rarely lost, and rarely lead to the wrong location. Most of the part files DO have unique files names, but occasionally hardware or some other minor component is copied into the folder (technically creating the existence of duplicates), yet it rarely prompts the user to choose which duplicate to use.

I'm looking into this because we have created some parameter driven assemblies that we Pack and Go into the whatever the current project folder is. Every time this is done, duplicate file names are created, yet when the assembly is opened from the destination folder it somehow knows to use the files in that location (convenient). Recently an issue has come up where one user in the department is finding that his assemblies are still referencing the original location of the parameter driven parts. To get around this, I've just had him activate the .IPJ file that was created with the Pack and Go so his assembly only references the correct files. However, since this isn't the "normal" work flow in the department, I'm trying to figure out why it's happening and if I can correct it so he can just use the default project as we do for everything else.

I understand that using the Default project is typically a NO NO, as is creating numerous duplicate files names. But that's just the way things are done here, and it seems to work fine for these people.

Re: How does the Default project actually work?

Mark.Lancaster — Wed, 18 Dec 2019 15:50:19 GMT

@DATUM88

May I ask why are you using pack n go internally? This utility is used when you want to send the information outside of your organization. Its not a tool for internal use. Are you using it to copy design?

Re: How does the Default project actually work?

DATUM88 — Wed, 18 Dec 2019 15:57:54 GMT

The Pack and Go is being used to copy the assembly and its parts to another folder.

Re: How does the Default project actually work?

Mark.Lancaster — Wed, 18 Dec 2019 15:59:50 GMT

@DATUM88

Wrong tool and the root cause of your issues. You need to be using iLogic Design Copy or Design Assistant to do this.. Pack n Go is not the correct tool for this.

https://synergiscadblog.com/2014/09/23/copy-files-easily-with-ilogic-design-copy-even-without-ilogic-rules-in-the-design/

Re: How does the Default project actually work?

DATUM88 — Wed, 18 Dec 2019 16:01:35 GMT

Even if we use a different tool, how does this explain where the Default project goes looking for the files?

Re: How does the Default project actually work?

Mark.Lancaster — Wed, 18 Dec 2019 16:04:07 GMT

@DATUM88

Its all based on the default project settings.

Perhaps you may want to review this https://synergiscadblog.com/2014/10/29/why-its-important-to-have-an-organized-structure-for-inventor-and-a-properly-configured-project-file-part-2-of-2/ to understand how any project file works.

Re: How does the Default project actually work?

Frederick_Law — Wed, 18 Dec 2019 17:31:42 GMT

I used single Project file for a long time and I allow duplicated files.

Because that option force IV to use full path for all files.

When files are not where they supposed to be, IV will ask.

Pack and Go is the same as copying the folder and rename it in windows.

All files are looking at same location for reference. Based on Workspace in Project file.

Design Assistant can change the reference to new folder when copy.

I always reuse models/projects by just copy the folders.

You just need to know how to do it properly.

Re: How does the Default project actually work?

DATUM88 — Thu, 19 Dec 2019 18:09:12 GMT

We seem to have resolved the issue. I was comparing my Default project settings to his, and noticed his work space setting was not the same as mine. Mine was set to the entire engineering drive, while his was one folder deeper (in the folder containing all the CAD files, which actually should have worked).

Changing his to point at the entire drive has allowed his files to somehow remember the last location referenced. So when the assembly in question is copied to the new project folder, then is opened, it references only the parts in that specific folder.

I don't understand why directing the Default project to reference the entire drive has fixed it, but at least its working now. It seems like the Default project path is programmed to reference the last location the files had reference to.

Re: How does the Default project actually work?

Frederick_Law — Thu, 19 Dec 2019 18:13:25 GMT

IV use path from the Workspace down.

So everything will start as Workspace\Folder\File.

If your coworker's Workspace is in another folder, IV still look for Workspace\Folder\File.

And of course its not there, its in Workspace\File.