In one of our recent implementations, we were working with Marketing List which could be in millions.
So we had the recent request wherein we split the marketing list into groups.
For adding members to a marketing list we have the following request
AddListMembersListRequest
https://msdn.microsoft.com/en-us/library/microsoft.crm.sdk.messages.addlistmemberslistrequest.aspx
which is quite efficient as we can add multiple members in a single request.
However, when it comes to removing a member from marketing, we do not have a corresponding Remove request like RemoveListMembersListRequest.
https://msdn.microsoft.com/en-us/library/microsoft.crm.sdk.messages.removememberlistrequest.aspx
We only have RemoveMemberListRequest, which only removes 1 member at a time, which is highly inefficient when we are taking in consideration large number of records.
Kindly vote up for this idea !!
https://ideas.dynamics.com/ideas/dynamics-crm/ID0002529
More details
Share this:
Static marketing lists are extremely inefficient. When ever a static marketing list changes the platform performs a locking count behind the scenes on each list and updates the list count field on the parent. If you do this in rapid succession using multiple threads you can end up with dead locks and/or the list count being incorrect. This is technically an anti-pattern and shouldn’t have been implemented that way. I don’t know if this had anything to do with the rationale to not implement a bulk delete. They obviously had a bulk add so it would seem having the opposite would have been a given. There’s probably more to the story then we know.
LikeLike
Thanks Smith for sharing your thoughts.
LikeLike