Project:
| View Revisions: Issue #40078 | [ Back to Issue ] | ||
| Summary | 0040078: If a new column is added to PaymentMethodCashup the data is inconsistent on WebPOS | ||
| Revision | 2019-01-31 06:53 by guillermogil | ||
| Steps To Reproduce | With Sessions module intalled Login on WebPOS Do a CashUp Truncate PaymentMethodCashup table Login again You will notice that startingCash amount is wrong |
||
| Revision | 2019-01-31 06:53 by guillermogil | ||
| Description | If a new column is added to PaymentMethodCashup the data is inconsistent on WebPOS. Once logged in, PaymentMethodCashup table was cleaned from WebSQL but not CashUp table. WebPOS pick the values from the processed cashup in WebSQL but since there was no information on PaymentMethodCashup it tried to regenerate it but the startingCash was set to the current Balance of the Financial Account. |
||
| Revision | 2019-01-31 06:48 by guillermogil | ||
| Steps To Reproduce | N/A | ||
| Revision | 2019-01-31 06:48 by guillermogil | ||
| Description | If a new column is added to PaymentMethodCashup the data is inconsistent on WebPOS. For example, in issue 38193 a new column was added. Once logged in PaymentMethodCashup table was removed from the tills but no CashUp table. WebPOS pick the values from the processed cashup in WebSQL but since there was no information on PaymentMethodCashup it tried to regenerate it but the startingCash was set to the current Balance of the Financial Account. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |