Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0034616Retail ModulesStoreServerpublic2016-11-24 13:502016-11-25 18:13
Reportermtaal 
Assigned Tomtaal 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionduplicate 
PlatformOS5OS Version
Product Version 
Target VersionRR17Q1Fixed in VersionRR16Q4 
Merge Request Status
Review Assigned To
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0034616: In multi-server with replication of transactional tables the import entries should not be replicated to the other server
DescriptionIn 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 ReproduceInstall multi-server
Do a cashup
See that import entry is created and processed in both servers
Proposed SolutionBy default prevent import entry syncing for specific types of import entries.
Additional Information
TagsNo tags attached.
Relationships
duplicate of design defect 0033534RR16Q4 closed mtaal In non-synchronized mode and webpos using storeserver synchronization module both import entry an transactional tables are sync 
related to feature request 0033241RR16Q4 closed mtaal Synchronized mode: in synchronized mode preference on then still don't do cashup in synchronized mode 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-11-24 13:50mtaalNew Issue
2016-11-24 13:50mtaalAssigned To => mtaal
2016-11-24 13:50mtaalTriggers an Emergency Pack => No
2016-11-24 13:50mtaalRelationship addedrelated to 0033241
2016-11-25 18:13mtaalRelationship addedduplicate of 0033534
2016-11-25 18:13mtaalStatusnew => closed
2016-11-25 18:13mtaalResolutionopen => duplicate
2016-11-25 18:13mtaalFixed in Version => RR16Q4

There are no notes attached to this issue.