Skip to main content
3-Newcomer
September 15, 2026
Question

Standard Attributes mapping with Database Column

I am using Windchill PDMLink Release 12.0 and Datecode with CPS 12.0.2.4 Hello, i am working in modelization of types and attributes in Windchill objects. I want to modelize the creation of new attributes using Local/Standard Attributes. Our implementation process is : - Create a Softtype as a subtype of standard type - Run AddColumn utility - Create Local/Standard Attributes through Type And Attribute Manager Once the development done, we put in code configuration : exported types (XML format), *TypeInfo.java, *TypeInfo.classInfo.ser, SQL File (Alter Table add column). When the Standard/Local attribute is created, the available column is allocated, but the issue is that when we deploy in differents environments, it seems to have a gap in the mapping between the Business attribute and the column in DataBase. For Example : - Env 1 : attr1 mapped to PTC_STR_1TYPEINFO and attr2 mapped to PTC_STR_2TYPEINFO - Env 2 : attr1 mapped to PTC_STR_2TYPEINFO and attr2 mapped to PTC_STR_1TYPEINFO Is it possible to keep consistency in the mapping between the business attribute and the column in DataBase ? If Yes, how to do it ?

2 replies

20-Turquoise
September 15, 2026

The AddColumns tool will do this. At least for the initial “upgrade”. Not sure how it would work for columns added after it was initially ran. Would have to test it on a test server.

https://support.ptc.com/help/windchill/r13.1.2.0/en/Windchill_Help_Center/WCUpgradeGuide/WCUpgrade_AddingColumnsToTypes.html#

Translate
HelesicPetr
22-Sapphire II
October 15, 2026

Hi ​@BS_14618438 

The easiest way is to create the mapping one attribute by one. 

First add the first attribute and use AddColumn utility

then repeated it for second attribute.

This way you can keep the correct attribute sequence. 

 

Also there can be better way  but I do not know it 

PetrH

Translate