Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0034656Openbravo ERPA. Platformpublic2016-11-30 16:402022-02-01 08:09
NaroaIriarte 
Triage Platform Base 
highminoralways
acknowledgedopen 
5
 
 
Core
No
0034656: An error is shown in Chrome console after executing a process
After executing the "Add Payment" process of the "transaction" subtab of the "financial account" window, an error is shown in the Chrome consoles:

"Uncaught TypeError: Cannot read property '_handleSelect' of null"
1- Log in the ERP with the 'F&B Admin' role.
2- Go to the "Financial Account" window.
3- Select the record named "Cashbook US".
4- Go to the "transaction" subtab and create a new record:
  4.1- In the "Transaction Type" field choose "BP Withdrawal".
  4.2- In the "Payment" field, click on the "+" button.
  4.3- A pick and execute window will open.
  4.4- In the "Order/Invoice" section, clear the grid by clicking the funnel icon.
  4.5- Select the first record by clicking the checkbox.
  4.6- Click on the "Done" button.
5- Realize that the process has been successfully completed but in the Chrome console an error message appears: Uncaught TypeError: Cannot read property '_handleSelect' of null.
The problem is fixed in latest version of Smartclient to the fix is to update the Smartclient version.
 The changeset which fixes the issue is this:

https://code.openbravo.com/private/com.isomorphic.smartclient/rev/f8ed5d1ae88c?revcount=960#l180.94 [^]

The fix is the same that it is needed in this issue, (but there are different changesets):

https://issues.openbravo.com/view.php?id=33539 [^]

No tags attached.
related to design defect 0033539 acknowledged Triage Platform Base JS Errors after closing Add Payment window having the focus on the Order/Invoices grid 
depends on feature request 0034303 acknowledged Triage Platform Base The SmartClient version must be updated. 
related to defect 0030249 acknowledged Triage Platform Base An error is get in the chrome console when executing a Process Definition. 
Not all the children of this issue are yet resolved or closed.
Issue History
2016-11-30 16:40NaroaIriarteNew Issue
2016-11-30 16:40NaroaIriarteAssigned To => platform
2016-11-30 16:40NaroaIriarteModules => Core
2016-11-30 16:40NaroaIriarteTriggers an Emergency Pack => No
2016-12-01 12:27alostaleStatusnew => acknowledged
2016-12-01 14:03alostalePrioritynormal => high
2016-12-13 12:42NaroaIriarteAssigned Toplatform => NaroaIriarte
2016-12-13 12:52NaroaIriarteStatusacknowledged => scheduled
2016-12-15 14:54NaroaIriarteTypedefect => design defect
2016-12-15 14:54NaroaIriarteProposed Solution updated
2016-12-15 14:54NaroaIriarteRelationship addedrelated to 0033539
2016-12-15 14:55NaroaIriarteRelationship addeddepends on 0034303
2016-12-15 14:56NaroaIriarteStatusscheduled => acknowledged
2017-02-02 11:24NaroaIriarteRelationship addedrelated to 0030249
2017-03-14 17:06NaroaIriarteAssigned ToNaroaIriarte => platform
2022-02-01 08:09alostaleAssigned Toplatform => Triage Platform Base

There are no notes attached to this issue.