Use this guide to understand which Salesforce fields Summize can map data from, plus handy workarounds if your desired fields aren’t available
Introduction
When using the Summize Salesforce integration, one of the biggest time savers is the ability to map data from Salesforce directly into your Summize request template forms. This reduces manual data entry, keeps Salesforce as your single source of truth, and speeds up the process of generating requests.
However, we know that some customers run into limitations when trying to map data from more complex Salesforce environments. This guide explains what’s possible today, where the limitations are, and what workarounds exist.
What you can do today
- Master record fields: Any field on the Salesforce record you’re launching Summize from (e.g. an Opportunity) can be mapped into your Summize intake form.
- Child record fields (one level down): You can also map to related child records, such as Opportunity Line Items or Quotes. However, this only works one level deep. (Also, see 'Very large related datasets' in the section below)
- Some Parent record fields (one level up): Limited fields from related parent records (such as the Opportunity’s Account or Owner) can also be mapped.
- Field types: This includes standard fields, custom fields, and formula fields.
In most cases, this covers the core data needed to generate requests quickly.
What isn’t supported
Some scenarios are not currently supported by the integration:
- Children of children: While you can map to child records, you cannot reach further down into children of children. For example, you can map to an Opportunity’s Line Items, but not to records related to those Line Items.
- Parent lookups beyond Account/User: Fields further up the hierarchy (beyond the master record’s immediate parents) are not available.
- Dynamic tables or lists: It’s not possible to pull through multiple child records into a table format (e.g. displaying all Quote Line Items in rows and columns).
- Very large related datasets: Even if a relationship is supported, Salesforce enforces a 100-record query limit. When Summize asks Salesforce for related data, Salesforce will only return up to 100 related items in a single query. So even if the field you want to map technically meets the requirements (e.g. it’s a supported parent/child relationship), if the related record set is very large (say hundreds of line items), Salesforce itself will stop returning results after the first 100. This means some data could be missed.
Why these limitations exist
The Summize Salesforce integration is designed to be simple and reliable, focusing on fields available on the record you’re working from. More complex queries into Salesforce (such as pulling in multiple related child or parent records) aren’t currently supported.
Additionally, Salesforce itself enforces certain technical limits - such as the 100-record query cap - which can prevent very large related datasets from being fully retrieved. This means that if you’d like to use data from other related records, that data needs to be “surfaced” onto the master record first.
Workarounds
Although you can’t map directly from deeper related records, there are reliable ways to bring the data you need into Summize:
- Formula fields: Ideal for pulling through fields from parent records.
- Roll-up summaries or Salesforce Flow: Useful for surfacing key datapoints from child records, such as bringing through a reference number from a related Quote.
- Concatenated strings: If you need multiple values (e.g. several Quote references), you can use Salesforce logic to combine them into a single field, formatted with commas or line breaks.
- Fixed child data: If you only ever need to bring across a small, predictable number of child records, you can use hidden fields on the master record (e.g. “Product Code 1”, “Product Code 2”). Salesforce Flow or Apex can populate these fields.
For larger datasets or repeating sections, manual entry in Summize may still be required.
Key takeaway
Summize can map any field that exists on the master record you’re launching from, including related child records one level down. If you want to use data from elsewhere in Salesforce, you’ll need to bring that data onto the master record first using Salesforce configuration (formula fields, roll-ups, or Flow).
And remember: if your Salesforce object has very large related datasets, Salesforce’s 100-record query limit may prevent some records from being pulled through.
This ensures you still benefit from Salesforce as your single source of truth, while keeping the Summize integration fast and reliable.