#Admin Design Principles0 diskutieren mit

Our upper management would like to hear if other organizations are creating multiple custom fields on the contact object to identify the various ways the organization thinks of the contact and how the contact interacts with the organization (using flows to automatically assign the relevant value based on actual activity), or if you take the approach not to duplicate data that can be easily viewed and filtered in related lists (through Opportunities, Affiliations, Campaigns, etc.) and reported on, only creating custom fields for data that would be difficult to gather into a single report.  For example, which of the following would be your approach? If you take the custom field approach, how do you limit your custom fields? How do you limit which data that is captured elsewhere and is viewable in a related list or easily reported on is also documented in custom fields?

*We are using an Account record type of Internal Group to collocate contacts who serve a function with the organization or belong to some group we defined to think of or work with them in a certain way.  We have dozens of such groups.

#Best Practices #Admin Design Principles

Want to clarify user stories and simplify Salesforce security? Discover the key ingredient at Purposeful Architect.

https://www.purposefularchitect.com/blog/personas-in-user-stories-and-salesforce-security

@The Blog Group @Ladies Be Architects

#Business Analysis #Admin Design Principles #Purposeful Architect