You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


Once you know all about ServiceNow Outbound and Inbound Table Maps, use this page for instructions on how to create and configure table maps to fit your ServiceNow needs. 

Add a table map to your ServiceNow dynamic share/bulk share

ServiceNow table maps are typically used in Perspectium Service Gateway integrations to handle the mapping of fields in certain ServiceNow tables as data is shared out of your instance. You can include a table map as part of your ServiceNow dynamic share or bulk share to help with field mappings and data transformation.

Notes:

  • When using a table map with a dynamic share, the dynamic share will trigger based on trigger conditions (i.e. create, update or filter conditions). So this may result in a dynamic share being triggered when a particular field is updated that is not in the table map. As a result, the table mapped record shared out may not have any updated content since all the fields mapped have not changed. To avoid this scenario, use the Share or ignore on specified field updates option.
  • If a table map is set, records with an attachment or message size greater than 5 MB will not be shared out due to ServiceNow platform limitations with how large one particular record can be.

Prerequisites:

Instructions:

  1. In your sharing ServiceNow instance, go to Perspectium > Perspectium Core > Shares > Dynamic Share or Perspectium > Perspectium Core > Shares > Bulk Share.

  2. Click View Dynamic Shares or View Bulk Shares.

  3. From the available shares, click on the one that you want to add a table map for.

  4. In the Data Enrichment tab, click the search icon next to Table map.

  5. From the resulting list, select the table map you want to add. 

  6. Click Update (top right). 

Customize your target database schema using table maps

By default, data replicated from existing tables will automatically create the same schema at the replicated database. The targeted database schema of replication needs to be flexible and customized in certain situations, such as: 

  • An existing schema that the replicated data need to fit in
  • A need to rename the field names or transform the field values using script at the source
  • The resulting field types need to be modified to a specific type or field length

Customizing your target database schema is done by using table maps in your dynamic share or bulk share.