UF_CLONE SetDefAssocFileCopy = True What task this function do

[Ehaviv]

Hi

This taken from the nxopen help.

UF_CLONE_set_def_assoc_file_copy (view source)
Overview
This routine sets a logical in the current clone operation indicating whether
associated files should by default be copied (for a clone), exported or
imported in the current operation.


Is this mean that non-masters parts are added automaticaly to the clone operation ?.
or I need to add them manualy.

Thank you in advanced.

 

[Ehaviv]

Add them manually I mean by using
addpart function.

 

[Ehaviv]

?!

 

[Ehaviv]

?!!

 

[jpetach]

If I understand the question correctly this may help.

Here is the description of the associated files capability that the API is automating.
Associated files Link
And here is a description on the import behavior.
Import Associated files Link

In short, if you are importing file 1234.prt and you also have a collocated sub-directory named 1234 all of the files in the 1234 sub-directory associated files candidates providing their file extensions are supported by the importing TC database (dataset types) and will be imported in addition to the part file if the boolean is True.

HTH, Joe

 

[Ehaviv]

Hi Joe and thank you very much.

I know that the content of a sub folder
in the def folder will be impored with
my assembly.

My problem is this

I use a journal to import my assembly to tc
using uf clone addassembly with the boolean
set to true as mentioned above.

But my non_masters (specifications parts)
that the documentation say to he imported
and are in the def directory are not imported.

I successed to import theme but with
a loop of addassembly method and I don't
successeded to import them by addpart method as the documentation say.

Again I'm very very thank you.

 

[Ehaviv]

Actually they should be automatically
without to use addpart method

Because thay are associated files.

Thanks.

 

[Ehaviv]

the spec files that I talk about are
the drawings of the assembly that I import with addassembly method.

 

[jpetach]

Adding the unmanaged assembly to the import operation can infer the component parts for the import operation. You have to add the additional files to the import list that are intended to be non-masters and identify which master they will relate to and what relationship type to use (usually specification).

The command line utility gets that information from an (input) log file which is an optional argument. See
Link
The Drawing would use the 4 field notation @DB/007405/A/spec/Drawing_dataset_name (vs the 2 field Item_ID/Item_revison notation style) and the drawing must refer to an existing item or item that will be created from the same import log file.

HTH Joe

 

[Ehaviv]

Hi Joe and thank you a lot.

You given me a new idea with the log file.

Please tell me if I'lm right.

My journal already in the export stage
export a prepared log file (a correct log file for import) but with a header of the export in other words do I can use the eeport log file as an
import log file without any changes. (As is)

Because the exported section in my journal exports also the non master
part as expected by the documentation (associated part)

(because my import log file not includes th non masters)

Is it possible. ?

Thank you again.

 

[Ehaviv]

Hi

Is for initnaming function I need to set
Something, before calling applydefault
And performeclone

Thank you in advaced