Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0036811Retail ModulesWeb POSpublic2017-09-08 09:592017-09-25 13:11
Reportermalsasua 
Assigned ToRetail 
PrioritynormalSeveritymajorReproducibilityrandom
StatusclosedResolutionduplicate 
PlatformOS5OS Version
Product Version 
Target VersionFixed in VersionRR17Q4 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customerOBPS
Support ticket47412
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0036811: Import entries of type "Business partner" are duplicated
Descriptionsometimes, the Import Entries of type "business partner" are duplicated, so the first record is processed fine, but the rest are stuck in Errors While Importing window
Steps To ReproduceRANDOM:
. in POS: create a new business partner
. in BackOffice:
 . the business partner has been created but errors in Error While Importing window are stuck with the same record
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
duplicate of defect 0036712 closed migueldejuana Duplicated records in c_import_entry_archive under some circumstances 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-09-08 09:59malsasuaNew Issue
2017-09-08 09:59malsasuaAssigned To => Retail
2017-09-08 09:59malsasuaOBNetwork customer => Yes
2017-09-08 09:59malsasuaSupport ticket => 47412
2017-09-08 09:59malsasuaResolution time => 1506636000
2017-09-08 09:59malsasuaTriggers an Emergency Pack => No
2017-09-12 15:31PracticsIssue Monitored: Practics
2017-09-25 13:11marvintmReview Assigned To => marvintm
2017-09-25 13:11marvintmRelationship addedduplicate of 0036712
2017-09-25 13:11marvintmNote Added: 0099540
2017-09-25 13:11marvintmStatusnew => closed
2017-09-25 13:11marvintmResolutionopen => duplicate
2017-09-25 13:11marvintmFixed in Version => RR17Q4

Notes
(0099540)
marvintm   
2017-09-25 13:11   
After reviewing the problem further, we have concluded that it has the same root cause as issue 36712.