You will import your spreadsheet into the custom entity and then use a workflow to automatically apply your updates to the correct records.Once the tool is built, you can reuse it to quickly update your data.If the user has over one hundred thousand records to process, this will take anywhere from a few hours to multiple days to complete.The speed of processing a large amount of records will vary drastically depending how many system users you are importing for and how many records they each have.Doing this will prevent deadlocking between the different tasks, which would be a significant problem when using load balance distribution.
When mapping your fields, make sure you’re setting the look-up on your update entity to use that unique field on the record you’re updating.
Before getting into the details, this method works best if: To demonstrate, we’ll create a tool to update the address on accounts from a spreadsheet below containing new address information. Add fields for each column of the spreadsheet with a look-up to the entity you are updating.
In this example, we will call the entity “Account Update” and place fields for Street 1, Street 2, City, State, and Zip, as well as a lookup to the account.
If you are developing an integration or migration package to an entity with access teams, there are a few important things to note, and this blog will explain some tips and strategies for updating access team records through web services and also provides some technical considerations when using access teams.
Table Locking When creating an access team, CRM will put update locks on system user principals and team membership.
Without all the necessary columns, multiple records might be updated in the table, possibly damaging the referential integrity of the table.