Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007964Openbravo ERPB. User interfacepublic2009-03-05 10:372022-02-01 08:08
Reporteralostale 
Assigned ToTriage Platform Base 
PriorityhighSeverityminorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOS5OS Version
Product Versionpi 
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
Summary0007964: Checkboxes do not take "N" value util they are saved
DescriptionWhen a checkbox is changed and it is used for dynamic checks without saving the record (for example in a validation) it works as expected when it is checked but not when it is unchecked.

Further information about the problem in 0007923

Steps To ReproduceThe same ones as 0007923
Proposed SolutionThis seems to be a HTML limitation: checkboxes are defined as <input type="checkbox" value="Y">, this means that it takes "Y" when it is checked but blank when it is not.

But it would be nice if there was a way to set "N" when it is not checked.
Additional Information
Tags250MP1
Relationships
related to defect 00079232.40 closed alostale Error applaying validation on c_tax_id field from Invoice line tab in Purchase Invoice window 
related to defect 0010015pi closed alostale Read only logic does not work with Business Partner fields 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-03-05 10:37alostaleNew Issue
2009-03-05 10:37alostaleAssigned To => rafaroda
2009-03-05 10:37alostaleRegression testing => No
2009-03-05 10:43alostaleRelationship addedrelated to 0007923
2009-03-05 10:51rafarodaAssigned Torafaroda => dbaz
2009-03-05 10:51rafarodaPrioritynormal => high
2009-03-05 10:51rafarodaStatusnew => acknowledged
2009-04-21 19:22dbazAssigned Todbaz => alostale
2009-04-22 13:29alostaleNote Added: 0015529
2009-04-22 13:29alostaleAssigned Toalostale => rafaroda
2009-04-22 16:00rafarodaNote Added: 0015543
2009-04-22 16:01rafarodaNote Added: 0015544
2009-04-23 16:04psarobeTag Attached: 250MP1
2009-06-01 12:16rafarodaAssigned Torafaroda => alostale
2009-08-31 14:32rafarodaRelationship addedrelated to 0010015
2009-10-06 09:01alostaleTypedefect => feature request
2017-04-10 14:39alostaleAssigned Toalostale => platform
2022-02-01 08:08alostaleAssigned Toplatform => Triage Platform Base

Notes
(0015529)
alostale   
2009-04-22 13:29   
As this is a HTML limitation it is not going to be fixed. It will be documented as a known issue in developers guide explaining the proposed workaround for 0007923.

For core we must ensure all display logic is using this workaround in case in the display logic participates a check box.
(0015543)
rafaroda   
2009-04-22 16:00   
For display logic:
SELECT w.name as window, t.name as tab, f.name as field, f.displaylogic
FROM ad_window w, ad_tab t, ad_field f
WHERE w.ad_window_id = t.ad_window_id
AND t.ad_tab_id = f.ad_tab_id
AND f.displaylogic IS NOT NULL
AND f.displaylogic like '%''N''%'
AND f.displaylogic like '%Is%'
(0015544)
rafaroda   
2009-04-22 16:01   
For validations:
SELECT ad_val_rule_id, name, code
FROM ad_val_rule
WHERE (code like '%@=%'
OR code like '%@ =%')