Introduction
This article describes how to map BOMLine references in the Mendix Teamcenter Extension when certain properties are not available through the standard extension UI. It provides a workaround for accessing properties like bl_predecessor_lines that are visible in Teamcenter but not selectable in the Teamcenter Extension property mapping interface.
Environment
- Studio Pro all versions
- Teamcenter Extension v4.2.0
Cause
The Teamcenter Extension currently has limitations in its capabilities for BOMLine objects. While it supports retrieving properties, relations, and references for ItemRevisions, it only supports retrieving properties for BOMLines. Relations and references (such as "bl_predecessor_lines") are not directly exposed in the extension's mapping interface.
The Teamcenter Extension has different levels of support for different object types:
| Object Type | Properties | Relations | References |
|---|---|---|---|
| ItemRevision | Fully supported in UI | Fully supported in UI | Fully supported in UI |
| BOMLine | Fully supported in UI | Not supported | Manual workaround needed |
Solution/Workaround
While the Teamcenter Extension UI does not support automatic configuration of BOMLine references, you can manually add associations to your domain model to enable this functionality. The Teamcenter Connector uses name-based mapping and will automatically populate associations that match Teamcenter reference names.
- Create the integration using the Teamcenter Extension
- Use the Teamcenter Extension to create the microflows and domain model for your get structure use case
- Configure the basic BOMLine property mappings as needed
- Locate the BOMLine entity in your domain model
- In the Teamcenter Extension, go to the History tab
- Double-click on the BOMLine object to open its domain model
- Create a new association with the exact Teamcenter reference name
- For predecessor lines: Create a new self-association (*-*) for BOMLine
- Name it exactly as it appears in Teamcenter:
bl_predecessor_lines - The exact naming is critical - the Teamcenter Connector uses name-matching to map data
- Test the integration
- Run your integration to retrieve BOMLine objects
- Verify that you can now retrieve predecessor BOMLines over the association
- The Teamcenter Connector will recognize the association by name and populate it with related BOMLine objects from Teamcenter
Note on other object types: The current use case describes using a reference where the referenced object is also a BOMLine. Hence, we are creating a self‑reference — for predecessor lines create a BOMLine self‑association (-) named exactly bl_predecessor_lines. If the Teamcenter reference points to a different object type (for example an ItemRevision), create an additional domain entity that specializes ItemRevision and create the association between BOMLine and that new entity (named exactly as the Teamcenter reference), or create the association directly to an existing ItemRevision entity. The Teamcenter Connector uses name‑based mapping and will populate any association whose name matches the Teamcenter reference.
Internal information related
265523
C07V9JC0NCE/p1763705481057979
Additional information
Mendix documentation:
0 Comments