Import Mapping - Empty value consistency

1

Hi,

 

Raised this with Mx who have added it to their feature board and asked to share here in case there's any drive.

 

I noticed there's inconsistency with how import mappings handle empty string values from an API call.

 

• Strings - import "" as ""
• Enums - imports "" as error
• Dates - import "" as empty
• Int - imports "" as error (which is really weird because "123" is imported as 123

It's be great if for all data types, "" just imported as empty to be consistent.

 

For context: we are calling a third party solution that returns empty values as "" in the api calls. So we have to make a parsing microflow, and then add it to all our attributes in the import mapping just to allow this... which is a pain.

 

Thanks,

Adam

asked 2025-11-19

0 answers