| Summary: | [Transactions][Bank Reconciliation] - Entered Amount values are not retained in Bank Statement Balance & Outstanding Not Entered Fields. | ||
|---|---|---|---|
| Product: | ML_DB 64-bit Mac | Reporter: | G.Shivasai <gshiva> |
| Component: | Bank Reconciliation | Assignee: | G.Shivasai <gshiva> |
| Status: | CLOSED --- | ||
| Severity: | Major | ||
| Priority: | High | ||
| Version: | 2026-14.0.22 + 26.0.1 Ver 04 | ||
| Hardware: | MAC | ||
| OS: | All | ||
|
Description
G.Shivasai
2026-04-30 15:15:14 IST
In Version 01 18215 bug sake we have fixed on the same fields which is logged in Version 01. now logging the bug in a different scenario on the same set off fields. Kindly verify more clearly. it is increasing the sensitivity of the code. In Both Scenarios - I have verified that First one is - Amount what ever entered that should update when selecting the "Get Transaction" Button and while doing tab also. Second One is - Entered amount should stay on the fields. Even closing and opening the BR Screen. However the logged issue is still exists in the current build. Fixed, Available in next build #REOPEN => Still the issue is exists in the replaced build version-03. FIRST SCENARIO IS WORKING FINE BUT SECOND SCENARIO, The Amounts which are entered are not retaining in the fields. after closing and opening the BR Screen. Screenshot: https://prnt.sc/mcQiDsXIoIda In last 21 patches it is like that only. we were expecting an action after entering the amount. Such a major flow, in version 02 you are logging. where in it is not a broken flow also. there were no show stoppers. why it has not been verified in Previous regressions. Now recurrently reopen as still issue exists. i have resolved the issue oly from outstanding value entering related issue i have resolved. That you have not verified. Fixed, Available in next build In Last 21 Patch there is no issue on this mam. When you fixed this bug 18215. This area is got effected and the entered values are not retaining in the fields. Still the issue is there on replaced build version-03. Fixed, Available in version 04. Please test Still the issue is exists in the version-04. Fixed, Available in next build Working fine as expected in the replaced build verison-04. |