{"id":24437,"date":"2024-02-15T14:53:34","date_gmt":"2024-02-15T22:53:34","guid":{"rendered":"https:\/\/docs.extraview.com\/v25\/book\/configuration-1\/"},"modified":"2025-02-18T15:33:36","modified_gmt":"2025-02-18T23:33:36","slug":"configuration-1","status":"publish","type":"page","link":"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/","title":{"rendered":"Configuration"},"content":{"rendered":"<p>Before beginning the configuration of the task, consider whether your synchronization will map data on ExtraView&#8217;s repeating rows.&nbsp; If this is the case, then ensure the following behavior settings have the appropriate values:<\/p>\n<ul>\n<li>\n\t\t<code>MULTI_RELEASE_XML<\/code> should be set to a value of <code>YES<\/code><\/li>\n<li>\n\t\t<code>CLI_EDIT_MULTI_VALUE_FIELDS<\/code> should be set to a value of <code>YES<\/code>, if you are migrating any multi-value fields between two servers<\/li>\n<li>\n\t\tIf you intend to map the <code>ORIGINATOR <\/code>field, then the behavior setting named <code>ALLOW_CLI_UPDATE_ORIGINATOR<\/code> should be set to a value of <code>YES<\/code>.<\/li>\n<\/ul>\n<p>Go to <strong>Administration<\/strong> &#8211;&gt; <strong>Operational Tasks<\/strong> &#8211;&gt; <strong>Task Manager<\/strong> to view all the tasks.&nbsp; <strong>Add a new task<\/strong> and choose the <em>ExtraView Peer Daemon Task &#8211; Handles replication between ExtraView instances<\/em> to begin the configuration of the task.<\/p>\n<p>To describe a specific synchronization, each configured integration has the following fields:<\/p>\n<ol>\n<li>\n\t\tTask Name<\/li>\n<li>\n\t\tThe Title of the task<\/li>\n<li>\n\t\tThe Node ID where the task runs<\/li>\n<li>\n\t\tThe Start Option.&nbsp; Typically this will be <code>START_NOW<\/code><\/li>\n<li>\n\t\tPoll Interval.&nbsp; The default time is 30 seconds.&nbsp; This timer determines the starting of the integration task and the frequency with which it runs. &nbsp;Note the configuration options <code>EVPOLLWAITTIME <\/code>and <code>EVPOLLWAITTIME2<\/code>&nbsp;also have an effect on timing.&nbsp;See below for a note on this topic<\/li>\n<li>\n\t\tThe Class Name &#8211; this must be <code>com.extraview.sccintegration.EVPeerDaemonTask<\/code><\/li>\n<li>\n\t\tThe Properties &#8211; this is where the mappings and other configuration options of the daemon are configured.<\/li>\n<\/ol>\n<p>You may configure more than one ExtraView Peer Daemon task.&nbsp; This should be done when you want to integrate one instance with two or more other instances.&nbsp; Another use of multiple tasks being configured may be to independently sychronize different business areas between two instances.&nbsp; The properties and mappings of the synchronization are defined within several sections as shown in the remainder of this page.<\/p>\n<h3>\n\tServer Connection Information<\/h3>\n<table border=\"0\" cellpadding=\"2\" cellspacing=\"2\" style=\"width: 100%;\">\n<tbody>\n<tr>\n<td style=\"width: 25%; vertical-align: top;\">\n\t\t\t\t<code>SERVER<\/code><\/td>\n<td style=\"width: 5%; vertical-align: top;\">\n\t\t\t\tRequired<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThis required entry specifies the URL of the first ExtraView server API<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>SERVER2<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tRequired<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThis required entry specifies the URL of the second ExtraView server API<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>\n\tUser Sign On Information<\/h3>\n<table border=\"0\" cellpadding=\"2\" cellspacing=\"2\" style=\"width: 100%;\">\n<tbody>\n<tr>\n<td style=\"width: 25%; vertical-align: top;\">\n\t\t\t\t<code>USER<\/code><\/td>\n<td style=\"width: 5%; vertical-align: top;\">\n\t\t\t\tRequired<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe ExtraView User ID that accesses the <code>SERVER<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>PASSWORD<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tRequired<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe password associated with <code>USER<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>USER2<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tRequired<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe ExtraView User ID that accesses the <code>SERVER2<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>PASSWORD2<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tRequired<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe password associated with <code>USER2<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>\n\tField Validation Information<\/h3>\n<table border=\"0\" cellpadding=\"2\" cellspacing=\"2\">\n<tbody>\n<tr>\n<td style=\"width: 25%; vertical-align: top;\">\n\t\t\t\t<code>BYPASS_EDIT_TEST<\/code><\/td>\n<td style=\"width: 5%; vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe fields for replication may be chosen from either server without being part of the EDIT_PROBLEM layout.&nbsp; When this is set to FALSE, the fields in the replication must be in the associated layout for the authorized user \/ area \/ project<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>BYPASS_ADD_TEST<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe fields for replication may be chosen from either server without being part of the ADD_PROBLEM layout.&nbsp; When this is set to FALSE, the fields in the replication must be in the associated layout for the authorized user \/ area \/ project<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>BYPASS_DETAILED_<br \/>\n\t\t\t\tREPORT_TEST<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe fields for replication may be chosen from either server without being part of the DETAILED_REPORT layout.&nbsp; When this is set to FALSE, the fields in the replication must be in the associated layout for the authorized user \/ area \/ project<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>\n\tMapping&nbsp;Information<\/h3>\n<p>Mappings may be bi-directional or uni-drectional.&nbsp; This syntax is only used within the mapping section of the configuration properties and is not used elsewhere.&nbsp; Consider the following:<\/p>\n<table border=\"0\" cellpadding=\"2\" cellspacing=\"2\">\n<tbody>\n<tr>\n<td>\n\t\t\t\t<code><font face=\"Courier New\">evfn.&lt;ExtraView field name&gt; = evfn2.&lt;ExtraView field name&gt;<\/font><\/code><\/td>\n<td>\n\t\t\t\tThe mapping of the field&nbsp;is bidirectional<\/td>\n<\/tr>\n<tr>\n<td>\n\t\t\t\t<code><font face=\"Courier New\">evfn.&lt;ExtraView field name&gt; =&gt; evfn2.&lt;ExtraView field name&gt;<\/font><\/code><\/td>\n<td>\n\t\t\t\tThis only maps from SERVER to SERVER2<\/td>\n<\/tr>\n<tr>\n<td>\n\t\t\t\t<code><font face=\"Courier New\">evfn.&lt;ExtraView field name&gt; &lt;= evfn2.&lt;ExtraView field name&gt;<\/font><\/code><\/td>\n<td>\n\t\t\t\tThis only maps from SERVER2 to SERVER<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The three classes of metadata objects which can be synchronized are:<font color=\"#000000\" face=\"Times New Roman\" size=\"3\">&nbsp;<\/font><font color=\"#000000\" face=\"Times New Roman\" size=\"3\"> <\/font><\/p>\n<ul>\n<li>\n\t\t<strong>UDF enumerated field values<\/strong> &#8211; You may specify any subset of all the enumerated fields to be synchronized.&nbsp; UDF list values are upserted based on their last date updated, which must be later than the latest date when the last UDF list update was done.&nbsp; Lazy propagation is an additional way that UDF list values are propagated:<\/p>\n<ul>\n<li>\n<p>An issue upsert is received from the peer, containing a UDF list value reference that does not map to any existing UDF list value on the server<\/p>\n<\/li>\n<li>\n<p>This triggers the insertion of the UDF list entry on the server, and an identity mapping to be established, thereby allowing the issue upsert to complete. This only inserts a single locale\u2019s value and no value is set in the ENABLED or SORT_SEQ fields of the UDF list entry<\/p>\n<\/li>\n<li>\n<p>During a later poll of the peer server, the UDF list value(s) that were inserted in&nbsp;the previous step&nbsp;are replicated by generating a metadata upsert from the UDF list values, as retrieved from the peer.&nbsp; Note that this step bypasses the timestamp restriction that normally would prevent a UDF list update.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n\t\t<strong>Allowed Values<\/strong> &#8211; The allowed value mapping includes only&nbsp;Allowed Value Types where both the parent field and the child field are mapped<br \/>\n\t\t&nbsp;<\/li>\n<li>\n\t\t<strong>Non-transactional metadata<\/strong> &#8211;&nbsp;Mappings for Relationship Groups, Attachments and Rankings are supported<\/li>\n<\/ul>\n<table border=\"0\" cellpadding=\"2\" cellspacing=\"2\">\n<tbody>\n<tr>\n<td style=\"width: 25%; vertical-align: top;\">\n\t\t\t\tGlobal Mapping of Field Names<\/td>\n<td style=\"width: 5%; vertical-align: top;\">\n\t\t\t\tRequired<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>evfn.&lt;ExtraView field name&gt; = evfn2.&lt;ExtraView field name&gt;<\/code><\/p>\n<p>\t\t\t\tMap the named field <code>evfn <\/code>in the first ExtraView server to the named field <code>evfn2 <\/code>in the second ExtraView server, and vice versa as this is a bi-derectional assignment.&nbsp; This is a global mapping of the field.&nbsp; Unlike other integration daemons, you must map all fields that you want to synchronize between databases.&nbsp; This ensures that the processing involved is kept to a minimum.&nbsp; You must always map the AREA and PROJECT fields, else an error occurs and no processing is performed.<\/p>\n<p>\t\t\t\tNote: The <code>CLI_EDIT_MULTI_VALUE_FIELDS<\/code> behavior setting must be set to <code>YES<\/code> in order for multi-value fields to be visible and editable in ExtraView.<\/p>\n<h4>\n\t\t\t\t\tExamples<\/h4>\n<p>\t\t\t\t<code>evfn.SHORT_DESCR = evfn2.SHORT_DESCR<br \/>\n\t\t\t\tevfn.DESCRIPTION = evfn2.DESCRIPTION<br \/>\n\t\t\t\tevfn.SHORT_DESCR = evfn2.FRED_TEXTAREA<br \/>\n\t\t\t\tevfn.AREA = evfn2.AREA<br \/>\n\t\t\t\tevfn.PROJECT = evfn2.PROJECT<br \/>\n\t\t\t\tevfn.OP_SYS = evfn2.OP_SYS<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\tField Value Mapping<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>evv.&lt;ExtraView field name&gt;.&lt;ExtraView field value&gt; = evv2.&lt;ExtraView field name&gt;.&lt;ExtraView field value&gt;<\/code><\/p>\n<p>\t\t\t\tMap the field value <code>evv<\/code> in the first ExtraView server to the field value <code>evv2<\/code>&nbsp;in the second ExtraView server, and vice versa.<\/p>\n<p>\t\t\t\tNote: These value mappings must be defined for mapped fields with a enumerated display type,(list, popup, radio, checkbox), in order for the synchronization to work.&nbsp; Note that the mappings occur by comparing the titles to the fields.&nbsp; If the values do not match exactly between servers, then the field is omitted from the synchronization transaction with a warning in the log.<\/p>\n<p>\t\t\t\tNote: spaces in field values must be escaped with the \\ character.<\/p>\n<h4>\n\t\t\t\t\tExamples<\/h4>\n<p><code>evv.STATUS.In\\ Progress = evv2.STATUS.Work\\ In\\ Progress<br \/>\n\t\t\t\t\tevv.AREA.Empty\\ Area = evv2.AREA.Engineering\\ Issues<br \/>\n\t\t\t\t\tevv.PROJECT.Empty\\ Area\\ -\\ Project\\ Data = evv2.PROJECT.Defects<\/code><\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\tField Value Mapping within a Business Area \/ Project<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>evv.&lt;AREA name&gt;.&lt;PROJECT name&gt;.&lt;ExtraView field name&gt;.&lt;ExtraView field value&gt; = evv2.&lt;AREA name&gt;.&lt;PROJECT name&gt;.&lt;ExtraView field name&gt;.&lt;ExtraView field value&gt;<\/code><\/p>\n<p>\t\t\t\tMap the field value <code>evv<\/code>&nbsp;in the business area and project in the first ExtraView server to the field value <code>evv2<\/code> in the business area and project in the second ExtraView server, and vice versa.<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\tUser Mapping<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>evv.user.&lt;ExtraView user id&gt; = evv2.user.&lt;ExtraView user id&gt;<\/code><\/p>\n<p>\t\t\t\tMaps the information for the <code>&lt;ExtraView user id&gt;<\/code> in the first ExtraView server to the user id in the second ExtraView server, and vice-versa.&nbsp; Note that User IDs and all supporting information&nbsp;are automatically inserted into the target instance when they do not exist but are referenced within the issue data.<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>SERVER <\/code>Item ID Mapping<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tRequired<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>EVID_FIELD = &lt;ExtraView Field Name&gt;<\/code><\/p>\n<p>\t\t\t\tIdentify the name of the field in the first ExtraView server containing the mapped item ID in the second ExtraView server.&nbsp; The field used for this purpose should have the following data dictionary attributes:<\/p>\n<p>\t\t\t\t\u200b- Display type = Text<br \/>\n\t\t\t\t&#8211; Select for Reports = Yes<br \/>\n\t\t\t\t&#8211; Filter Criteria = Yes<\/p>\n<p>\t\t\t\tThe <code>EVID_FIELD <\/code>does not need to be on the screen layout.<\/p>\n<h4>\n\t\t\t\t\tExample<\/h4>\n<p><code>EVID_FIELD = EV_ID<\/code><\/p>\n<div>\n\t\t\t\t\tIf you are synchronizing more than two ExtraView instances, you should use different fields to map the IDs on each server.<br \/>\n\t\t\t\t\t&nbsp;<\/div>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>SERVER2 <\/code>Item ID Mapping<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tRequired<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>EVID_FIELD2 = &lt;ExtraView Field Name&gt;<\/code><\/p>\n<p>\t\t\t\tIdentify the name of the field in the second ExtraView server containing the mapped item ID in the first ExtraView server.&nbsp; The field used for this purpose should have the following data dictionary attributes:<\/p>\n<p>\t\t\t\t\u200b- Display type = Text<br \/>\n\t\t\t\t&#8211; Select for Reports = Yes<br \/>\n\t\t\t\t&#8211; Filter Criteria = Yes<\/p>\n<p>\t\t\t\tThe <code>EVID_FIELD <\/code>does not need to be on the screen layout.<\/p>\n<h4>\n\t\t\t\t\tExample<\/h4>\n<p>\t\t\t\t<code>EVID_FIELD2 = EV_ID<\/code><br \/>\n\t\t\t\t&nbsp;<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\tRelationship Group Mapping<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>rg.&lt;Relationship Group Name&gt; = rg2.&lt;Relationship Group Name&gt;<\/code><\/p>\n<p>\t\t\t\tThis mapping provides for the replication of relationship group entries between the instances.&nbsp; Note that you may map between&nbsp;relationship groups with different names on each server.&nbsp; Only those relationship group entries that have issues that are replicated by the integration task are replicated.&nbsp; At this point only parent-child relationships are support for synchronization.<\/p>\n<h4>\n\t\t\t\t\tExample<\/h4>\n<p>\t\t\t\t<code>rg.my_relationship_group = rg2.another_relationship_group<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\tRepeating Row mapping<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tYou must have a repeating row field with a text display type defined in both servers to facilitate the mapping.&nbsp; These fields should not be placed on the repeating row layouts.&nbsp; Ensure that you set the <strong>Field Belongs To<\/strong> to a value of <code>Repeating Row<\/code> <code>Records<\/code>&nbsp; The fields are analogous to the <code>EVID_FIELD <\/code>and <code>EVID_FIELD2<\/code> fields that map issues and should have the same data dictionary attributes as specified for these fields.&nbsp; The fields do not need to be on the screen layouts.<\/p>\n<p>\t\t\t\tAs described in the Administration Guide, there is one built-in repeating row type in ExtraView, named <code>RELEASE<\/code>.&nbsp; If you are mapping this repeating row type&nbsp;from <code>SERVER&nbsp;<\/code>to <code>SERVER2<\/code>, there is no need to explicitly provide a mapping for the layout type.&nbsp; However, you may often want to map repeating rows with different layout types.&nbsp; In these cases, you use the following syntax to identify the repeating row types being mapped:<\/p>\n<p><code>layout_type.xxxx = layout_type2.yyyy<\/code><\/p>\n<p>where <code>xxxx <\/code>and <code>yyyy <\/code>are the layout type names for the repeating row layouts being mapped <span style=\"font-size:9.0pt;font-family:&quot;Arial&quot;,sans-serif;\nmso-fareast-font-family:&quot;Times New Roman&quot;;color:#333333;mso-ansi-language:EN-US;\nmso-fareast-language:EN-US;mso-bidi-language:AR-SA\">on <code>SERVER <\/code>and <code>SERVER2 <\/code>respectively<\/span>.&nbsp; You may have multiple entries of this kind to map fields for multiple repeating row layouts within the same issue.&nbsp; The statements that map the fields themselves will not be ambiguous as fields on one repeating row layout are never configured on another repeating row layout.<\/p>\n<h4>\n\t\t\t\t\tExample<\/h4>\n<p><code># EVID_FIELD = &lt;ExtraView Field Name&gt;<br \/>\n\t\t\t\t\t#<br \/>\n\t\t\t\t\t# Identify the name of the field in the first ExtraView server containing the mapped # item ID<\/code> <code>in the second ExtraView server.<br \/>\n\t\t\t\t\t#<br \/>\n\t\t\t\t\tEVID_FIELD = EV_ID<br \/>\n\t\t\t\t\tRR_EVID_FIELD = RR_EV_ITEM_ID<\/code><\/p>\n<p><code># EVID_FIELD2 = &lt;ExtraView field name&gt;<br \/>\n\t\t\t\t\t#<br \/>\n\t\t\t\t\t# Identify the name of the field in the second ExtraView server containing the<br \/>\n\t\t\t\t\t# mapped item ID in the first ExtraView server.<br \/>\n\t\t\t\t\t#<br \/>\n\t\t\t\t\tEVID_FIELD2 = EV_ID<br \/>\n\t\t\t\t\tRR_EVID_FIELD2 = RR_EV_ITEM_ID<\/code><\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\tDeleted Issue mapping<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tUnless it is necessary to map deleted issues from one server to another, the recommendation is to set this to <code>NO<\/code> for both the source and target servers&nbsp; The settings may either be:<\/p>\n<p>\t\t\t\t<code>deletes.client = NO<br \/>\n\t\t\t\tdeletes.client2 = NO<\/code><\/p>\n<p>\t\t\t\tor:<\/p>\n<p>\t\t\t\t<code>deletes.client = YES<br \/>\n\t\t\t\tdeletes.client2 = YES<\/code><\/p>\n<p>\t\t\t\tIf you set these to a value of <code>NO<\/code>, then if issues are deleted on one server, they will not be deleted on the other server.&nbsp; It is useful for performance to set this value to <code>NO<\/code> if you are using the integration to migrate a significant number of records from one server to another as part of an initial data migration.&nbsp; Once the initial migration of records is complete, you can set this back to <code>YES<\/code> and the deletes will happen over time.<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>INSERT_VALUES<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>INSERT_VALUES.&lt;ExtraView field name&gt; = &lt;ExtraView field value&gt;<\/code><\/p>\n<p>\t\t\t\tThis property is used to provide a value to be used to set a field in all issue INSERT operations in the first ExtraView <code>SERVER<\/code>.&nbsp; This is not used for updates, only inserts and its primary purpose is to ensure that you provide field values for required fields on the target instance.<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>INSERT_VALUES2<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code><font face=\"Courier New\">INSERT_VALUES2.&lt;ExtraView field name&gt; = &lt;ExtraView field value&gt;<\/font><\/code><\/p>\n<p>\t\t\t\tThis property is used to provide a value to be used to set a field in all issue INSERT operations in <code>SERVER2<\/code>.&nbsp; This is not used for updates, only inserts<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>\n\tSynchronization Properties<\/h3>\n<p>The properties that begin with the characters <code>MI_ <\/code>refer to <code>SERVER<\/code>, whilst the properties that begin with the characters <code>MJ_<\/code> refer to the <code>SERVER2<\/code>.<\/p>\n<table border=\"0\" cellpadding=\"2\" cellspacing=\"2\">\n<tbody>\n<tr>\n<td style=\"width: 25%; vertical-align: top;\">\n\t\t\t\tIdentifying the field in <code>SERVER <\/code>upon which synchronization occurs<\/td>\n<td style=\"width: 5%; vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>MI_FIELD = &lt;ExtraView field name&gt;<\/code><\/p>\n<p>\t\t\t\tIdentify the field to be inspected for the <code>MI_REGEX<\/code> evaluation to determine if an item in the first ExtraView server maps to an item in the second ExtraView server.<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe expression which evaluates <code>MI_FIELD <\/code>in <code>SERVER<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>MI_REGEX = &lt;regular expression&gt;<\/code><\/p>\n<p>\t\t\t\tThe expression that is used with the <code>MI_FIELD<\/code> value to determine if an item in the first ExtraView server maps to an item in the second ExtraView server.&nbsp; If <code>MI_FIELD<\/code> is set, then this entry is required.<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\tIdentifying the field in <code>SERVER2 <\/code>upon which synchronization occurs<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>MI_FIELD2 = &lt;ExtraView field name&gt;<\/code><\/p>\n<p>\t\t\t\tIdentify the field to be inspected for the <code>MI_REGEX<\/code> evaluation to determine if an item in the second ExtraView server maps to an item in the first ExtraView server.<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe expression which evaluates <code>MI_FIELD2 <\/code>in <code>SERVER2<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>MI_REGEX2 = &lt;regular expression&gt;<\/code><\/p>\n<p>\t\t\t\tThe expression that is used with the <code>MI_FIELD2<\/code> value to determine if an item in the second ExtraView server maps to an item in the first ExtraView server.&nbsp; If <code>MI_FIELD<\/code> is set, then this entry is required.<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe expression which determines whether an issue in <code>SERVER <\/code>maps to an issue in <code>SERVER2<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tIn this expression, a string in the form <code>\"__NAME__\"<\/code> refers to a field name in the ExtraView issue; when the expression is evaluated, this string is substituted&nbsp;with the value of the field in the issue being tested.<\/p>\n<h4>\n\t\t\t\t\tExamples<\/h4>\n<p>\t\t\t\t<code>MI_POLL_TRIGGER = &lt;Boolean expression with replaceable variables&gt;<br \/>\n\t\t\t\tMI_POLL_TRIGGER = \"__area__\" eq \"Empty Area\"<\/code><br \/>\n\t\t\t\t&nbsp;<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe expression which determines whether an issue in <code>SERVER2 <\/code>maps to an issue in <code>SERVER<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tIn this expression, a string in the form <code>\"__NAME__\"<\/code> refers to a field name in the ExtraView issue; when the expression is evaluated, this string is substituted&nbsp;with the value of the field in the issue being tested.<\/p>\n<h4>\n\t\t\t\t\tExamples<\/h4>\n<p>\t\t\t\t<code>MJ_POLL_TRIGGER = &lt;Boolean expression with replaceable variables&gt;<br \/>\n\t\t\t\tMJ_POLL_TRIGGER = \"__area__\" eq \"Empty Area\"<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>EVPOLLWAITTIME<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe number of milliseconds between poll times of the first server (<code>SERVER<\/code>).&nbsp; The default is 10,000 milliseconds (10 seconds)<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>EVPOLLWAITTIME2<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe number of milliseconds between poll times of the second server (<code>SERVER2<\/code>).&nbsp; The default is 10,000 milliseconds (10 seconds)<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>ATTACHMENT_UPSERT<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThis is a switch which can have the values of <code>YES <\/code>or <code>NO<\/code>.&nbsp; When the value is <code>YES<\/code>, attachments are uperted along with the issues upon synchronization<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>SOCKET_TIMEOUT_SECONDS<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThis timeout sets the time within which the integration daemon should wait for a response from both the source and target servers.&nbsp; The default value for this is <code>300<\/code> seconds.&nbsp; If the records being synchronized are large, or there are a significant number of attachments, document fields or image fields, then this number should be increased, perhaps to <code>800 <\/code>or <code>1000<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<font><span class=\"report_text\"><code>PUSH_DOWN_FILTERS<\/code><\/span><\/font><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tSee the following section<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<font><span class=\"report_text\"><code>PUSH_DOWN_FILTERS2<\/code><\/span><\/font><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tOptional<\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tSee the following section<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Note<\/strong>: The Poll Interval for the task and the configuration options&nbsp;<code>EVPOLLWAITTIME <\/code>and <code>EVPOLLWAITTIME2<\/code> have different purposes.&nbsp; The default times for these three options should work well for most instances.&nbsp; The task&#8217;s&nbsp;Poll Interval is the frequency with which commands to the task (such as <code>START_NOW <\/code>and <code>STOP_NOW<\/code>) are processed.&nbsp; The <code>EVPOLLWAITTIME <\/code>and <code>EVPOLLWAITTIME2 <\/code>are independent timers that control how often the two background threads (<code>EVPOLLWAITTIME <\/code>and <code>EVPOLLWAITTIME2<\/code>) check their work queues, once the task is running.&nbsp; Note that the Poll Interval is set in seconds, while <code>EVPOLLWAITTIME <\/code>and <code>EVPOLLWAITTIME2 <font color=\"#333333\" face=\"Arial\">are set in milliseconds.<\/font><\/code><\/p>\n<h3>\n\tPush Down Filters<\/h3>\n<p style=\"margin-left:0px; margin-right:0px\">In order to extract the issues from the <code>SERVER <\/code>to synchronize with <code>SERVER2<\/code>, ExtraView performs queries on the <code>SERVER <\/code>database.&nbsp; To make these queries more efficient, thereby speeding the process, there are two properties, <font><span class=\"report_text\"><code>PUSH_DOWN_FILTERS<\/code> and <code>PUSH_DOWN_FILTERS2<\/code> that specify filters that are added to the queries that extract data from the ExtraView <code>SERVER <\/code>for replication to the peer server <code>SERVER2<\/code>.<\/span><\/font><\/p>\n<p style=\"margin-left:0px; margin-right:0px\"><font><span class=\"report_text\">&nbsp;The syntax of the <code>PUSH_DOWN_FILTERS<\/code> parameters is the same as the syntax for <code>MI_POLL_TRIGGER<\/code> &#8211; namely, an expression including the substitutable variables <code>__area__<\/code> and <code>__project__<\/code> with the operators <code>eq <\/code>and <code>ne<\/code>.<\/span><\/font><\/p>\n<p style=\"margin-left:0px; margin-right:0px\"><font><span class=\"report_text\">&nbsp;<code>PUSH_DOWN_FILTERS<\/code> is the parameter name for the <code>SERVER <\/code>filters and <code>PUSH_DOWN_FILTERS2<\/code> is the parameter name for <code>SERVER2<\/code>.<\/span><\/font><\/p>\n<p style=\"margin-left:0px; margin-right:0px\"><font><span class=\"report_text\">&nbsp;<strong>Example<\/strong>: to exclude issues from a business area titled Engineering Issues:<\/span><\/font><\/p>\n<p style=\"margin-left:0px; margin-right:0px\"><code><font><span class=\"report_text\">&nbsp;PUSH_DOWN_FILTERS = __area__ ne \"Engineering Issues\"<\/span><\/font><\/code><\/p>\n<p style=\"margin-left:0px; margin-right:0px\"><font><span class=\"report_text\">&nbsp;<strong>Example<\/strong>: to include only issues from the business area titled <code>Engineering Issues<\/code> and a project titled <code>Contacts Project Data<\/code>:<\/span><\/font><\/p>\n<p style=\"margin-left:0px; margin-right:0px\"><code><font><span class=\"report_text\">PUSH_DOWN_FILTERS = __area__ eq \"Engineering Issues\" || __project__ eq \"Contacts - Project Data\"<\/span><\/font><\/code><\/p>\n<h3>\n\tNotification Options<\/h3>\n<p>Notification is provided to administrators via email upon error conditions as follows<\/p>\n<table border=\"0\" cellpadding=\"2\" cellspacing=\"2\">\n<tbody>\n<tr>\n<td style=\"width: 25%;\">\n\t\t\t\t<code>DAEMON_ERROR_<br \/>\n\t\t\t\tNOTIFICATION_INTERVAL<\/code><\/td>\n<td style=\"width: 5%;\">\n\t\t\t\tOptional<\/td>\n<td>\n\t\t\t\tNotifications will be sent to the administrators no more often than the number of minutes specified in this property&nbsp;<\/td>\n<\/tr>\n<tr>\n<td>\n\t\t\t\t<code>DAEMON_WARN_<br \/>\n\t\t\t\tNOTIFICATION_COUNT<\/code><\/td>\n<td>\n\t\t\t\tOptional<\/td>\n<td>\n\t\t\t\tError email notification will not be sent until <code>DAEMON_WARN_NOTIFICATION_COUNT<\/code> error logs have occurred in <code>DAEMON_WARN_NOTIFICATION_INTERVAL<\/code> minutes<\/td>\n<\/tr>\n<tr>\n<td>\n\t\t\t\t<code>DAEMON_WARN_<br \/>\n\t\t\t\tNOTIFICATION_INTERVAL<\/code><\/td>\n<td>\n\t\t\t\tOptional<\/td>\n<td>\n\t\t\t\tError email notification will not be sent until <code>DAEMON_WARN_NOTIFICATION_COUNT<\/code> error logs have occurred in <code>DAEMON_WARN_NOTIFICATION_INTERVAL<\/code> minutes<\/td>\n<\/tr>\n<tr>\n<td>\n\t\t\t\t<code>DAEMON_ERROR_<br \/>\n\t\t\t\tTHRESHOLD<\/code><\/td>\n<td>\n\t\t\t\tOptional<\/td>\n<td>\n\t\t\t\tErrors that are sent to the log are not reported until there are <code>DAEMON_ERROR_THRESHOLD<\/code> errors<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>\n\tLogging Properties<\/h3>\n<table border=\"0\" cellpadding=\"2\" cellspacing=\"2\">\n<tbody>\n<tr>\n<td style=\"width: 25%; vertical-align: top;\">\n\t\t\t\t<code>LOG_FILE_PATH_NAME<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe EV Peer Daemon log file<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>LOG_FILE_PATH_<br \/>\n\t\t\t\tNAME_ABSOLUTE<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThis setting may be used for standalone installations on Windows, or when ExtraView is running within a war file<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>USE_SYSTEM_LOG<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tIf this setting is Y, the daemon will use the ExtraView application server log file as opposed to the log file defined in LOG_FILE_PATH_NAME<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>PSP_LOG<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tUse this statement with a value of Y if you want to write the SQL from the task to the log file<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>XML_LOG_FLAG<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tSet this to a value of TRUE if you want to use XML format within the log file<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>LOG_FILE_MAX_SIZE<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe maximum size of the log file, before it rolls over to a new file, in kB<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>LOG_CHARSET<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThis should be UTF-8<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>LOG_INCLUDE_<br \/>\n\t\t\t\tTHREAD_NAME<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tA value of YES writes the Java thread name with each entry into the log file<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>DEFAULT_LOG_LEVEL<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe default log level for the daemon.&nbsp; The usual value is 6<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>LOG_LEVEL<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe log level for the daemon.&nbsp; The usual value is 6<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>LOG_DATE_FORMAT<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tA valid date format to use in generating log records.&nbsp; The default is yyyy-MM-dd<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>LOG_TIME_FORMAT<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tA valid time format to use in generating log records.&nbsp; The default is kk:mm:ss<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>LOG_TIME_AT_CREATION<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThis entry may be true or false.&nbsp; If true, the log file name is generated with a creation date\/time string appended. The default is false.<\/td>\n<\/tr>\n<tr>\n<td style=\"vertical-align: top;\">\n\t\t\t\t<code>LOG_FILE_MANAGE_SCRIPT<\/code><\/td>\n<td style=\"vertical-align: top;\">\n\t\t\t\tThe name of a script to run when switching log files. The default is none<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>\n\tCloned Issues<\/h3>\n<p><span style=\"font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;\nmso-fareast-font-family:&quot;Times New Roman&quot;;color:black;mso-ansi-language:EN-US;\nmso-fareast-language:EN-US;mso-bidi-language:AR-SA\">If an issue that is mapped is subsequently cloned, the mapping identity field should not be propagated to the cloned issue.&nbsp; The reason for this is that it would establish a mapping from one peer issue to two issues (i.e. the original issue and its clone).&nbsp; This is not a fatal error, but the behavior would be odd, causing updates to the peer issue for each update to either&nbsp;the original issue&nbsp;or the cloned issue.&nbsp; To handle this behavior, there is a&nbsp;data dictionary&nbsp;attribute that prevents the cloning of the field value for specific fields.&nbsp; This attribute is set when the field is used as a mapping field in the&nbsp;integration daemon.<\/p>\n<p>\tSetting the DO_NOT_CLONE data dictionary&nbsp;attribute for a field means that the containing field&#8217;s value will not be propagated to any clone of an issue &#8212; its value will be null in the cloned issue.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Before beginning the configuration of the task, consider whether your synchronization will map data on ExtraView&#8217;s repeating rows.&nbsp; If this is the case, then ensure the following behavior settings have the appropriate values: MULTI_RELEASE_XML should be set to a value of YES CLI_EDIT_MULTI_VALUE_FIELDS should be set to a value of YES, if you are migrating&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":24436,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_lmt_disableupdate":"no","_lmt_disable":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"class_list":["post-24437","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v25.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Configuration - Product Documentation<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Configuration - Product Documentation\" \/>\n<meta property=\"og:description\" content=\"Before beginning the configuration of the task, consider whether your synchronization will map data on ExtraView&#8217;s repeating rows.&nbsp; If this is the case, then ensure the following behavior settings have the appropriate values: MULTI_RELEASE_XML should be set to a value of YES CLI_EDIT_MULTI_VALUE_FIELDS should be set to a value of YES, if you are migrating...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/\" \/>\n<meta property=\"og:site_name\" content=\"Product Documentation\" \/>\n<meta property=\"article:modified_time\" content=\"2025-02-18T23:33:36+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"18 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/\",\"url\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/\",\"name\":\"Configuration - Product Documentation\",\"isPartOf\":{\"@id\":\"https:\/\/docs.extraview.com\/v25\/#website\"},\"datePublished\":\"2024-02-15T22:53:34+00:00\",\"dateModified\":\"2025-02-18T23:33:36+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/docs.extraview.com\/v25\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ExtraView 25\",\"item\":\"https:\/\/docs.extraview.com\/v25\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Integration Guides\",\"item\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Extraview &#8211; ExtraView Peer Instance Integration\",\"item\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/\"},{\"@type\":\"ListItem\",\"position\":5,\"name\":\"Configuration\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/docs.extraview.com\/v25\/#website\",\"url\":\"https:\/\/docs.extraview.com\/v25\/\",\"name\":\"ExtraView Product Documentation\",\"description\":\"ExtraView Documentation\",\"publisher\":{\"@id\":\"https:\/\/docs.extraview.com\/v25\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/docs.extraview.com\/v25\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/docs.extraview.com\/v25\/#organization\",\"name\":\"ExtraView Corporation\",\"url\":\"https:\/\/docs.extraview.com\/v25\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/docs.extraview.com\/v25\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/docs-stg.extraview.com\/wp-content\/uploads\/2024\/03\/favicon.png\",\"contentUrl\":\"https:\/\/docs-stg.extraview.com\/wp-content\/uploads\/2024\/03\/favicon.png\",\"width\":512,\"height\":512,\"caption\":\"ExtraView Corporation\"},\"image\":{\"@id\":\"https:\/\/docs.extraview.com\/v25\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Configuration - Product Documentation","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/","og_locale":"en_US","og_type":"article","og_title":"Configuration - Product Documentation","og_description":"Before beginning the configuration of the task, consider whether your synchronization will map data on ExtraView&#8217;s repeating rows.&nbsp; If this is the case, then ensure the following behavior settings have the appropriate values: MULTI_RELEASE_XML should be set to a value of YES CLI_EDIT_MULTI_VALUE_FIELDS should be set to a value of YES, if you are migrating...","og_url":"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/","og_site_name":"Product Documentation","article_modified_time":"2025-02-18T23:33:36+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"18 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/","url":"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/","name":"Configuration - Product Documentation","isPartOf":{"@id":"https:\/\/docs.extraview.com\/v25\/#website"},"datePublished":"2024-02-15T22:53:34+00:00","dateModified":"2025-02-18T23:33:36+00:00","breadcrumb":{"@id":"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/configuration-1\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/docs.extraview.com\/v25\/"},{"@type":"ListItem","position":2,"name":"ExtraView 25","item":"https:\/\/docs.extraview.com\/v25\/"},{"@type":"ListItem","position":3,"name":"Integration Guides","item":"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/"},{"@type":"ListItem","position":4,"name":"Extraview &#8211; ExtraView Peer Instance Integration","item":"https:\/\/docs.extraview.com\/v25\/extraview-25\/integration-guides-1\/extraview-extraview-peer-instance-integration-1\/"},{"@type":"ListItem","position":5,"name":"Configuration"}]},{"@type":"WebSite","@id":"https:\/\/docs.extraview.com\/v25\/#website","url":"https:\/\/docs.extraview.com\/v25\/","name":"ExtraView Product Documentation","description":"ExtraView Documentation","publisher":{"@id":"https:\/\/docs.extraview.com\/v25\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/docs.extraview.com\/v25\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/docs.extraview.com\/v25\/#organization","name":"ExtraView Corporation","url":"https:\/\/docs.extraview.com\/v25\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/docs.extraview.com\/v25\/#\/schema\/logo\/image\/","url":"https:\/\/docs-stg.extraview.com\/wp-content\/uploads\/2024\/03\/favicon.png","contentUrl":"https:\/\/docs-stg.extraview.com\/wp-content\/uploads\/2024\/03\/favicon.png","width":512,"height":512,"caption":"ExtraView Corporation"},"image":{"@id":"https:\/\/docs.extraview.com\/v25\/#\/schema\/logo\/image\/"}}]}},"taxonomy_info":[],"featured_image_src_large":false,"author_info":{"display_name":"carl.koppel","author_link":"https:\/\/docs.extraview.com\/v25\/author\/carl-koppel\/"},"comment_info":0,"_links":{"self":[{"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/pages\/24437","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/comments?post=24437"}],"version-history":[{"count":0,"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/pages\/24437\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/pages\/24436"}],"wp:attachment":[{"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/media?parent=24437"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}