Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0045155Retail ModulesDiscounts and Promotionspublic2020-09-28 16:002020-09-28 16:39
Reportercbrazier 
Assigned ToRetail 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customerGold
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0045155: Discount and promotion- Removing filters are not sent to WebPOS
DescriptionWhen removing filter such as characterics or products in a discount, related WebPOS IndexedDB tables are not updated.
Steps To Reproduce1/ Create a new promotion / discount
2/ Add product
3/ Run incremental refresh
4/ Remove product
5/ Run incremental refresh
Proposed Solution
Additional Information
TagsNOR
Relationships
related to defect 0044662 closed ranjith_qualiantech_com Discounts are not updated on webpos after incremental refresh 
related to defect 0045153 closed ranjith_qualiantech_com Discount and promotion - Disabling organizations are not sent to WebPOS 
related to defect 0045154 closed ranjith_qualiantech_com Discount and promotion - Filter change are not sent to WebPOS 
related to defect 0045188 closed ranjith_qualiantech_com Incremental Refresh fail: continues the load when it should stop 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2020-09-28 16:00cbrazierNew Issue
2020-09-28 16:00cbrazierAssigned To => Retail
2020-09-28 16:00cbrazierTriggers an Emergency Pack => No
2020-09-28 16:17rafarodaTag Attached: NOR
2020-09-28 16:17rafarodaRelationship addedrelated to 0044662
2020-09-28 16:18rafarodaRelationship addedrelated to 0045153
2020-09-28 16:18rafarodaRelationship addedrelated to 0045154
2020-09-28 16:19rafarodaOBNetwork customer => Gold
2020-09-28 16:19rafarodaResolution time => 1602280800
2020-09-28 16:19rafarodaPrioritynormal => urgent
2020-09-28 16:19rafarodaSeveritycritical => major
2020-09-28 16:19rafarodaReproducibilityhave not tried => always
2020-09-28 16:28rafarodaNote Added: 0123433
2020-09-28 16:39marvintmReview Assigned To => marvintm
2020-09-28 16:39marvintmNote Added: 0123434
2020-09-28 16:39marvintmStatusnew => closed
2020-09-28 16:39marvintmResolutionopen => no change required
2020-10-05 11:41rafarodaRelationship addedrelated to 0045188

Notes
(0123433)
rafaroda   
2020-09-28 16:28   
As per Antonio, this is the expected behavior "This mode has a specific limitation: it is not able to detect data removals, due to using the updated column to check which records changed. " http://wiki.openbravo.com/wiki/Retail:MasterdataLoading#Technical_implementation_of_masterdata_loading [^]
(0123434)
marvintm   
2020-09-28 16:39   
Unfortunately this is how the incremental refresh works:

http://wiki.openbravo.com/wiki/Retail:MasterdataLoading#Technical_implementation_of_masterdata_loading [^]

"This mode has a specific limitation: it is not able to detect data removals, due to using the updated column to check which records changed. "

Incremental refresh works by finding records which were updated after the last refresh for the terminal. If the record is deleted, then the system is unable to find it, so the terminal will not realise this. The right way to work when using incremental refresh is to disable the masterdata records instead, so that the incremental refresh can detect them, and remove them from the terminal database.