Addition To Mass Update - Field Data Mapping

Who would benefit?

What impact would it make?

How should it work?

It would be very useful to have as part of the mass update functionality the ability to populate a field based on data available from one or more existing fields. This could also pull data from a parent entity to populate data into the new child entity field or to aggregate data into a parent entity, some requirements would need to be defined and met to handle this type of thing.

Why is it needed?

This could be used for:

• Moving a field from one entity to another

• Data type changes to entity fields

• Constructed field data (Ex: create data on items based on pattern)

This would be to support model changes, assuming that once data is copied or set up properly the original fields would be removed or cleaned. Multiple purposes exist for this need.