Skip to main content
Question

Best practice: External postcode API integration in Universal edit screen

  • January 2, 2026
  • 0 replies
  • 29 views

Hello Thinkwise Community,

I’m working in Universal (version 2025.3) and I want to automatically fill street and city fields based on a postal code and house number using the Company.info API, so that the address information is always up-to-date.

The main challenge is that I cannot call the API while inserting/editing a row in the default screen. Additionally, I want to ensure data integrity: if the API fails or does not return a valid address, the original values in the record should remain unchanged. I’ve seen solutions using an auto-commit approach, but that can leave fields empty if the API doesn’t find a match, which I want to avoid.

Requirements / constraints:

  • Universal environment (2025.3)

  • Call an external postcode/address API to populate street and city

  • Triggered when editing a record

  • On API failure or missing data, revert the record to its original state

Has anyone implemented a similar solution in Universal? Are there best practices for safely calling an external API from a row-edit screen while maintaining the original record if the API call fails?

Thanks in advance for your insights!

Forum|alt.badge.img

This is such a good idea collin