As I wrote in your similar question, you can try to bypass the Teamcenter Connector completely and consume that API from Mendix as a normal external service. But that is only realistic if Teamcenter or your middleware already exposes an endpoint Mendix can call directly. In that setup, you would be building and maintaining the authentication, request/response mapping, and error handling yourself instead of using the connector’s built-in session management. Please revise the documentation as well.
So the practical recommendation would be:
The reason you are only seeing certain object types through the Extension is that the Extension is built on top of the Connector and is a lower-code layer, not a replacement for all Teamcenter access patterns.
If this resolves your issue, please mark it as accepted.
Hi,
No, in Mendix you cannot directly call Teamcenter SOA services without Java actions.
Because of this, Mendix microflows alone cannot replace Java actions for SOA calls.
Use Teamcenter REST APIs (if available):
This allows you to:
Use a middleware layer:
Flow:
Mendix → REST → Middleware → Teamcenter
Then Java actions are mandatory: