--- schema_version: "1" id: 444800e57f5ca7338c0251627287478a302e5407abb6aa01ae9136d6bc13eca6 title: Join Objects in a Batch Data Transform collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_batch_transform_join.md canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_batch_transform_join.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: a054fe60d26ee6aeeed99b4184764e8bf8aaf9d15e8138849ee360db240ce257 description: On the batch data transform canvas, use a node to create a join between data objects. To make sure that data from multiple data objects is combined accurately and not duplicated, always add a key qualifier field to create a fully qualified key (FQK) in a join. To ensure that null values in a key qualifier field are matched correctly, use a null-safe join by replacing null values with null strings or empty strings. products: - Data 360 release: "264" --- # Join Objects in a Batch Data Transform On the batch data transform canvas, use a node to create a join between data objects. To make sure that data from multiple data objects is combined accurately and not duplicated, always add a key qualifier field to create a fully qualified key (FQK) in a join. To ensure that null values in a key qualifier field are matched correctly, use a null-safe join by replacing null values with null strings or empty strings. All data lake object (DLO) fields used in the data transform table join must have an associated key qualifier. See [Data Interpretation with Fully Qualified Keys](https://help.salesforce.com/s/articleView?id=data.c360_a_data_inter_fqk.htm&type=5&language=en_US) and [Configure a Key Qualifier Field](https://help.salesforce.com/s/articleView?id=data.c360_a_add_or_view_key_qualifier.htm&type=5&language=en_US). Data 360 automatically adds key qualifiers to data model object (DMO) fields. 1. Between two input data sources or at the end of the batch data transform, click **Add Node** ![Add Node button](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/resources-global/analytics/images/bi_button_add_node.png). To show the Add Node button between two input data source objects, hover the cursor on the connecting line. To join an input source to itself, drag the Add Node button to it and select **Join**. 2. Select **Join**. ![The Add Node modal showing the Join node.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/resources-global/analytics/images/bi_integrate_recipe_node_join.png) 3. Select the data to join, choose which fields to include and click **Next**. Currency fields on each side of a join must match. If no currency is selected, the left side of the join's currency is used. For right outer join's, the right side of currency is used. 4. Choose the join type. The batch data transform adds suggested join keys from both sets of input data. To improve results, use up to five keys to match records. For example, when you’re adding contact information to lead data, using only names as a match can result in duplicate matches if different leads have the same name. Instead, use two keys—one to match on name and one for company—to ensure that you’re matching the correct data. For better performance, use a primary key column as one of the keys in your join condition. 5. To create FQKs and ensure that the table join works correctly, under Join Keys, click the plus sign (+) and add key qualifier fields. 6. Apply your changes. 7. On the canvas, in a key qualifier field column on one side of the join, replace all null values with string values. You can’t compare null values with each other. If a null value is present, the table join doesn’t work correctly. 1. Click **Add Node** and select **Transform**. 2. Under Columns, select a key qualifier field. 3. In the Transform toolbar, click the Replace icon. 4. Select **Search for null** (1), and in the Replace text box, enter \--NULL-- (2). Alternatively, enter an empty string (" ") or a value that doesn’t conflict with the value of an existing key qualifier field when compared to the other side of the join. 5. Apply your changes. 6. Repeat these steps for the other side of the join. 7. Preview your changes, and on both sides of the join, make sure that no null values appear in the key qualifier field column. 8. To prevent API name conflicts between fields in the left and right data sources, enter a prefix for fields coming from the data source on the right. The join node prepends the API name prefix of all fields on the right. For example, if you specify Case as the prefix, all field API names on the right begin with “Case.” 9. On the Columns tab in the right panel, select the columns to include in the batch data transform. The Source column shows the object that each column comes from. 10. To preview column data, click **Preview**. To hide columns while in Preview, click the Hide button (![The Hide button.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/data_cloud/images/hideIcon.png)). Hidden columns are still included in the data transform. To show columns, click the Show button (![The Show button.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/resources-global/analytics/images/bi_button_show.png)). Preview can display up to 100 columns. 11. Apply your changes, and save the batch data transform. #### See Also - [_Salesforce Help_: Lookup](https://help.salesforce.com/s/articleView?id=data.c360_a_batch_transform_join_lookup.htm&release=264.0.0&type=5 "A lookup returns all rows from the left input data source object and only matching rows from the right object, the lookup source. To ensure that the grain of the results doesn’t change, the lookup output data includes one row for each row in the left object.")