Knowledge Hub

Advice and answers from the Restaurantology Team

Custom Salesforce Account enrichment mappings empower users to seamlessly integrate Restaurantology’s market intelligence into their Salesforce CRM. By creating custom mappings, administrators can automate the enrichment of new Accounts and updates to existing records, enhancing data accuracy and usability.

Creating custom enrichment mappings

Administrators can create custom mappings for Concepts and Companies within the Data Enrichment Settings of the Restaurantology App’s Setup & Settings component. They can also create custom mappings for unit-level imports, which is discussed in a separate Knowledge Hub article.

Each custom enrichment rule is made up for six (6) key components:

  1. Account field: The destination field you wish to update with enriched Restaurantology data. Note that there may be limitations to updating certain field or field types, such as shadow fields (those with exact-match API names) and formula fields.
  2. Value/field reference: Choose value if you intend to insert a specific value into the Account field, or choose field reference if you’d like to enrich data available on the latest RestaurantologyLog record. Selecting field reference will result in an additional picklist with the fields available in the managed package, such as Service Type, Restaurantology Target TAM (verified unit count), Tech Insights, and more.
  3. Mapping mode: Here admins will specify the mapping mode to determine how data is matched between fields:
    • No mapping, simple assignment
    • Exact match
    • Contains-mode match
    • Starts-with-mode match
    • Does-not-contain-mode match
  4. Cast as: Select the data type to cast the mapped value as, including String, Integer, Double, or Boolean.
  5. Update option: Choose the update option to determine the behavior when updating existing records. Options include Complete if Missing and Overwrite.


Examples of Custom Rules:

#1, using Field Value → Create a standard Account Record Owner for newly created accounts by providing the ID of the desired user.

#2, using Field Reference → Map technographic information from the latest RestaurantologyLog where the data contains “Toast (POS)” and cast it as a picklist value to an existing custom POS Type field.

Example of a custom data enrichment mapping of POS detections to a POS Type picklist field with contains-mode matching as a String, completed only if data is missing.

Testing mappings for collisions and errors

Account record enrichment may trigger field validation rules or workflow automation, sometimes resulting in errors. The Permissions and Shared Settings area in Data Enrichment Settings allows administrators to test active enrichment rules and address any errors before subsequent updates are applied. This proactive approach ensures smooth data enrichment processes and enhances overall data quality within Salesforce.

Using the “Test your settings” functionality to catch errors resulting from enrichment attempts on Accounts with field validation or workflow automation.