In CRM Analytics, a cross join combines unrelated records and includes all rows from
the left (recipe data) and the right. Unlike other joins that use keys to find matches, the
cross join pairs every row from one dataset with every row of another dataset (known as the
Cartesian Product).
Required Editions
Available in Salesforce Classic and Lightning Experience.
Available with CRM Analytics, which is available for an extra cost in
Enterprise, Performance, and Unlimited Editions. Also available in
Developer Edition.
Tip When designing a cross join, use the larger dataset first (left) and then
join the smaller dataset (right). For example, join a:
10,000-row dataset (left) with a 1,000-row dataset (right)
20,000-row dataset (left) with a 500-row dataset (right)
40,000-row dataset (left) with a 250-row dataset (right)
100,000-row dataset (left) with a 100-row dataset (right)
Example
A company sells products at various locations. To assist with stock tracking, use a cross
join to combine the product and store datasets to find all the possible pairs of product
and store.
Consider the following two data streams that feed the recipe’s target dataset. To
illustrate how this join combines unrelated records, row number is included for reference
but isn’t needed in the data.
After performing the cross join, the recipe produces this target dataset.
Limitations for Cross Join
Because a cross join
creates a larger dataset than either of the source datasets, it has some limitations. Keep
these points in mind when designing and testing your cross join.
Only one cross join per recipe
Cross join results maximum of 10 million
Left dataset column maximum of 8 and row maximum of 100,000
Right dataset column maximum of 8 and row maximum of 1,000
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
