Skip to main content

Most of our data at the Account and Contact level contains "institutional" data; fields that are populated from other sources (such as first name, last name, email, job title, department id, etc).

What is the best practice for governance around these institutional fields? For example, if an Alumni states they want their name changed on mailings, or during an interaction we discover a job title is inaccurate, but that field is populated via an integration from another university database, how can that be handled?

Looking for creative ideas such as formula fields / page layouts, as well as business process answers regarding how requests to modify institutional data fields are documented and governed.

10 risposte
0/9000