Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] 00. Application dictionarymajoralways2009-05-20 08:332009-05-22 19:26
ReporteralostaleView Statuspublic 
Assigned Toiciordia 
PrioritynoneResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0009098: Read Only Logic does not work if the clausure does not include a column from the table

DescriptionRead only logic only works when the values included within it are columns for the same table than the field that affect it.

It would be necessary to add the capability of adding session values too.

For example a read only logic does not work if the clause is like:


The javascript function created is:

function readOnlyLogic() {
  readOnlyLogicElement('ColumnName', (strAD_User_ID != 1000000));
  return true;

It seems that a field called strAD_User_ID should be a column from the table.
This column does not exist in the table so, the Read Only Logic does not work

It exists a workaround:

Create an Auxiliary input like:


In Read Only logic use:

Steps To ReproduceGo to Application Dictionary > Tables and Columns > C_BPartner.

Search column: name.

In Read Only Logic add: @#AD_User_ID@!1000000

Compile the window.

Login the application using an user <> 1000000
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0009083 closedalostale Read Only Logic does not work if the clausure does not include a column from the table 

-  Notes
iciordia (manager)
2009-05-22 09:55


I assign this feature request to you till you move all platform feature requests back to me (as a reminder :-)


- Issue History
Date Modified Username Field Change
2009-05-20 08:33 alostale New Issue
2009-05-20 08:33 alostale Assigned To => pjuvara
2009-05-20 08:33 alostale Regression testing => No
2009-05-20 08:33 alostale Issue generated from 0009083
2009-05-20 08:33 alostale Relationship added related to 0009083
2009-05-21 22:34 pjuvara Assigned To pjuvara => iciordia
2009-05-22 09:55 iciordia Assigned To iciordia => pjuvara
2009-05-22 09:55 iciordia Note Added: 0016570
2009-05-22 19:26 pjuvara Assigned To pjuvara => iciordia

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker