User Tools

Site Tools


replicate_table_map

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
replicate_table_map [2017/07/19 17:59]
dloo [Defining a Table Map with Schema Support]
replicate_table_map [2017/07/20 00:11] (current)
paul
Line 1: Line 1:
 ====== Custom Target Database Schema using Table Maps ====== ====== Custom Target Database Schema using Table Maps ======
  
-<​wrap ​round info>coming soon</​wrap>​+<wrap info>[[updateset_releases|v3.25.0]]</​wrap>​
  
 By default, data replicated from existing tables will automatically create the same schema at the replicated database. In certain situations, the targeted database schema of replication needs to be flexible and customized: By default, data replicated from existing tables will automatically create the same schema at the replicated database. In certain situations, the targeted database schema of replication needs to be flexible and customized:
Line 16: Line 16:
  
 ==== Defining a Table Map with Schema Support ==== ==== Defining a Table Map with Schema Support ====
- 
-<wrap round info>new !</​wrap>​ 
  
 Think of [[snc_table_maps|Outbound Table Maps]] as a way to create an output of formatted XML or JSON payload, kind of like an "​Export Set" in ServiceNow. ​ In a nutshell, you can select a single table or a [[http://​wiki.servicenow.com/​index.php?​title=Database_Views|Database Views]] (joined tables) as your source table in a Table Map and select fields or use scripts to generate the target fields. Think of [[snc_table_maps|Outbound Table Maps]] as a way to create an output of formatted XML or JSON payload, kind of like an "​Export Set" in ServiceNow. ​ In a nutshell, you can select a single table or a [[http://​wiki.servicenow.com/​index.php?​title=Database_Views|Database Views]] (joined tables) as your source table in a Table Map and select fields or use scripts to generate the target fields.
  
-The following example ​shows using the Jira **common_incident** Table Map and set to **Generate Schema**, overriding the **caller_email** output field to 100 character length, and lastly specifying the **number** field as the "​GUID"​.+The following example ​uses the Jira **common_incident** Table Map with **Generate Schema** ​selected, overriding the **caller_email** output field to 100 character length, and lastly specifying the **number** field as the "​GUID"​.
  
-<WRAP round important>​Note that specifying Field Type and Field Length is optional except for designating at least one field as "Sys ID (GUID)"​ required for the target DB table to be created and queried for updates and deletes. ​+<WRAP round important>​Note that specifying Field Type and Field Length is optional except for designating at least one field as "Sys ID (GUID)"​.  This is required for the target DB table to be created and queried for updates and deletes. ​
  The default Field Type is "​string"​ and the default Field Length is "​1000"</​WRAP>​  The default Field Type is "​string"​ and the default Field Length is "​1000"</​WRAP>​
  
replicate_table_map.txt ยท Last modified: 2017/07/20 00:11 by paul