en:start
Differences
This shows you the differences between two versions of the page.
— | en:start [2025/04/26 12:26] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | TitleEngTAG | ||
+ | ===== What is Sprinkler ===== | ||
+ | |||
+ | <color # | ||
+ | |||
+ | || **Supported Versions** | Microsoft Dynamics 365 Business Central from v.14 to v.26, with data exchange even between different versions. || | ||
+ | || **Scalability** | Unidirectional or bidirectional replication, | ||
+ | || **SaaS Enabled** | Communication between different Tenants, as well as between SaaS and On-Prem instances. || | ||
+ | || **Flexibility** | Data exchange also between different tables, towards different fields, with different field sets for different destinations, | ||
+ | || **Data Subscriptions** | Data can be subscribed from Table lavel to a single Record level, and changes to subscribed data can be sent to subscribing systems both automatically and OnDemand. || | ||
+ | || **Transaction Management** | In-Transaction replication mode: in this configuration, | ||
+ | || **Trigger Management** | From setup, you can decide whether to invoke the standard OnInsert, OnModify, OnDelete, OnRename triggers of the receiving table, as well as individually each of the OnValidate triggers of the involved fields. || | ||
+ | || **Conditional Distribution** | Filters can be applied to records to exclude some records from the replication process. || | ||
+ | || **Integration with other Apps** | Public replication functions are available that can be called directly from code. || | ||
+ | || **Extensibility** | On the receiving node, the App exposes a series of subscribable Events:\\ - OnBeforeSpkInsertRecord / OnAfterSpkInsertRecord\\ - OnBeforeSpkModifyRecord / OnAfterSpkModifyRecord\\ - OnBeforeSpkDeleteRecord / OnAfterSpkDeleteRecord\\ - OnBeforeSpkRenameRecord / OnAfterSpkRenameRecord || | ||
+ | || **Data Protection** | Each field can be subjected to Masking with a one-way hash function, to obscure the data on the receiving Company. || | ||
+ | || **Control Dashboard** | A centralized Dashboard has been created that summarizes the status of all remote systems. || | ||
+ | || **License Free for Partners** | <WRAP tip> | ||
+ | |||
+ | <color # | ||
+ | |||
+ | ==== Detailed Operation ==== | ||
+ | |||
+ | In its basic configuration, | ||
+ | |||
+ | {{DistributionSchema-01.png}} | ||
+ | |||
+ | A flexible setup system in the Source Peer allows you to define in detail which operations should be detected and sent to different Target Peers, while a similar setup system on the individual Target Peer allows you to define at the same level of detail which operations, among those signaled, should be imported and replicated, or discarded. | ||
+ | |||
+ | A Company can also be configured at the same time as both a Source Peer and a Target Peer, and this allows you to define highly flexible bidirectional distribution schemes. | ||
+ | |||
+ | {{DistributionSchema-02.png}} | ||
+ | |||
+ | Data distribution is implemented via SOAP WebServices calls, allowing data exchange even between SaaS or remote systems. | ||
+ | |||
+ | {{DistributionSchema-03.png}} | ||
+ | |||
+ | (r) eeRisTAG |