Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0004434Openbravo ERPA. Platformpublic2008-07-17 14:582009-05-22 19:34
galderromo 
iciordia 
normalminoralways
acknowledgedopen 
20Gentoo 2.6.24
2.40beta 
 
Core
No
0004434: Uneditable fields souldn't be list (drop)
Having an uneditable field means can't be changed. So does not make sense being a value list (tabledir, list, etc.).
This issue is very important when you have a huge amount of data, because the application slows down and the performance is not acceptable.
For example,
Supposing you have 20.000 business partners on you C_BPARTNER table.
Go to Business partner window, bank account tab, and check how long it takes to load the business partner uneditable list.
Change all uneditable list to search for business partners, products, accounts, projects, etc. For the rest of the cases, find a suitable solution.

Take into account, that an uneditable search field just loads and shoes one record.
Performance, ReleaseCandidate, ToBeReviewed
Issue History
2008-07-17 14:58galderromoNew Issue
2008-07-17 14:58galderromoAssigned To => cromero
2008-07-17 14:58galderromosf_bug_id0 => 2020579
2008-07-17 15:09galderromoNote Added: 0008326
2008-07-22 09:27cromeroNote Added: 0008354
2008-07-22 09:27cromeroTypedefect => feature request
2008-11-10 13:10cromeroAssigned Tocromero => pjuvara
2008-11-16 15:27pjuvaraTag Attached: ReleaseCandidate
2008-11-16 15:28pjuvaraStatusnew => acknowledged
2008-11-16 15:28pjuvaraProjectionnone => @40@
2008-11-16 15:28pjuvaraCategoryI. Performance => A. Platform
2008-11-16 15:28pjuvaraTag Attached: ToBeReviewed
2008-11-16 15:29pjuvaraTag Attached: Performance
2009-05-22 19:34pjuvaraAssigned Topjuvara => iciordia

Notes
(0008326)
galderromo   
2008-07-17 15:09   
Also appends on the dictionary:
Go to:
- WINDOW: Windows, tabs and fields.
- TAB: Tabs
- TAB: Fields
- TAB: Field translation.
- Being AD_FIELD_ID uneditable the application loads all the data on table AD_FIELD.
(0008354)
cromero   
2008-07-22 09:27   
There are some problems related to this issue that should be take into account and that is why I prefer change this issue to 'Feature request':
* Read only logic: now you can have fields that depending on the values of the fields in the page can be readonly or not.
* Callouts: it is normal that fields that are readonly and can not be modified by the user can be modified via callouts. So, this issue should also modify all the callouts in order to read and set the proper value.