Differences

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

@@ Line 1: / Line 1: @@
+TitleEngTAG
+<HTML><H3>Data Distribution Export Setup</H3></HTML>
+On this page you have to specify the changes you want to detect and report with Sprinkler to the remote system. This page is populated with a list of all existing tables on the database.
+{{DataDistributionSetupOUT.png}}
+  * [[AdvancedReplication|HOME Menu]]
+  * [[AdvancedReplication|ACTIONS Menu]]
+All configurations on this page are referred to the peer shown into the field //Peer Server ID//
+**Functionalities**
+  *	For each table you can choose to detect every INSERT, MODIFY, DELETE and/or RENAME transaction;
+  *	On an INSERT transaction, you can choose to detect and report all or even a limited set of fields; among this set, only the not-empty fields at the time of INSERT statement will be reported (this is relevant in case of DelayedInsert); the record key will be reported in any case.
+  * On a MODIFY transaction, you can choose to detect and report all or even a limited set of fields; any modification to a key field is reported as a RENAME.
+  * On a DELETE transaction, only the key fields will be reported.
+  * On a RENAME transaction, only the key fields will be reported, (both with original and modified values). Please refer to page [[RenameIssue|RENAME Important Topic]] for more informations.
+  * It is possible to setup one or more fields on a table to be read-only, or even the whole table; it is also provided a setup to disable the RENAME operation for a table.
+  * You can set a filter for each table: all operations on a record will be reported only if the record meets the filter.
+  * Every INSERT, MODIFY, DELETE, RENAME report is a single atomic operation, belonging to the same transaction of the trigger OnDatabaseInsert, OnDatabaseModify, OnDatabaseDelete or OnDatabaseRename of //ApplicationManagement// codeunit.
+**Limitations**
+  * FlowFields are not considered by Sprinkler, and will not be reported under any circumstance.
+  * BLOB fields are not considered by Sprinkler at this time, and will not be reported even if modified.
+For each table you can then specify:
+  * **Report Insertion** with possible values:
+    * blank - no INSERT operation will be reported,
+    * All Fields - all the not-blank fields (at the time of INSERT) will be reported,
+    * Some Fields - the AssistEdit button opens the [[OutFieldSelection|Fields Selection]] page for the detailed configuration: only the requested fields will be reported, but only if not-blank at the time of INSERT.
+  * **Report Modification** with possible values:
+    * blank - no MODIFY operation will be reported,
+    * All Fields - all the modified fields will be reported,
+    * Some Fields - the AssistEdit button opens the [[OutFieldSelection|Fields Selection]] page for the detailed configuration: only the requested fields will be reported, but only if modified.
+  * **Report Deletion** with possible values:
+      * blank - no DELETE operation will be reported,
+      * All Fields - only the key fields will be reported,
+      * Some Fields - the AssistEdit button opens the [[OutFieldSelection|Fields Selection]] page, but only the key fields will be reported.
+  * **Report Rename** - if set, every RENAME operation will be reported; only the Rec and xRec key fields will be reported.
+  * **Force Read-Only** - if set, any operation detected on a record will trigger an ERROR on the same transaction of the detected operation: the operation will be then reverted with a rollback.
+    * It must, however, pay particular attention to the fact that the ERROR may have unintended consequences if the operation is made without GUI (ex. by NAS).
+    * The ERROR will be raised only if the operation is detected: this flag will not effective if all //Report Insertion//, //Report Modification// and //Report Deletion// are blank.
+    * If a field or a table is set as Read-Only, this affects both manual and automatic operations (validations, triggers and so on); in this case, the only User enabled to modify such field or table is the //Data Distribution Service User// declared in //Data Distribution Setup//.
+  * **Prohibit Rename** - if set, any RENAME operation detected on a record will trigger an ERROR on the same transaction of the detected operation: the operation will be reverted with a rollback. Also in this case, the only User enabled to rename the record is the //Data Distribution Service User// declared in //Data Distribution Setup//.
+  * **Table Export Filter** - This filter will be applied to see if the record modified has to be reported: the filter syntax is the same used in Report DataItem TableView, for exemple
+  <code>               WHERE(Field1=FILTER(1..),Field2=CONST(EUR))</code>
+    * __WARNING: as seen in the example, it is suggested to use the numeric syntax instead of field caption (Field10 instead of caption of the field 10), because the numeric syntax is not language-dependent: otherwise unexpected errors may occur in the filter application__
+    * NOTE: this feature is dramatically time-consuming, and is better to use it only in case of real need.
+  * **Record Counter** - shows the number of records for the tables with a setup. It is suggested to hide this field to improve the page responsiveness.
+**Advanced Replication Filter** – This filter is applied on the selected table when the Advanced Replication buttons of HOME and ACTIONS menu are used. If not blank, this filter overrides the table filter specified as [Table Export Filter]. For more informations please see [[AdvancedReplication|Advanced Replication Tools]]. This filter is not used by the standard Data Distribution operations.
+  * [[AdvancedReplication|Advanced Replication Tools]]

Sprinkler

User Tools

Site Tools

Differences

Page Tools