save assemblings on different folders without links.

[leggera]

Hello.

I came from catiav5 and went to inventor2017.
I don't understand how with inventor you can save a set on two different folders so you can work individually without problems.
of course together saved in the folder connected to the parts of the folder a.
the axieme of the b folder connected to the parts of the b folder.
someone wrote with pack&go, but I didn't understand how to do it.
do not tell me to use the function seeks because I did not find anything, or I misplaced the search I did not get an acceptable answer.

Thank you.

 

[Tarkus]

In fact you want to work on a copy of a set and its parts.
it takes the pack & go.
to get there:
click on the inventor icon (top left)
pointer on "Save with name" without clicking
in the side window that opens, find the pack & go.
here you can make your copy and decide whether to copy styles, library parts, models etc.

 

[Hybrid]

In fact you want to work on a copy of a set and its parts.
it takes the pack & go.
to get there:
click on the inventor icon (top left)
pointer on "Save with name" without clicking
in the side window that opens, find the pack & go.
here you can make your copy and decide whether to copy styles, library parts, models etc.

"copy on a single path" or "preserve folder hierarchy"?
- "only template file" or "include attached files"?
because if I leave the default spuns, in the pack and go created the parts of the axieme continue to point to the original position!
I want to be able to modify/rename the created parts/under created assemblies!

 

[Hybrid]

In fact you want to work on a copy of a set and its parts.
it takes the pack & go.
to get there:
click on the inventor icon (top left)
pointer on "Save with name" without clicking
in the side window that opens, find the pack & go.
here you can make your copy and decide whether to copy styles, library parts, models etc.

were about to start epochal disasters. . .
1) being used well with solidworks and solid edge do not understand the philosophy inventor
3) there is a single project file for all folders
2) I have a set named pippo.iam with under parts pippo 1.par, pippo 2.par, pippo 3.par and its drawings pippo 1.idw, pippo 2.idw etc... What is the command that clones me the axieme and its under parts without going to affect the original path? There are 60 parts/axioms and relatives on the table...I hope I don't have to put files for files to rename it by hand and give it back the reference!

 

[TECNOMODEL]

I guess you don't use the vault, otherwise the command is "project file copy"

from what I know you can do with both design assistant and pack a & go.

 

[Hybrid]

I guess you don't use the vault, otherwise the command is "project file copy"

from what I know you can do with both design assistant and pack a & go.

with design assistant I have no idea how to do it, while with pack a & go, having a unique project file for all projects, continues to fish somewhere else

 

[leggera]

for me it is a lack of the program cannot save a set in 5 different folders and manage them independently.
They do all the programs.

 

[callaghan]

2) I have a set named pippo.iam with under parts pippo 1.par, pippo 2.par, pippo 3.par and its drawings pippo 1.idw, pippo 2.idw etc... What is the command that clones me the axieme and its under parts without going to affect the original path? There are 60 parts/axioms and relatives on the table...I hope I don't have to put files for files to rename it by hand and give it back the reference!

I usually do this...

cmq you can try to copy all folder with files on another path, with a different project file
I think it's the only way to reuse all files, obviously with the risk of having different parts but with the same name

 

[leggera]

It is good that catia and solidworks are another world, but this should be a basic function.
sin.

is there anything about this?

 

[stefanobruno]

3) there is a single project file for all folders

the problem is all this, in a project file you can only have a file with the pippo name.
if you have more than one and are identical, the prog. takes the first and does not warn you (sometimes I warn you, but I have not yet understood what is the discrimination between behavior and the other and try to avoid deepening).
If they are the same only in the name, you feel that what he found is not the correct one, but let you the burden of finding the right one, if you have 5 scattered around, best wishes.
In any case, I do not understand why to keep 5 equal files in 5 different folders, in one project path, I would already avoid having them in different projects.
This way of doing is "many" dangerous, not that you cannot use it, but it is essential to understand well what you are doing.
different is to clone a set while renouncing the details and under relative assemblies, but I did not understand if this is the final result you want.

 

[TECNOMODEL]

the problem is all this, in a project file you can only have a file with the pippo name.
if you have more than one and are identical, the prog. takes the first and does not warn you (sometimes I warn you, but I have not yet understood what is the discrimination between behavior and the other and try to avoid deepening).
If they are the same only in the name, you feel that what he found is not the correct one, but let you the burden of finding the right one, if you have 5 scattered around, best wishes.
In any case, I do not understand why to keep 5 equal files in 5 different folders, in one project path, I would already avoid having them in different projects.
This way of doing is "many" dangerous, not that you cannot use it, but it is essential to understand well what you are doing.
different is to clone a set while renouncing the details and under relative assemblies, but I did not understand if this is the final result you want.

fully agreed

 

[Tarkus]

