API Update or Merge - REPLACE mergeMode General Question
API Update or Merge - REPLACE mergeMode General Question
We are using the Update or Merge list API method to update lists. We use a merge spec with a mergMode of REPLACE. We are wondering a couple of things.
1. Based on that it is called REPLACE, it sounds as though the entire list is cleared and then repopulated. However it also says in the documentation 'Any records in the list that are not in the uploaded records are deleted.' This makes me wonder if records that are present in both the upload file and the list remain while the others are added or delete. Can you clarify how the RPELACE works?
2. If the answer to the first question is that the entire list is cleared and then repopulated. Is the list locked during this process so that someone would be unable to use the list while it is empty or only partially populated?
Thanks for your help.
REPLY #1
Thanks for your questions, I'm sorry for the delay getting you an answer!
For you first question:
The name REPLACE is more about the end results than the process, here's the behavior you will see:
a. Any record in the target list that is identical in the uploaded list is not modified.
b. Any record who's in the target list (based on the MergeKeyHeading, typically email), but has different values in the uploaded list in will be updated to the new record values in the uploaded list.
c. Any record in the target list that is not in the uploaded list (based on the MergeKeyHeading, typically email), will be deleted
d. Any record in the uploaded list, but not in the target list (based on the MergeKeyHeading, typically email), will be added.
Does that help clarify?
For your second question, because the entire list is not deleted, it is not locked during the upload.
I hope this helps! If you need more clarification, let me know here or contact Act-On Support to open a ticket.
Thanks!
Justin Philbrook
Act-On Software
Senior Solutions Engineer | API Specialist
REPLY #2
That does answer my questions.Thanks for your help.
Comments
0 comments
Please sign in to leave a comment.