Data Integration. Lookup Mapping

Data Integration. Lookup Mapping


Learn about Lookup mapping for Import and Synchronization tools in Skyvia. Check the use case examples, settings details, and the ways to use Lookup mapping effectively while configuring data integrations.

More information at: https://skyvia.com/
Closed Caption:

hello and welcome to Sky via daa
integration tutorials today's topic is
lookup mapping lookup is data
transformation feature that helps to
retrieve data based on specific
conditions in Sky via the lookup feature
is available as a mapping type in import
and synchronization Integrations and as
a separate component in data flow
integration learn more about the data
flow lookup component in a separate
video lookup fetches values for mapping
in any available Source or Target
objects based on specific conditions
there are several cases when lookup
mapping is the most helpful when there
is no value for mapping in the source
object to define specific records for
update delete and upsert operations and
for loading related data when the parent
object records already exist in
Target lookup mapping works the
following way Sky queries a lookup
object for every Source record and
checks if the lookup key matches the
specified condition if skyva finds a
matching record it Maps the needed field
value to the Target Field SkyV supports
two types of lookup mapping source and
Target lookup Source lookup retrieves a
value from a record in the source object
while Target lookup retrieves a value
from a record in the Target
object to enable lookup mapping select
Target or Source lookup on the mapping
definition tab in your integration and
assign values to lookup
settings lookup object is a source or
Target object where the search is
performed result column is a field in
the lookup object that contains the
desired value lookup key column is a
field in the lookup object based on
which the needed value is retrieved you
can use more than one lookup key or
lookup condition in this case lookup
returns values that match all the
conditions lookup condition is a value
on a source that is compared with the
lookup key there are several conditions
available use column condition to
compare the lookup key field of a source
field use constant condition to compare
all lookup key values with a single
constant value use Source lookup and
Target lookup conditions to retrieve a
value for the lookup key from another
object in the source Target use when
there is no field in the source object
to be compared with the lookup key
lookup can behave differently depending
on the situation for example it may find
nothing or fetch multiple results you
define Its Behavior using lookup options
set them separately for each lookup
mapping in an integration
the used cachee option determines
whether to use a lookout cache when you
select this option skyva queries the
lookup object and loads the result into
a catch during the integration run SkyV
queries this catch for every Source
record and checks if the lookout key
matches the specified condition it helps
to save API calls and increase
performance if the data source contains
millions of Records or API doesn't
support filters for some
objects set null when no matches found
option determines what to do if there is
no match for the lookout condition if
enabled Skyvia assigns n Mount Fields if
disabled the record fails this option is
helpful for the upsert operation when
lookup finds no match skyva will insert
a new record if lookup finds a match Sky
will update the existing record use the
first match when multiple results option
determines what to do when lookup finds
multiple rows matching the specified
Lookout conditions if enabled Skyvia
Maps the first matching value to the
Target Field it dis the record
fails case in sensitive lookup option
enables case insensitive comparison for
string values by default lookup performs
case sensitive
comparisons now let's check several
examples the first example demonstrates
how the simple lookup fetches the
unknown value from another object in
Target we import a list of contacts from
a CSD file into sales force and assign
them to existing Salesforce accounts to
do that we must provide the account ID
Rel to each
contact the column mapping won't help
because the source file doesn't contain
the Salesforce account IDs however it
contains company names that match the
account names and
Salesforce we use lookup to fetch the
absent account ID values by comparing
account names and Salesforce and company
names in the CSD file select Target
lookup for the account ID field account
ID is a foreign key field that
Associates the contact object with the
account object for such Fields Sky sets
the lookup object and result column
values
automatically select the account name
field as the lookup key column choose
column condition select the column in
the source file with which the lookup
will compare the lookup key in our case
it is the company field we will leave
the lookup options in the default State
as a result we built lookup which
retrieves the unknown account ID value
from another object in
Target another example will demonstrate
how to use lookup by a constant
let's insert product prices from the CSD
file into the Salesforce standard price
book The Salesforce price book INE
object requires mapping the price book
ID if you don't know the ID of the
desired price book you can use lookup to
retrig it by its name the lookup will
compare the price book name and
Salesforce with the provided name and
map its ID to all imported
records we select the target lookup for
the pricebook ID field pricebook ID is a
foreign key field associating the price
book andry object with the price book
object for such Fields skyva sets the
lookup object and result colon values
automatically in other cases we select
them
manually select the price book name
field as the lookup key column choose
constant mapping specify the price book
name with which lookup will compare the
lookup
key as a result we built the lookup
which gets the unknown ID of the price
book knowing its name the next example
shows how to get the needed Val value
using multiple Lookout
Keys let's update product prices that
belong to the Salesforce standard price
book we don't know the ID of Records to
update we only have a price book ID and
a list of product names and their
prices we can't identify the records to
update only by product name because the
same product May belong to multiple
Price Books but we can identify them by
Price Book entry ID and price book ID we
use lookup with a composite key to
perform such an update this lookup will
get the price book andry ID values using
two lookup keys with separate
conditions select Target lookup for the
ID
field select price book and tree as the
lookup object and ID as the result
column select the price book and tree
name field as the lookup key column and
choose column mapping specify the column
with which lookup will compare the
lookup key this column is even in this
example below click add lookup key and
select the price book ID field choose
constant mapping and specify the ID of
the needed price book our lookup with
composite key is ready it retrieves
values for mapping using two separate
conditions another example demonstrates
retrieving a value for mapping using a
two-l lookup let's import data from Zoho
CRM to Salesforce we already have Zoho
CRM accounts in Salesforce now we import
Zoho CRM contacts preserving their
relations with accounts and
Salesforce the account ID field in
Salesforce contact object stores the
reference to the parent account we can't
map account ID by column because account
IDs differ in sales force and zo CRM we
can use lookup to compare account names
in Salesforce and zoto and get
Salesforce account IDs for matching
records but there is a problem we can't
use the column or constant conditions
because zo's CRM contacts object doesn't
store the account names it Stores Only
the IDS of the related accounts thus we
can use the source Lookout condition to
compare account ID s between Zoho CRM
contacts and related accounts and
retrieve account names then lookup
compares the fetched names with account
names in Salis force and assigns their
IDs to the account ID field of the
target
contacts on the source definition tab we
select the relation that will be used by
lookup for this example we use contact
account
relation on the mapping definition tab
we select Target lookup for the account
ID field then we select account as the
lookup object and select the ID as
result
column we choose name as the lookup key
column and select the source lookup
mapping to get the corresponding account
names from zo CRM accounts select the
accounts object as the lookup object and
the account name as the result
column select ID as the lookup key
column and choose count in the bottom
drop- down
list our twole lookup is ready it
fetches the value for a lookup key and
then retrieves a value for
mapping the last example shows how to
use look up to import complex structured
data we import a list of products from a
database to
Shopify we store the list of products in
the products table and their variants
are stored in the product variance table
each product variance record refers to
the product it belongs to by the product
ID column in Shopify the products and
variants are stored in a single products
object the variance field has a complex
structure and stores a nested array of
Records to assign napping to the fields
of the nested object we use lookup in
this case Source lookup compares the
lookup key with the field in another
source object and returns all the
matching records in Array format then
you can map the fields of this array to
the nested fields of the target
object such a lookup fetches the array
of records for mapping to the nested
objects of the Target Field it compares
the product IDs and product variants
with product IDs and products it
retrieves all the matching records at
once and transforms the result into the
required data structure
to insulate this case enable the nested
objects checkbox in the import
integration and add an import
task set Doo products as source and
products as
Target on the mapping definition tab
select Source lookup for the variance
field select product variance as the
lookup
object choose product ID as the lookup
key column and select the column mapping
select the ID field to compare with the
lookup key and complete the nested
Fields
mapping as a result we have a new record
in Shopify products with variance etched
from another table with a different
complex
structure as you can see lookup mapping
lets you use different Advanced
integration scenarios we hope this
tutorial help you understand how to use
lookup mapping if you have any questions
leave them in the comments below thank
you for watching and have a nice day

