As a CRM Consultant, I often get requests from clients to auto-populate data whenever the expected value is known. There may be several key fields from the parent record that need to be displayed on the child record, but they don’t want the end user to have to re-key the same data.
No problem - just create a 1:N Relationship and then add a mapping for each of the fields you want displayed on the child record. Easy enough, right? Right, except that the client’s request often comes with an assumption. Clients often assume that the mapped data is dynamically updated. Not so. The data is only pushed down to the child record when the child record is first created, but it does not display any updates that may be made to the parent record in the future.[More]