Who would benefit? |
Developers, and by extension users |
What impact would it make? |
Reduce time to market for new development that requires a lot of data updates. Increased customer satisfaction through a better performing system - seeing results faster. |
How should it work? |
Much like the existing UpdateFieldsForEntity, except no EntityId is supplied, rather it's just a list of fields for different entities. |
Why is it needed? |
Time and time again I have had situations where I need to update a single fieldtype across many different entities. Today I have to update them one by one, resulting in a lot of round trips. |
Additional feedback, background or context:
Currently I have a situation where I need to update 1.34 million entities in our Dev environment, all with the same field, and these have to be updated one by one with the current options available. When Dev is done, I have to do the same for Test and Prod, except there's even more entities to update there.
If we were able to batch these updates, it could increase performance for developers and users, and possibly reduce hosting costs for inRiver, as we have to do fewer transports, and inRiver can optimize the database actions.
Is Mass Update unable to achieve this?