cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

We are happy to announce the new Windchill Customization board! Learn more.

How to introduce the positioning assemblies for exist assmblies?

BalazsToth
12-Amethyst

How to introduce the positioning assemblies for exist assmblies?

Hello, 

We want to introduce the extended positioning assemblies method in the company. I configured the Windchill and Creo template and it works fine with brand new data. My question is that how we can apply this new method for existing assemblies. We have used Windchill for several years so we have millions assemlby objects in released state. I don't want to check out or revise any assmblies.

My plan was that:

  1. I created a global string attribute (XPOSASSY_STR) and added to EPDM document type. The default value was empty. 
  2. I created a new Creo assembliy with one part. The .asm did not contain the XPOSASSY_STR parameter. 
  3. I checked in the assembly. The info page contains XPOSASSY_STR empty attribute but the CADWorker generated a normal assembly representation. 
  4. I repeated the test but the new Creo assembly contained the XPOSASSY_STR parameter and I got extended positioning attribute. 

So empty string attribute of object did not work fine if the CAD assembly did not have same attribute. 

On the other hand it is not possible to update existing object with a default value of a newly added attribute in Windchill PDMLink Article - CS237076. 

Do you have idea? Thanks. 

1 ACCEPTED SOLUTION

Accepted Solutions
TomU
23-Emerald IV
(To:BalazsToth)

A couple of comments.

 

1.)  While not officially supported, it is possible to create new attributes for existing objects without revising or altering them.  Fishbowl Solutions has a product that can do this and @d_graham could easily create something as well.  This would allow you to mass-assign the new attribute to the selected assemblies.  Of course this doesn't do any good unless you also republish all of them after the attribute is added.

 

2.)  Instead of using the ibaname stuff in CS130256, I've elected to use a custom filter method as described in the help docs.  This gives much more control over how each item is published.  You could even decide how to handle stuff that is missing your custom attribute if you wanted.  In my case I publish all assemblies as extended positioning assemblies unless they are in one particular context or they are Manikin assemblies.  Code snippet is below.

 

TomU_0-1646689241049.png

 

TomU_1-1646689313986.png

 

Edit:  CS291199 may prove useful as well.

View solution in original post

4 REPLIES 4
jlecoz
13-Aquamarine
(To:BalazsToth)

You can manually republish legacy  assemblies as Positionning assemblies.

You can use that mainly on assemblies:

  • Do not need publishing often
  • Are too large to be loaded in to CAD application memory
  • Do not go out-of-date
  • Fail to publish as non-positioning assemblies due to worker resource or other limitations

Procedure - I'm assuming that you need the positioning assembly capability on few assemblies. Doing so won't require setting an attribute value and to iterate the CAD models.

1- Verify that the Windchill user is member of the Administrators group, this enables the Positioning switch in the Create representation UI, you can see the switch in the screenshot below.

Pos Assembly.jpg

 

 

 

 

 

 

 

 

 

2- Create the representations manually using this UI  set them as default to replace the existing one ( that won't be deleted) and check the Publish as Positioning Assembly switch .

 

Alternate method:

Use the Publish and Thumbnail Control UI available from the Utilities menu. From there you can define the list of assemblies that should be published as positioning assemblies. At the next check-in of these assemblies they will be published according to this. If you want to republish without iteration, delete the default representation and republish with a batch job or manually.

 

Note: the publication process is much faster than a "regular" publication.

 

 

TomU
23-Emerald IV
(To:BalazsToth)

A couple of comments.

 

1.)  While not officially supported, it is possible to create new attributes for existing objects without revising or altering them.  Fishbowl Solutions has a product that can do this and @d_graham could easily create something as well.  This would allow you to mass-assign the new attribute to the selected assemblies.  Of course this doesn't do any good unless you also republish all of them after the attribute is added.

 

2.)  Instead of using the ibaname stuff in CS130256, I've elected to use a custom filter method as described in the help docs.  This gives much more control over how each item is published.  You could even decide how to handle stuff that is missing your custom attribute if you wanted.  In my case I publish all assemblies as extended positioning assemblies unless they are in one particular context or they are Manikin assemblies.  Code snippet is below.

 

TomU_0-1646689241049.png

 

TomU_1-1646689313986.png

 

Edit:  CS291199 may prove useful as well.

BalazsToth
12-Amethyst
(To:TomU)

Thank you for your support! I will evaluate the opportunities. 

As @TomU mentioned.  I can write a utility to update existing object with a default value of a newly added attribute.

Sounds like you want to limit the update to only assemblies.

It might not be part of Windchill PDMLink functionality but it's certainly doable.

 

Feel free reach out to me if you like my help.

 

David

Top Tags