Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0034778 | Openbravo ERP | 09. Financial management | public | 2016-12-20 10:46 | 2017-01-10 12:37 |
|
Reporter | shuehner | |
Assigned To | alekosmp86 | |
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | scheduled | Resolution | open | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0034778: Error in tab definition for Financial Account -> Accounting tab: "a column and an auxiliary input have the same name" |
Description | Opening that tab in form view shows an error message in openbravo.log file
2016-12-20 10:42:42,680 [ajp-bio-127.0.0.1-8009-exec-27] ERROR org.openbravo.client.application.window.FormInitializationComponent - Error: a column and an auxiliary input have the same name in ADTab(FF80808130BB89090130BB9A3A2B0043) (name: Accounting, window: 94EAA455D2644E04AB25D93BE5157B6D). This will lead to wrong computation of values for that column. |
Steps To Reproduce | Go to Financial Account window and select a row
Go to the Accounting child tab and open it in form view
Check openbravo.log for the error message |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | feature request | 0034779 | | new | Triage Platform Base | FIC check for "a column and an auxiliary input have the same name" could probably be done at compile time |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2016-12-20 10:46 | shuehner | New Issue | |
2016-12-20 10:46 | shuehner | Assigned To | => Triage Finance |
2016-12-20 10:46 | shuehner | Modules | => Core |
2016-12-20 10:46 | shuehner | Triggers an Emergency Pack | => No |
2016-12-20 11:04 | shuehner | Relationship added | related to 0034779 |
2016-12-20 17:06 | markmm82 | Assigned To | Triage Finance => collazoandy4 |
2016-12-26 16:38 | markmm82 | Assigned To | collazoandy4 => alekosmp86 |
2016-12-26 16:49 | alekosmp86 | Status | new => scheduled |
2016-12-26 21:06 | alekosmp86 | Note Added: 0092998 | |
2016-12-26 21:06 | alekosmp86 | Note Edited: 0092998 | bug_revision_view_page.php?bugnote_id=0092998#r14126 |
2017-01-03 15:09 | psanjuan | Note Added: 0093135 | |
2017-01-10 12:37 | aferraz | Note Added: 0093305 | |
Notes |
|
(0092998)
|
alekosmp86
|
2016-12-26 21:06
|
|
Test Plan
Log in as F&B International Group Admin
Go to Financial Account screen
Select "Cuenta de Banco" financial account
Go to Accounting tab
Select any record and open it in form view
In Eclipse IDE, or openbravo.log file, notice there's no error.
|
|
|
|
|
|
|
DOCBASETYPE auxiliary inputs are used for Accounting Dimensions configuration (DimensionDisplayUtility.java).
Every DOCBASETYPE auxiliary input should be renamed to avoid having the same name as DocBaseType column (as it happens in Financial Account | Accounting tab).
Anyway, these auxiliary inputs could be used in any other place and in case we rename them, we could introduce a regression. I think it is not worth to do this risky change just to avoid an error in the log. |
|