Video Length: 10:59
Uploaded By: Skyvia
Published: 12/4/2024
View Count: 321

Related Software Products
Skyvia Data Integration
Skyvia Data Integration

Published By:
Devart

Description:
Skyvia Data Integration: No-Code ETL, Replication and Sync Between 200+ Cloud Apps and Databases Skyvia Data Integration is Devart's browser-based ETL service that moves data between more than 200 cloud apps, databases, data warehouses and file storages, with import, export, replication and two-way sync wizards and a visual pipeline designer, and no code to write. It's for operations staff, analysts and small data teams who need Salesforce...


Related Videos
How to Automate CSV Data Import in Salesforce with Skyvia
How to Automate CSV Data Import in Salesforce with Skyvia

Video Length: 03:40
Uploaded By: Skyvia (1/16/2024)
View Count: 23,253

Connect SQL Server to Snowflake: Replication & 2-way Sync
Connect SQL Server to Snowflake: Replication & 2-way Sync

Video Length: 10:14
Uploaded By: Skyvia (2/17/2025)
View Count: 5,789

Dynamics 365 Integration with SQL Database or Data Warehouse
Dynamics 365 Integration with SQL Database or Data Warehouse

Video Length: 09:22
Uploaded By: Skyvia (9/20/2024)
View Count: 4,476

Skyvia Data Replication
Skyvia Data Replication

Video Length: 05:05
Uploaded By: Skyvia (10/22/2025)
View Count: 205

Copyright © 2026, Ivertech. All rights reserved.