Article - CS41608
Alias attributes based on Global attributes shows multiple/duplicated values in Windchill
Modified: 17-Dec-2025
Applies To
- Windchill PDMLink 10.0 to 13.0
- Windchill MPMLink 10.0 to 12.1
Description
- Alias attributes based on Global attributes shows duplicated values
- Alias attributes based on Global attributes shows previous and current values
- Start Date Effectivity attribute which is an Alias attribute shows double values in details page of object
- Alias attribute on Document show multiple values from Part which is associated Describe Link
- e.g. Mapping for Alias attribute on WTDocument where TestingPart is WTPart subtype and AliasAttr2 is internal name of attribute
[email protected]~describes^TestingPart~AliasAttr2
- When an Alias Attribute is created on WTPart with below mapping, if the EBOM/Design/Upstream Part (which has an Equivalent Link with a MBOM/Manufacturing/Downstream Part) is Revised and if the Equivalent Link is updated using Update to Current Upstream Equivalent Object, then the Attribute Value shows all Revisions instead of the Latest one
[email protected]~roleAObject^wt.part.WTPart~revision
- When an alias attribute is created on WTPart to map Extended Data attributes, the WTPart attribute shows the attribute value of all the Extended Data revisions instead of latest
- When an alias attribute is used to map attribute from a parent document to a child document, the child document attribute displays all iteration values instead of the latest one
- Alias attributes inherited from Change Request to Change Notice show duplicated values after Change Request revision, causing ESI failures due to multi-valued behavior, is there any way to enforce single-valued inheritance
- When working with Alias attribute, is it possible to only pull in the value from the latest iteration of the object to which the attribute is mapped
This is a printer-friendly version of Article 41608 and may be out of date. For the latest version click CS41608