Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Discounts and Promotionsmajoralways2020-09-28 16:002020-09-28 16:39
ReportercbrazierView Statuspublic 
Assigned ToRetail 
PriorityurgentResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Tomarvintm
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0045155: 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
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0044662 closedranjith_qualiantech_com Discounts are not updated on webpos after incremental refresh 
related to defect 0045153 closedranjith_qualiantech_com Discount and promotion - Disabling organizations are not sent to WebPOS 
related to defect 0045154 closedranjith_qualiantech_com Discount and promotion - Filter change are not sent to WebPOS 
related to defect 0045188 closedranjith_qualiantech_com Incremental Refresh fail: continues the load when it should stop 

-  Notes
rafaroda (developer)
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. " [^]
marvintm (developer)
2020-09-28 16:39

Unfortunately this is how the incremental refresh works: [^]

"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.

- Issue History
Date Modified Username Field Change
2020-09-28 16:00 cbrazier New Issue
2020-09-28 16:00 cbrazier Assigned To => Retail
2020-09-28 16:00 cbrazier Triggers an Emergency Pack => No
2020-09-28 16:17 rafaroda Tag Attached: NOR
2020-09-28 16:17 rafaroda Relationship added related to 0044662
2020-09-28 16:18 rafaroda Relationship added related to 0045153
2020-09-28 16:18 rafaroda Relationship added related to 0045154
2020-09-28 16:19 rafaroda Resolution time => 1602280800
2020-09-28 16:19 rafaroda Priority normal => urgent
2020-09-28 16:19 rafaroda Severity critical => major
2020-09-28 16:19 rafaroda Reproducibility have not tried => always
2020-09-28 16:28 rafaroda Note Added: 0123433
2020-09-28 16:39 marvintm Review Assigned To => marvintm
2020-09-28 16:39 marvintm Note Added: 0123434
2020-09-28 16:39 marvintm Status new => closed
2020-09-28 16:39 marvintm Resolution open => no change required
2020-10-05 11:41 rafaroda Relationship added related to 0045188

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker