Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0045842Retail ModulesWeb POSpublic2021-02-03 16:482021-02-12 07:58
Reporteravicente 
Assigned Toranjith_qualiantech_com 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionduplicate 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0045842: Confused message when the Full Refresh fails
DescriptionWhen the full refresh fails, always the message 'Error getting Business Partner Information' is raised although another entity has failed.

Steps To ReproduceSee a video in a customer's environment where the product module fails:

https://drive.google.com/file/d/1cHDCRrkaa3KKUP-YpY6Znud75zij7TaV/view?usp=sharing [^]
Proposed SolutionThe message should inform about the failed entity
Additional Information
TagsNOR
Relationships
duplicate of defect 0045192RR20Q2.2 closed prakashmurugesan88 cannot open pos for offline pos in remote client mode 
related to defect 0045188 closed ranjith_qualiantech_com Incremental Refresh fail: continues the load when it should stop 
related to defect 0045187 closed ranjith_qualiantech_com Full Refresh fail: continues the load when it should stop 
related to defect 0045834 closed ranjith_qualiantech_com When an incremental refresh fails, the field 'Channel - Touchpoint || Incremental Refresh Masterdata Load' is updated 
related to defect 0045852 closed ranjith_qualiantech_com Wrong behaviour when the browser is closed before Full Refresh finishes 
related to defect 0045879 closed ranjith_qualiantech_com Full refresh does not restar after F5 in all the cases 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2021-02-03 16:48avicenteNew Issue
2021-02-03 16:48avicenteAssigned To => Retail
2021-02-03 16:48avicenteResolution time => 1614726000
2021-02-03 16:48avicenteTriggers an Emergency Pack => No
2021-02-03 16:49avicenteTag Attached: NOR
2021-02-03 16:56rafarodaIssue Monitored: rafaroda
2021-02-03 16:56rafarodaRelationship addedrelated to 0045188
2021-02-03 16:56rafarodaResolution time1614726000 => 1613862000
2021-02-03 16:57rafarodaRelationship addedrelated to 0045187
2021-02-03 16:57rafarodaRelationship addedrelated to 0045834
2021-02-04 12:50rafarodaRelationship addedrelated to 0045852
2021-02-09 13:59ranjith_qualiantech_comAssigned ToRetail => ranjith_qualiantech_com
2021-02-10 14:46rafarodaRelationship addedrelated to 0045879
2021-02-11 09:56ranjith_qualiantech_comStatusnew => scheduled
2021-02-12 02:18ranjith_qualiantech_comRelationship addedrelated to 0045192
2021-02-12 07:58marvintmReview Assigned To => marvintm
2021-02-12 07:58marvintmRelationship replacedduplicate of 0045192
2021-02-12 07:58marvintmNote Added: 0126084
2021-02-12 07:58marvintmStatusscheduled => closed
2021-02-12 07:58marvintmResolutionopen => duplicate

Notes
(0126084)
marvintm   
2021-02-12 07:58   
Even though the description of the issue seems different, in the end the problem is the same. This problem was fixed in 21Q1, but it was also backported to affected releases up to 20Q3.2.