Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012051Openbravo ERP00. Application dictionarypublic2010-01-23 11:262010-02-10 11:43
ReporterNeha Mathur 
Assigned Todbaz 
PriorityurgentSeveritycriticalReproducibilityalways
StatusclosedResolutionduplicate 
PlatformOS10OS VersionXP Professional - SP2
Product Version2.50 
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
Summary0012051: Read only logic fails on combo if a callout is associated with it.
DescriptionWhen a read only logic is applied on a field (or updatable field is false) and there is a callout is associated with it ;then on changing the value from the combo box the callout associated with it is triggered automatically.But since the field is read only , the callout for it should not be triggered.
Since the callout runs for the readonly logic , our purpose is not solved.
 
Steps To Reproduce1. add a read only logic to a field
2. make a relevant call out for that field
3. associate the callout with that field.
4. now compile
5. try to change the combo box's value which was set read only (or updatable false)
6. the callout associated with it is triggered which fails the logic for setting a readonly logic.
Proposed SolutionWhen read only logic works the callout behind that field should be disabled automatically.
Additional Information
TagsNo tags attached.
Relationships
duplicate of defect 0012052 closed dbaz Read only logic doesn't disable combo's onChange 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-01-23 11:26Neha MathurNew Issue
2010-01-23 11:26Neha MathurAssigned To => alostale
2010-01-24 18:58iciordiaAssigned Toalostale => dbaz
2010-01-24 18:58iciordiaPrioritynormal => urgent
2010-01-24 18:58iciordiaStatusnew => acknowledged
2010-01-24 18:58iciordiaStatusacknowledged => scheduled
2010-01-24 18:58iciordiafix_in_branch => pi
2010-01-25 11:18dbazRelationship addedhas duplicate 0012052
2010-01-25 11:18dbazNote Added: 0023788
2010-01-25 11:19dbazFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/23ac7482985604c75216c6c4f8572769cfce2ca0 [^]
2010-01-25 11:19dbazfix_in_branchpi =>
2010-01-25 11:20dbazRelationship replacedduplicate of 0012052
2010-01-25 11:20dbazStatusscheduled => closed
2010-01-25 11:20dbazDuplicate ID0 => 12052
2010-01-25 11:20dbazResolutionopen => duplicate
2010-01-26 00:00anonymoussf_bug_id0 => 2939798
2010-02-10 11:43Neha MathurNote Added: 0024089

Notes
(0023788)
dbaz   
2010-01-25 11:18   
Repository: erp/devel/pi
Changeset: 23ac7482985604c75216c6c4f8572769cfce2ca0
Author: David Baz Fayos <david.baz <at> openbravo.com>
Date: Sun Jan 24 22:35:41 2010 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/23ac7482985604c75216c6c4f8572769cfce2ca0 [^]

Fixed issue 12052: Combos with ReadOnlyLogic now don't fire onchange when readonly

---
M src/org/openbravo/erpCommon/security/Login_F1.html
M web/js/utils.js
---
(0024089)
Neha Mathur   
2010-02-10 11:43   
You have considered the issue, as resolved, but we have confirmed at our end that even after replacing the JS (as suggested in the solution), the callout is still triggered.

The fix may work on fields that are permanently marked as read only but it does not work on fields with columns on which Read Only LOGIC is applied.

Following are the steps to reproduce the error / problem:

Associate a callout and apply read only logic on the same column (having TableDir or Table as refernce); during run time, when the condition is satisfied to make the column read only, the field is shown as disabled, BUT the callout still gets triggered which defeats the purpose of making the column read only.

Please get the issue resolved ASAP, since this is one of the major hurdle and is defeating the logic being used to maintain the data integrity.