Hi Ashok mukka
The reason you cannot see the typed reference (SFD0QualificationFor) in Create Item is because Teamcenter only exposes properties that exist in the CreateDescriptor of that ItemRevision type. If a property is not part of the CreateDescriptor, the Mendix Teamcenter Extension will not show it in the Create mapping.
Use the Teamcenter Extension → Create Item with Item Revision.
Do not map or pass fnd0Maturity.
SFD0QualificationFor)Because it is not part of the CreateDescriptor, you must update it after the item revision exists:
Microflow pattern:
UpdatedPropertiesInputValuesInput:SFD0QualificationFor
I hope it helps!
This behavior is expected when using the Teamcenter Extension in Mendix.
The Create Item activity does not support setting typed reference properties (such as SiteQual / SFD0QualificationFor) during item creation. Only standard properties exposed by the Teamcenter create input are available in the mapping.
Typed references in Teamcenter are technically relations, not creation attributes. Therefore, they will not appear in the Create Item mapping even though they are visible in Search Workspace Object or Relate Workspace Object activities.
The recommended and working approach is:
SemiconductorQualification and its revision.SiteQual object.SFD0QualificationForThis mirrors how Teamcenter internally handles typed references.
fnd0Maturity ErrorThe error:
An invalid object instance tag is being used in conjunction with property fnd0Maturity
occurs because the required relationship context is missing during object initialization.
Although fnd0Maturity is auto-assigned in Teamcenter UI, the backend validation expects the business object to be correctly related before lifecycle properties are resolved.
Once the typed reference relation is created after item creation, this error is resolved.
This method works reliably in production environments.