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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0030163
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajoralways2015-06-12 09:032015-06-19 13:17
ReportermalsasuaView Statuspublic 
Assigned ToNaroaIriarte 
PrioritynormalResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabasePostgreSQLJava version1.6.0_18
OS VersionCommunity ApplianceDatabase version8.3.9Ant version1.7.1
Product VersionSCM revision 
Merge Request Status
Review Assigned Toalostale
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0030163: Error with property field and display logics

DescriptionIf one property field, that it references to one column of other table, is added to one tab, and it is included in a display logic of other field in the same tab, the window can not be opened, and error is returned
Steps To Reproduce(obx attached)
. go to window: windows tabs and field
 . record: goods shipment
 . go to tab: lines
 . add field:
   property: shipmentReceipt.documentNo
   show in grid: yes
   display logic: @DOCSTATUS@='DR'
 . add field:
   property: shipmentReceipt.documentStatus
   show in grid: yes

change rol to Openbravo Admin
go to window: goods shipment
error is returned:
 Error occured: freemarker.template.TemplateModelException: get(tabView) failed on instance of org.openbravo.client.application.window.StandardWindowComponent
TagsNo tags attached.
Attached Filestar file icon issueDisplayLogic.tar [^] (1,313 bytes) 2015-06-12 09:16

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0078395)
NaroaIriarte (viewer)
2015-06-19 13:14
edited on: 2015-06-19 13:16

This is not an issue, the thing is that if the display logic is referencing a property field, it has a concrete way of writing it that is:
"@inp_propertyField_FIELDNAME_COLUMNNAME@"

That was why this wasn't working.

It has to be:

@inp_propertyField_bb_DocStatus@='DR'

instead of:

@DOCSTATUS@='DR'


- Issue History
Date Modified Username Field Change
2015-06-12 09:03 malsasua New Issue
2015-06-12 09:03 malsasua Assigned To => platform
2015-06-12 09:03 malsasua OBNetwork customer => Yes
2015-06-12 09:03 malsasua Modules => Core
2015-06-12 09:03 malsasua Resolution time => 1436652000
2015-06-12 09:03 malsasua Triggers an Emergency Pack => No
2015-06-12 09:16 malsasua File Added: issueDisplayLogic.tar
2015-06-12 12:24 alostale Status new => scheduled
2015-06-12 12:24 alostale Assigned To platform => NaroaIriarte
2015-06-19 10:11 NaroaIriarte Issue Monitored: alostale
2015-06-19 10:11 NaroaIriarte Review Assigned To => alostale
2015-06-19 13:14 NaroaIriarte Note Added: 0078395
2015-06-19 13:16 NaroaIriarte Note Edited: 0078395 View Revisions
2015-06-19 13:17 NaroaIriarte Status scheduled => closed
2015-06-19 13:17 NaroaIriarte Resolution open => no change required


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker