Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0005287Openbravo ERPB. User interfacepublic2008-09-26 23:012008-11-17 06:53
Reportergalderromo 
Assigned Topjuvara 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionduplicate 
PlatformOS20OS VersionGentoo 2.6.24
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0005287: Case sensitive parametrization option for fields
DescriptionUsers should be able to specify whether a particular field is case sensitive or insensitive for searches.
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
duplicate of feature request 0004205 acknowledged rmorley Searching criteria > Case sensitive searchs 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-09-26 23:01galderromoNew Issue
2008-09-26 23:01galderromoAssigned To => cromero
2008-09-26 23:01galderromosf_bug_id0 => 2130994
2008-10-12 19:40pjuvaraNote Added: 0009525
2008-10-12 19:40pjuvaraStatusnew => feedback
2008-10-20 23:12galderromoNote Added: 0009662
2008-10-26 20:10pjuvaraAssigned Tocromero => pjuvara
2008-10-26 20:10pjuvaraStatusfeedback => new
2008-10-26 20:12pjuvaraOBNetwork customer => No
2008-10-26 20:12pjuvaraNote Added: 0009750
2008-10-26 20:12pjuvaraSummaryCase sensitive parametrization option for fieleds => Case sensitive parametrization option for fields
2008-10-26 20:12pjuvaraDescription Updated
2008-10-26 20:12pjuvaraStatusnew => acknowledged
2008-10-26 20:15pjuvaraTag Attached: ReleaseCandidate
2008-11-17 06:53pjuvaraStatusacknowledged => scheduled
2008-11-17 06:53pjuvarafix_in_branch => trunk
2008-11-17 06:53pjuvaraRegression testing => No
2008-11-17 06:53pjuvaraRelationship addedduplicate of 0004205
2008-11-17 06:53pjuvaraStatusscheduled => closed
2008-11-17 06:53pjuvaraDuplicate ID0 => 4205
2008-11-17 06:53pjuvaraResolutionopen => duplicate
2008-11-17 06:53pjuvaraTag Detached: ReleaseCandidate

Notes
(0009525)
pjuvara   
2008-10-12 19:40   
Please provide a more complete explanation of the desired behavior. Please do not express it in terms of code as in 5054 but in functional terms (what do you want users to be able to do).

Please also provide a justification of why this is important.

Personally I do not see the benefit (if anything I would think that this is NOT a desired behavior for search keys and document numbers) so it is important that you explain your rationale for this request.

Thanks.
(0009662)
galderromo   
2008-10-20 23:12   
On one hand, some users define case sensitive identifiers on their product catalogue. For example: ACT01C, ACT01c, ACT02C, ACT02c, etc. This is way it is important for this user to use case sensitive searching.

On the other hand, some users do not pay attention on identifiers case, so the define: BER01, Ber02, BER03, ber04, etc. And when they want to search for a particular record starting with BER% only 2 record are showed, ber% only one record is showed, etc. Applying case sensitive to searches is annoying.

Takinto into account the previous example, the feature request is based on having the option to make a field or a column case sensitive, or not, throught the application dictonary (for generated windows) and also for manual windows.

Is this explanation enough? Do I have explaine my self clearly?
(0009750)
pjuvara   
2008-10-26 20:12   
Original description:

Be able to setup case sensitive functionality for each field.

Related with issue 0005054