Group Data Mapping populates assigns inputfields in destination action for those not defined in source object
Hi,
The Group Data Mapping feature seems to be producing some (I assume unintended?) behavior when applied to objects with optional fields. Consider the following steps of a recipe I've been developing using a custom connector:
Observe in the second screenshot (input to step 5) that simple fields like terms, merchant_memo, logo_url, and even objects like shipping_info with their own properties are being defined with empty values despite not being present in the original object (output of step 4). This does not strike me as intended behavior.
Arc Anium
Group Data Mapping populates assigns inputfields in destination action for those not defined in source object
Hi,
The Group Data Mapping feature seems to be producing some (I assume unintended?) behavior when applied to objects with optional fields. Consider the following steps of a recipe I've been developing using a custom connector:
Observe in the second screenshot (input to step 5) that simple fields like terms, merchant_memo, logo_url, and even objects like shipping_info with their own properties are being defined with empty values despite not being present in the original object (output of step 4). This does not strike me as intended behavior.
Thank you for any help.