Fetching LOV Values from Reference Objects in Teamcenter Using Mendix OOTB (TC) Connector

0
Hi Everyone,I need some guidance on a use case in my Mendix project involving Teamcenter LOVs (List of Values).As part of our feasibility analysis of the OOTB Teamcenter Connector, we identified two available SOAs: GetInitialLOVValues and GetNextLOVValues.During testing, we found that these SOAs can successfully fetch LOV values when the LOV is directly attached to an object property. However, when a property retrieves its values from a reference object that has an associated LOV, the existing OOTB SOAs are unable to fetch those values.Has anyone encountered a similar scenario? Is there a way to retrieve LOV values from reference objects into a Mendix application using the OOTB Teamcenter Connector or any alternative approach?Any suggestions or guidance would be greatly appreciated.Thank you!
asked
1 answers
0

Hi Phani,


The OOTB Teamcenter Connector provides GetInitialLOVValues and GetNextLOVValues for retrieving List of Values (LOV) data. However, when the property involves a reference object, you may need to resolve that reference and retrieve its properties explicitly rather than expecting the connector to traverse the reference automatically.


I would suggest the following approach:


1. Resolve the reference object

Retrieve the required property from the original Teamcenter business object and identify the referenced object's UID and type. If the reference is not already resolved to a TcConnector.ModelObject, retrieve the referenced object first.


2. Retrieve the referenced object's properties

Use the connector's property-retrieval functionality, such as GetProperties, to obtain the properties required from the referenced object. Confirm that the referenced object and its property are available in the current Teamcenter session.


3. Retrieve the LOV values

Prepare a TcConnector.GetInitialLOVValuesInputEntity for the relevant business object and property, including the required LOV input and filter configuration. Then call GetInitialLOVValues with the correct Teamcenter configuration.

If the response indicates that moreValuesExist is true, use GetNextLOVValues to retrieve the remaining values.


4. If the OOTB flow still fails

Compare the request generated by your microflow with a working request for a property whose LOV is attached directly to the object. Verify the referenced object's UID, type, property name, LOV association, and filter input.


If the required reference-object scenario is not supported by the existing connector flow, use CallTeamcenterService to implement the required Teamcenter SOA call and map the response to the Mendix domain model. Confirm the appropriate SOA operation and input structure against your Teamcenter version.


Official references:


One clarification: Is the LOV attached to the reference property itself, or is it attached to a property on the referenced object? That distinction determines whether you need to retrieve the LOV for the original object's property or first resolve the referenced object and retrieve its LOV separately.


Hope this helps! If you find this answer helpful, please mark it as the accepted answer.

answered