0

Hi Team,I am integrating Teamcenter with Mendix using a SOAP Web Service (WSDL).Current approach:Imported the Teamcenter WSDL into Mendix.Created a microflow to call the Teamcenter operation (getVariantInformation).Imported the XML response using the generated import mapping.Retrieved the VariantOption list from the response.Iterated through VariantOptions and AllowedValues.Created Mendix entities (VariantOption and VariantOptionValue) and committed the records.My microflow currently looks like:Call Web Service → Import XML → Retrieve VariantOption List → Loop VariantOption → Create VariantOption → Loop AllowedValues → Create VariantOptionValue → CommitI am stuck on the implementation and would like guidance on the following:Is this the correct architecture for Teamcenter-to-Mendix integration using SOAP/WSDL?Should I map the XML response directly into my domain model entities instead of creating objects manually in microflows?What is the recommended way to store Teamcenter response data in Mendix?How should I design the domain model for VariantOption and VariantOptionValue?Once the data is stored in Mendix entities, what is the correct way to display it on a Mendix page?Should I use a Data Grid, List View, or Data Grid 2 to display the imported Teamcenter data?Are there any best practices regarding commits inside loops and performance optimization?My goal is:Fetch Variant data from Teamcenter.Store the data in Mendix entities.Display the data on a Mendix UI page.I have attached my microflow screenshot for reference.Any suggestions, examples, or sample implementations would be greatly appreciated.Thank you.

asked 2026-06-12

1 answers