Instantiating Document Templates

[jopal]

I've noticed recently when instantiating document templates, sometimes it saves the files as CATProduct123.CATProduct or CATPart123.CATPart, and not save the file to the instance/part name in the tree. I've also noticed it somemtimes pulls a copy of the document template highest product level and places a copy of it in the design folder which i am working in. We do not have our components catalogued, they are in windows directory structure.

 

[DBezaire]

I have noticed some of my parts having this issue(R20.SP7)

Tools - Options - Infrastructure - Catalog Editor - PartNumber Management.
Check on Modify Part Number when resolve family.

I think the issue might be coming from the Check the uniqueness of the Part Name option. In my case I have it checked on. I am currently evaluating R21.SP6 and will keep an eye on Part Number management.
There might be some deeper issues with document instantiation. I have certain Document templates adding the extension twice CATProduct123.CATProduct.CATProduct and CATPart123.CATPart.CATPart I have have narrowed the field to the Document Template Definition. If I uncheck the Auto modify part numbers with suffix the problem begins.

How are you instantiating documents that are not in a catalogue?


Regards,
Derek


Win XP64
R20SP7/21SP5, 3DVIA Composer 2013, ST R20
Dell T7400 16GB Ram
Quadro FX 4800 - 1.5GB

 

[jopal]

Are documents templates are stored on our network in multiple file folders that we pre-defined, and we add these folders. We use Instantiate from document as opposed to going into catologue browser. I will try the other options and see if it fixes the problem

 

[jopal]

"Modify part number" is checked on. "Check uniqueness" is not.

 

[DBezaire]

There is no Instantiate from Document at the assembly level like in product design. Are you using New From or Insert Existing Document?


Win XP64
R20SP7/21SP5, 3DVIA Composer 2013, ST R20
Dell T7400 16GB Ram
Quadro FX 4800 - 1.5GB

 

[jopal]

We have Product Knowledge Template, under that workbench we use "Instantiate from Document"

See Pic

 

[DBezaire]

Well I do sit here corrected on instantiating methods.

There are some pluses to using a catalogue methodology for documents.
1) single source to find company macros/UDF/components/smart assemblies
2) single source to find customer macros/UDF/components/smart assemblies
3) publish macro/UDF smart assemblies to later use as a Catia Icon.

You could still access the documents with your current directory structure. I have added the DLNAME to the mix. It helped with version control of catalogs and deployment to a different business unit.

Win XP64
R20SP7/21SP5, 3DVIA Composer 2013, ST R20
Dell T7400 16GB Ram
Quadro FX 4800 - 1.5GB

 

[jopal]

I am not very familiar with using or creating catologues. I would have to investigate further as opposed to our current methods to see which is more beneficial in our environment. Our directory structures captures items 1 and 2 you listed. Item 3 sounds interesting for most frequently used components common to most jobs.

What is DLNAME?

 

[DBezaire]

DLNAME is short for Dynamic Link Name. It would be similar to you setting a windows short cut link in My Docs to the base location of your assemblies.

I am not sure of your situation but for the most part DLNAME could be a bit of overkill. I snapped a few images and placed them in the attached doc file. The DLNAME structure helped out with keeping the catalogs in multiple business units as the server paths were different. You could achieve similar results with Windows short cut links to the My Document folder to get the designer to the end location faster.

#3 is a big time saver. Custom menus are added at the assembly level for template instantiating and macros used at the assembly level only. Likewise, UDF and macros for PD (Part Design)/GSD (Generative Shape Design) workbenches.

Regards,
Derek


Win XP64
R20SP7/21SP5, 3DVIA Composer 2013, ST R20
Dell T7400 16GB Ram
Quadro FX 4800 - 1.5GB

 

[rbeson]

Based on this thread, is there a way to automatically update the instantiated parts? For example, if I update my document template, is it possible to automatically update all the instances?

Thanks,
Rob

 

[DBezaire]

You could use Assembly Design - Insert Existing Component. This does not make a new instance (create new UUID)of the part/assembly. This is a similar idea to resolving the catalogs. Obviously if you made a geometry change to your document template that was used as a shared link you would need to open each Assembly that was affected to update.

Regards,
Derek



Win XP64
R20SP7/21SP5, 3DVIA Composer 2013, ST R20
Dell T7400 16GB Ram
Quadro FX 4800 - 1.5GB