How duplicate values are handled when using Update existing in a web request

[SigurdEileras]

Hi

I have a question about how duplicate values are handled when using the Update existing feature in the Web Request action node.

Using the example from the documentation, I have two questions:

1. If you have duplicate customer numbers in Companies (temp) in Appfarm, are all objects with the matching customer number updated? When testing, it seems that only the first matching object is updated. Is that correct?

2. If you have duplicate customer numbers in the response, will the matching object in the Appfarm data source be updated for every match, with the last match being the final state once the web request is completed?

(And yes, I know having duplicate values on the property you match on isn’t ideal — but real-life data rarely is ideal )

Thanks,
Sigurd

[kristian]

Hi!

Regarding question 1)
I can verify that only the first occurence is updated, if multiple occurences is matching the Mapping property.

Test case: Having 2 companies with OrgNo 919697199 in my Company data source, and doing a Brreg search on “Appfarm” with OrgNo as mapping property - only the first existing entry is updated.

The blue dot info on the “Mapping property” already reflects this behaviour, but could be update / be a bit more info here.

Regarding question 2)
Yes, if you have 1 company with orgno 919697199 existing alread, and you receive 2 entries in the response with that same orgno - the last one of these will be mapped to the existing. The first one is discarded.

[SigurdEileras]

Thank you for clarifying!