0046711: Incremental refresh not updating business partner multiple price list

Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #46711		[ Back to Issue ]
Summary	0046711: Incremental refresh not updating business partner multiple price list

Revision	2021-05-25 11:03 by santi_lozano
Steps To Reproduce	* Download a tip instance locally and install retail and retail sampledata (I have used a QAA version because I wasn't able to install sampledata on tip and build correctly) * as System Admin on Windows Tabs and Fields, for window Price List then for tab Product Price allow the field Active to be shown (not shown there by default), compile the application to apply the change (it would be necessary to set core in development in order to do this) * access as System Admin. Go to window Preference. Set this preferences to be "Web POS Enable Multi Price List" and "Web POS Show Standard Price on Search and Browse" with value = Y, and selected = yes * access as White Valley Group Admin, go to Price List window, select CTS - Price List, on tab Product Price add a new price of 500 for product Alpine Poles * go to Business Partner tab, select Arturo Montoro, on its tab change its price list to be CTS - Price List * go to the webpos * search for the product Alpine Pole with anonymous customer, it is 36.50 * change customer to be Arturo Montoro, search for the product Alpine Pole its price shows the custom 500 * remove filters there * go to backoffice, on window Price List, set the Alpine Pole entry that we have just created to be inactive * on webpos do an incremental refresh, now search for the Alpine Pole product again, it still shows the 500 price, this should have been updated with the refresh

Revision	2021-05-25 11:03 by santi_lozano
Description	Set preferences to have multiple price list functionality, set a new value for a product on a price list different of the used one in webpos, assign this price list to a customer, check this customer has a custom price for this product on webpos, set not active this custom price on backoffice, do an incremental refresh on webpos, check on webpos that the price is still custom (when it should have disappeared). This can lead to incorrect prices in webpos.

Revision	2021-05-25 10:57 by santi_lozano
Steps To Reproduce	* go to livebuilds retail tip instance. Credentials: Openbravo / openbravo https://livebuilds.openbravo.com/retail_pi_pgsql [^] * access as System Admin. Go to window Preference. Set this preferences to be "Web POS Enable Multi Price List" and "Web POS Show Standard Price on Search and Browse" with value = Y, and selected = yes * access as White Valley Group Admin, go to Price List window, select CTS - Price List, on tab Product Price add a new price of 500 for product Alpine Poles * go to Business Partner tab, select Arturo Montoro, on its tab change its price list to be CTS - Price List * go to the webpos, access with credentials vallblanca / openbravo https://livebuilds.openbravo.com/retail_pi_pgsql/web/org.openbravo.retail.posterminal/?terminal=VBS-1 [^] * search for the product Alpine Pole with anonymous customer, it is 36.50 * change customer to be Arturo Montoro, search for the product Alpine Pole its price shows the custom 500 * remove filters there * go to backoffice, on window Price List, remove the Alpine Pole entry that we have just created * on webpos do an incremental refresh, now search for the Alpine Pole product again, it still shows the 500 price, this should have been updated with the refresh * attached the terminal log (reproduced on tip and on qaa, also with setting the product inactive)

Revision	2021-05-25 10:57 by santi_lozano
Description	Set preferences to have multiple price list functionality, set a new value for a product on a price list different of the used one in webpos, assign this price list to a customer, check this customer has a custom price for this product on webpos, delete this custom price on backoffice, do an incremental refresh on webpos, check on webpos that the price is still custom (when it should have disappeared). This can lead to incorrect prices in webpos.