TCConnector 2606.0.1 – Some associations missing from generated domain model

0
I'm using TCConnector 2606.0.1 with StudioPro 11.12.5 to generate entities and associations through object mappings.I've noticed that some relationships defined in the object mapping don't appear as associations in the generated Mendix domain model, even though the related entities are created successfully.For example, in a Get Properties integration, I have the following mappings:ItemRevision → Item (items_tag)ItemRevision → ReleaseStatus (release_status_list)ItemRevision → TC_Project (project_list)After generation, the associations for items_tag and project_list appear in the domain model, but the release_status_list association does not.I believe I've encountered similar behaviour with other entities and relationships.Is this expected behaviour??Does the Connector handle certain associations differently, particularly inherited Teamcenter properties? If an association is defined in the object mapping but isn't visible in the domain model, how should it be accessed in a microflow?I've attached screenshots showing the mapping and the generated domain model.
asked
1 answers
1

Hi Tomasz,

The association isn’t missing. It comes from the TcConnector module.

What’s happening

Your generated entities are specializations of TcConnector entities. The blue labels (TcConnector.ItemRevision, TcConnector.ReleaseStatus, …) show their generalizations. The TcConnector domain model (Marketplace modules → TcConnector → Domain model) already contains the standard

Teamcenter reference associations, including:

  • release_status_list: WorkspaceObject ↔ ReleaseStatus
  • items_tag: ItemRevision ↔ Item
  • project_list: WorkspaceObject ↔ TC_Project

In Mendix, a specialization inherits all associations of its generalization. Your ItemRevision → TcConnector.ItemRevision → TcConnector.WorkspaceObject, so it already has TcConnector.release_status_list. The generator reused that existing association instead of creating a duplicate.

The domain model editor only draws associations that belong to the current module. release_status_list belongs to TcConnector, so it’s drawn there, not in your module.

For items_tag and project_list the generator created its own associations in your module. The most likely reason is that the base association’s multiplicity doesn’t match your mapping. For example, the base items_tag is one-to-one while your mapping is *..1; the __1 suffix only avoids the name clash. You can compare the multiplicity of each association line in the TcConnector domain model with your mapping.

How to use it in a microflow

  • Retrieve → By association from $ItemRevision and select TcConnector.release_status_list. It appears in the list even though it isn’t drawn in your domain model.
  • Or use XPath on ReleaseStatus: [TcConnector.release_status_list = $ItemRevision]
  • The result is typed as TcConnector.ReleaseStatus. If you need attributes that exist only on your specialized ReleaseStatus, use an inheritance split and a cast.

Kindly accept the answer if it resolves your query.

answered