Openbravo Issue Tracking System - Retail Modules
View Issue Details
0039199Retail ModulesWeb POSpublic2018-08-30 08:592018-08-30 10:21
umartirena 
Retail 
immediatemajoralways
closedinvalid 
5
 
RR18Q3.2 
marvintm
Production - QA Approved
2018-04-23
RR18Q3
https://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/819ac4a1f0fc [^]
No
0039199: "Get Product Tax Category impementation" preference wrong configuration makes not possible to add products in Web POS
If "Get Product Tax Category impementation" preference is configured as "N" and no module is installed to implement Multi Tax Category it will not be possible to add any product in Web POS. "Cannot calculate receipt taxes" error popup appears and the products are not added.
In https://livebuilds.openbravo.com/retail_pi_pgsql [^] configure "Get Product Tax Category impementation" as value "N" for client white valley.

Login in https://livebuilds.openbravo.com/retail_pi_pgsql/web/org.openbravo.retail.posterminal/?terminal=VBS-1. [^]
Try to add any product to a ticket.
Check an error popup is displayed with message "Cannot calculate receipt taxes" and the product is not added
No tags attached.
blocks defect 0039197 closed marvintm "Get Product Tax Category impementation" preference wrong configuration makes not possible to add products in Web POS 
Issue History
2018-08-30 09:53marvintmTypedefect => backport
2018-08-30 09:53marvintmTarget Version => RR18Q3.2
2018-08-30 10:21marvintmReview Assigned To => marvintm
2018-08-30 10:21marvintmNote Added: 0106532
2018-08-30 10:21marvintmStatusscheduled => closed
2018-08-30 10:21marvintmResolutionopen => invalid
2018-08-30 10:28marvintmNote Edited: 0106532bug_revision_view_page.php?bugnote_id=0106532#r17582

Notes
(0106532)
marvintm   
2018-08-30 10:21   
(edited on: 2018-08-30 10:28)
Backport finally cannot be done because part of the fix involves changing an external module. There is a very simple workaround for anybody affected which is to just remove the preference "Get Product Tax Category impementation" and then the masterdata query will work correctly.