0034616: In multi-server with replication of transactional tables the import entries should not be replicated to the other server

Description

In multi-server when a new import entry is created which is used to generate transactions and these transactions are also replicated, then these import entries should not be replicated to the other server. This because then they get processed twice.

In practice this works fine most of the time as symmetric ds detects duplicates and won't give an error. But it is safer not to replicate import entries.

So by default specific import entries for specific types of data should always have the setting that they are not to be replicated to other servers. These are: order, cashup, business partner, cash management.

Steps To Reproduce

Install multi-server
Do a cashup
See that import entry is created and processed in both servers

Proposed Solution

By default prevent import entry syncing for specific types of import entries.

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

duplicate of	design defect	0033534	RR16Q4	closed	mtaal	In non-synchronized mode and webpos using storeserver synchronization module both import entry an transactional tables are sync
related to	feature request	0033241	RR16Q4	closed	mtaal	Synchronized mode: in synchronized mode preference on then still don't do cashup in synchronized mode

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2016-11-24 13:50	mtaal	New Issue
2016-11-24 13:50	mtaal	Assigned To	=> mtaal
2016-11-24 13:50	mtaal	OBNetwork customer	=> No
2016-11-24 13:50	mtaal	Triggers an Emergency Pack	=> No
2016-11-24 13:50	mtaal	Relationship added	related to 0033241
2016-11-25 18:13	mtaal	Relationship added	duplicate of 0033534
2016-11-25 18:13	mtaal	Status	new => closed
2016-11-25 18:13	mtaal	Resolution	open => duplicate
2016-11-25 18:13	mtaal	Fixed in Version	=> RR16Q4