Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0008160
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] 00. Application dictionaryminorhave not tried2009-03-17 16:452012-07-29 13:52
ReporterAinhoaPagolaView Statuspublic 
Assigned Tomtaal 
PrioritynormalResolutionfixedFixed in Version3.0MP13
StatusclosedFix in branchpiFixed in SCM revision3.0MP13
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0008160: Display of read-only fields that are not columns of the table liked to the tab.

DescriptionFor every field shown in a tab there must be a column associated to it in the table linked to the tab. That is, every field displayd is a column of the table.

There is no chance to show fields, on read-only mode, that are not in the table itself, such as calculated fields, or fields from other table that could provide useful information.

For instance, if there is a field for the birth date, it could be nice to show a calculated field age. Nowadays to show this field it must be kept as a column, but it makes no sense.

My suggestion is to make it possible somehow to add read-only fields to the tab that do not belong to the table under it, but are calculated with a query.
Proposed SolutionAn idea could be to provide the possibility of making auxiliary inputs visible somehow in the tab. On read-only mode.
TagsReleaseCandidate
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0014742)
pmagnin (reporter)
2009-03-17 19:48

I would like to emphasize the importance to be able to show two tables in the same page. This strong limitation forces developers to duplicate the information in order to use only on table and impose a strong limitation in term of design and user experience.

The direct consequence of the ability to have many table in the same page will be the Master-Detail project.
(0050970)
dmitry_mezentsev (developer)
2012-07-29 13:33

http://wiki.openbravo.com/wiki/Release_Notes/3.0MP13, [^] Computed fields III.
(0050971)
dmitry_mezentsev (developer)
2012-07-29 13:52

http://wiki.openbravo.com/wiki/Release_Notes/3.0MP13, [^] Computed fields III.

- Issue History
Date Modified Username Field Change
2009-03-17 16:45 AinhoaPagola New Issue
2009-03-17 16:45 AinhoaPagola Assigned To => pjuvara
2009-03-17 16:45 AinhoaPagola Regression testing => No
2009-03-17 19:48 pmagnin Note Added: 0014742
2009-03-20 12:18 pjuvara Tag Attached: ReleaseCandidate
2009-03-20 12:18 pjuvara Status new => acknowledged
2009-05-22 19:26 pjuvara Assigned To pjuvara => iciordia
2012-07-29 13:33 dmitry_mezentsev Status acknowledged => scheduled
2012-07-29 13:33 dmitry_mezentsev Assigned To iciordia => mtaal
2012-07-29 13:33 dmitry_mezentsev fix_in_branch => pi
2012-07-29 13:33 dmitry_mezentsev Note Added: 0050970
2012-07-29 13:33 dmitry_mezentsev Status scheduled => resolved
2012-07-29 13:33 dmitry_mezentsev Fixed in Version => 3.0MP13
2012-07-29 13:33 dmitry_mezentsev Fixed in SCM revision => 3.0MP13
2012-07-29 13:33 dmitry_mezentsev Resolution open => fixed
2012-07-29 13:34 dmitry_mezentsev Status resolved => closed
2012-07-29 13:52 dmitry_mezentsev Note Added: 0050971


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker