What are the common and good design patterns that users can design their own mappings?

For example, a user can define one field can map to another field.

Custom.name -> Account.name

Custom.address -> User.street_address

Where can I put/store this information in a user-friendly way for a user who doesn't know APEX too much?

With these features, I can remove the hard coded mapping part from the APEX backend code.


  • A system administrator, or any arbitrary user?
    – sfdcfox
    Aug 7, 2017 at 21:42

1 Answer 1


You can use a Custom Metadata Type, which allows System Administrators to choose fields directly as lookup values, and you can access these in Apex Code, package them in packages, and migrate them via Change Sets. All of the information you'll need is the linked documentation, or you can view this directly in Help under "Custom Metadata Types."

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .