Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009228Openbravo ERP00. Application dictionarypublic2009-05-28 18:322009-05-30 00:00
Reporternetworkb 
Assigned Toalostale 
PriorityimmediateSeverityminorReproducibilityalways
StatusclosedResolutionsuspended 
PlatformOS30OS Version
Product Version2.40MP3 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0009228: The wherecluase of the tab does not allow to use expressions as @#Ad_Role_ID@ <> 100012
DescriptionThe wherecluase of the tab does not allow to use expressions as @#Ad_Role_ID@ <> 100012. If you use the expression with other order, it works. example:
   100012 <> @#Ad_Role_ID@
Steps To Reproduce-Loggin as system administrator
-Go to windows tabs and fields window.
-Edit a tab of a window
-Add in the where clause field the following:
  @#Ad_Role_ID@ <> 100012
-Save and compile the window
-You get the following error
       [java] 71923 [main] INFO org.openbravo.wad.Wad - Processing Window: Business Partner - Tab: Vendor/Creditor - id: 224
     [java] java.lang.StringIndexOutOfBoundsException: String index out of range: -1
     [java] at java.lang.String.substring(String.java:1932)
     [java] at java.lang.String.substring(String.java:1905)
     [java] 72085 [main] ERROR org.openbravo.wad.Wad - Problem at close of the file: 224
     [java] at org.openbravo.wad.WadUtility.getSQLWadContext(Unknown Source)
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0009178 closed dbaz Tab keys are not properly set for fields unit price & List price in Sales Order || Lines page after the product is selected. 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-05-28 18:32networkbNew Issue
2009-05-28 18:32networkbAssigned To => rafaroda
2009-05-29 08:52rafarodaNote Added: 0016745
2009-05-29 08:52rafarodaAssigned Torafaroda => alostale
2009-05-29 16:06alostaleStatusnew => closed
2009-05-29 16:06alostaleNote Added: 0016769
2009-05-29 16:06alostaleResolutionopen => suspended
2009-05-30 00:00anonymoussf_bug_id0 => 2798626
2009-06-02 22:10dbazRelationship addedrelated to 0009178

Notes
(0016745)
rafaroda   
2009-05-29 08:52   
Asier,

Could you please comment on this issue and schedule it for 2.40 if required?

Thanks.
(0016769)
alostale   
2009-05-29 16:06   
I wouldn't fix this issue because:

1. It has a very simple workarround, just change the order of the parameter in the clause.
2. It is a very unusual case. Generally session variables are not compared with constant arguments but with columns in the tab.
3. It might add instability. This fix requires some modifications in a piece deep in WAD, which might add new instability.

If after reading the reasons to reject this issue you still think it should be fixed, please reopen it.