
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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.
When configuring a Join transformation in the Transform element to combine two collections (for example, Orders and Accounts) using fields such as Id -> AccountId as join keys, users may encounter the following errors if the field mapping is not properly completed:
This article answers the question: why does selecting the Id field, or any other field, as a Join Key in the Flow Builder Transform element cause a validation error, and how do you fix it? The Transform element in Flow Builder supports joining two collections using an Inner Join. It requires three mandatory steps to be completed:
The validation errors above appear when step 2 (selecting join fields) or step 3 (mapping fields) is skipped or left incomplete — the error isn't specific to the Id field itself, but to leaving the join configuration incomplete after choosing a join key.
For detailed configuration steps, refer to Join Collections in a Flow.
005385250