Building a M/Reduce to create records that are chi...
# suitescript
n
Building a M/Reduce to create records that are children to another custom record. It was suggested to me, that updating the parent by using a UE on the child would be a good approach. (that is to say on create of the child, update various values on the parent using the UE on the child)) However, it occurred to me that doing this could cause "record has been changed" issues if the map/reduce creates the child record before the UE has completed for the previous record. Or am I worrying about nothing?