We start from an assumption, inventor associates the various files (iam,ipt, idw etc) to other files resident in a folder where the .ipj file resides, that is the file that is created every time you start a new project. does not associate with files, or subfolders, other than those not resident in the folder where the .ipj is located.
if in that folder there are more files with the same name, warn, as already said stefanobruno, of the conflict.
so if you want to have copies of multiple unique files, these must be in a folder (other than the original folder) that must contain a new .ipj file other than that of origin.
So, I remain of mine, and it also seems simple:
create a new project in a new folder, and in it throws a copy of your assemblies and related subaxis and parts files.
you can do this with the pack&go (and here you can choose whether to create the subfolder hierarchy or not) or with the design assistant in case you want to rename some files, maybe to give a new revision number ) or absurdly, you can copy, choosing them, all the files you need.

 

[Tarkus]

apart from the fact that you answered in another discussion, I bring back your answer

I tried but it gives me some mistakes.

I'm also trying with pack&go this way:

- select the axieme also from windows, button dx pack&go and place it in the new folder a.
- I do 3-4 axioms saving them always on the new folder to
The program creates four projects that really don't need anything.
- I open a new empty set and there amounts to the four assemblies.
- save and now it's all bet on the new folder a

It seems to me to work egregiously.

Can there be any counter indications? Let's lose the copy of the files that become double.

Thank you.

, think about this:
folder with pippo.ipj file, folder b with pluto.ipj file, folder c with duckino.ipj file.
you have three folders with different project files.
if you take the b and c folders and move them in to, at the opening of the project you will see all the files of the folder and subfolders b e c.
at the opening of the project b or you will see only the files of its subfolders.
if you use the pack&go, that also copies the .ipj file (at least it seems to me).
but if you have put all the files of the b and c folders in the folder, you will also find in the relative .ipj files
So if you want, I think I understand, more assemblies from different projects, under a single project, you only have to delete the .ipj files too, leave only one (a) in the main folder.
for the rest is fine

 

[Hybrid]

the problem is all this, in a project file you can only have a file with the pippo name.
if you have more than one and are identical, the prog. takes the first and does not warn you (sometimes I warn you, but I have not yet understood what is the discrimination between behavior and the other and try to avoid deepening).
If they are the same only in the name, you feel that what he found is not the correct one, but let you the burden of finding the right one, if you have 5 scattered around, best wishes.
In any case, I do not understand why to keep 5 equal files in 5 different folders, in one project path, I would already avoid having them in different projects.
This way of doing is "many" dangerous, not that you cannot use it, but it is essential to understand well what you are doing.
different is to clone a set while renouncing the details and under relative assemblies, but I did not understand if this is the final result you want.

I only agree that it is "many" dangerous. However:
- drawing a burkert valve dn40. will be inserted in all the assemblies and projects I have. if I have to change it (and of course I have built the assemblies with a minimum of logic-always the same constraints), they automatically change all the assemblies! in solidworks+dbcent, everything was as smooth as oil. in a second clonavo a group from hundreds of parts and I went to change only the components that were to be modified. put on the table and what else they were like.
inventor...no comment

 

[Tarkus]

I only agree that it is "many" dangerous. However:
- drawing a burkert valve dn40. will be inserted in all the assemblies and projects I have. if I have to change it (and of course I have built the assemblies with a minimum of logic-always the same constraints), they automatically change all the assemblies! ........................ ...... ...... ...... ...... ...... ...... ...... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .
inventor...no comment

This is different.
In this case that valve is a component that you use for different projects, so put it, instead create it in a folder" library" which then you will add to all those projects where you intend to mount a valve.
I have two bookcases folders, one where there are all those unregulated trade components (reducers, pneumatic components, valves) that usually unload from the network, another where I keep all the components of corporate standards that I create from me.
These two folders are always added to all my projects under the library item.
Everything works perfectly just as you say....in a moment I change all the assemblies.
Also to change those components that are inside the libraries, I have to enter the project of the libraries themselves.
so there is less risk of accidental changes.

 

[Hybrid]

This is different.
In this case that valve is a component that you use for different projects, so put it, instead create it in a folder" library" which then you will add to all those projects where you intend to mount a valve.
I have two bookcases folders, one where there are all those unregulated trade components (reducers, pneumatic components, valves) that usually unload from the network, another where I keep all the components of corporate standards that I create from me.
These two folders are always added to all my projects under the library item.
Everything works perfectly just as you say....in a moment I change all the assemblies.
Also to change those components that are inside the libraries, I have to enter the project of the libraries themselves.
so there is less risk of accidental changes.

It's not a fold! great

 

[stefanobruno]

inventor...no comment

I'd say it's just a matter of habit.
I with inventor do not make any effort to realize the same things, and do not use the vault, which would further simplify things.
we started with the description of a need and we arrived at another thing, with procedure very well described by tarkus.