How to Create a Lookup Connection for DataHub

Created by Aleksandra Furundzic, Modified on Tue, 27 Aug at 3:32 PM by Aleksandra Furundzic


Creating a Lookup Connection for DataHub allows you to link and compare data from different sources, much like the "VLOOKUP" function in Excel. 


With a Lookup Connection, you can choose two different data points to compare: one from a source field and another from a DataHub table column header. 


The Lookup Connection will then compare these fields and return all matching items from the DataHub table, automatically populating the corresponding fields in your mapping process.


TABLE OF CONTENTS



 

Step 1: Create a Task and Access the Lookup Connection



1.1 Create a Task in SyncSpider:


Begin by setting up a task in SyncSpider with your desired source integration. For this example, we will use Google Sheets as the source integration and DataHub as the target integration.



1.2 Navigate to the Mapping Page:


After configuring your source and target integrations, proceed to the Mapping page within the task setup.



1.3 Access the Lookup Connection Tool:


On the Mapping page, locate the 'Lookup Connection' option on the right panel and click on it to begin setting up your lookup connection.


SyncSpider mapping setup, highlighting where to create a lookup connection for data integration





Step 2: Set Up the Lookup Connection

2.1 Initiate the Lookup Process:


If this is your first time setting up a lookup connection, click on the “Create a new lookup” button in the Lookup Connections panel.


SyncSpider interface highlighting the 'Create a new lookup' link.



2.2 Search for DataHub:


In the dropdown menu that appears, search for "DataHub" and select it as your lookup connection service.


Dropdown menu in SyncSpider to search and select existing integrations for the lookup connection setup.




2.3 Select Your DataHub Integration:


Next, choose the appropriate DataHub integration from the available options that contain the data you wish to connect.






Step 3: Configure the Lookup Connection

After selecting your DataHub integration, you will configure the lookup connection by specifying the fields you want to compare.



3.1 Select the Source Field:


Once your DataHub integration is selected, two dropdown menus will appear.


In the first dropdown menu, select the source field from your integration (e.g., Google Sheets) that you want to compare with the DataHub table data.


Selecting the source field for the lookup connection in SyncSpider.



3.2 Choose the DataHub Entity:


In the second dropdown menu, choose the DataHub entity where your table is located.


Selecting a DataHub entity from the 'Select Entity' dropdown menSelecting a DataHub entity from the 'Select Entity' dropdown menu in SyncSpider.u in SyncSpider.


3.3 Map the Relevant DataHub Field:


After selecting the DataHub entity, a new dropdown will appear showing the column headers from the selected DataHub table. 


Choose the header that corresponds to the data you want to compare with the source field.  


SyncSpider interface showing the selection of a DataHub entity and the dropdown to choose the relevant lookup field for mapping.





Step 4 : Finalize and View the Lookup Connection


Click the "Done" button to finalize the creation of your lookup connection.


After the connection is created, you will see a new collection available in the source fields, named after the DataHub entity you selected. 


This collection will contain all the relevant fields from the DataHub table, ready for use in your data mapping.



New DataHub entity collection in SyncSpider source fields after creating a lookup connection.



We hope this guide helps you efficiently create and utilize Lookup Connections in SyncSpider. 


If you need further assistance, please contact us via [email protected] or use our chat widget! 



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article