Naming Convention for Subtypes
The subtypeable capability enables subtypes, which are available in Windchill, in the some domains in Windchill REST Services.
When the subtype is enabled in Windchill REST Services, the following naming convention is used:
• The subtype created in Windchill appears in Windchill REST Services with its internal name.
• The domain name which is added as prefix to the internal name is removed.
• The first character of the internal name is capitalized.
For example, consider a parent entity Part in Windchill. Under Part, add a new subtype with the display name demo. The domain name of the subtype is com.ptc. The internal name of the subtype in Windchill is <DomainName.SubtypeName>. In this example, the internal name of the subtype is com.ptc.demo. When the subtype is available in Windchill REST Services, its name is Demo.
• In Windchill REST Services, if subtypes have duplicate internal names, then an error message is returned for the duplicate name. You must change the internal name of the subtype in Windchill to resolve the duplicate name issue in Windchill REST Services.
For example, consider a parent entity Part in Windchill. Under Part, two subtypes are available with the display names demo-assembly and demo_assembly. In Windchill REST Services, you cannot use characters, such as, a hyphen (-) and an underscore (_) in internal names. In this case, the name of both the subtypes in Windchill REST Services is Demoassembly. In Windchill REST Services, the first subtype is added with internal name Demoassembly. For the second subtype, the duplicate name error is returned.
• If you define a subtype with an internal name in the <Entity JSON> file, and create a subtype in Windchill with the same internal name, then Windchill REST Services gives precedence to the subtype created in <Entity JSON> file.