This month, we are launching exciting product updates in Lemax. Learn about the details below (available from January 22nd, 2026).
Update DataPersistMode(1) on “PassengerUpdate” API method
What’s new
The PassengerUpdate API has been enhanced to improve how passenger data is updated when using DataPersistMode = 1.
With this upgrade, passenger fields can now be updated in a consistent and predictable way, including country-related fields, while ensuring that empty or missing values do not overwrite existing information. This allows correct updates of passenger data that was previously protected or auto-assigned by the system.
This update is automatically available to you once the release is launched. Please note that the usage of this update could depend on system setups (which modules/products you use) and user roles.
Problem being solved
When using the PassengerUpdate API with DataPersistMode = 1, the system previously saved only fields that were empty or had certain default values.
This resulted in inconsistent behavior and prevented legitimate updates—most notably for country-related fields—even when correct new values were provided.
As a result, integrations could not reliably correct passenger data once initial values were set.
Benefit for the users
- Enables reliable passenger data updates when
DataPersistMode = 1is used - Allows correction of default or auto-assigned country values
- Prevents accidental overwriting of existing data with null or empty inputs
- Provides consistent behavior across all passenger fields
How it works
Updated Save Logic for DataPersistMode = 1
When PassengerUpdate is called with DataPersistMode = 1, the API now behaves like a partial (PATCH-style) update.
Behavior applies ONLY to DataPersistMode = 1:Summary Table (Applies to ALL Fields)
| Existing value | Incoming value | Saved Result | Status |
|---|---|---|---|
| null | “A” | “A” | Updated |
| “A” | “B” | “B” | Updated |
| “A” | null | “A” | Preserved |
| “A” | “” | “A” | Preserved |
This logic applies to all passenger fields.
Country Field Updates with DefaultCountryID (DataPersistMode = 1)
Country-related fields (Country, Citizenship, Passport Issuing Country) now follow the same update rules when DataPersistMode = 1 is used.
Updated behavior:
- If the existing country value equals
DefaultCountryID(defined in Superadmin settings), the field is editable - A non-empty value provided via PassengerUpdate will overwrite the default value
- The previous restriction that blocked overwriting non-empty country values has been removed
Example use case:
- Passenger is created with CountryID set to DefaultCountryID
- PassengerUpdate is called with a different CountryID and
DataPersistMode = 1 - The new CountryID is saved and visible in the back-office
