Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0014126Openbravo ERP01. General setuppublic2010-08-05 10:332010-08-10 00:00
networkb 
iciordia 
immediatemajoralways
closedno change required 
5
2.50MP20 
2.50MP21 
Core
No
0014126: A squence created for the value field of the partner is not applied automatically
A squence created for the value field of the partner is not applied automatically, when the column 'Value' is not mandatory
- As System Administrator go to Application Dictionary || Tables and Columns
- Go to Business Partner table
- Select the column: Value
- Uncheck 'Mandatory'

- Compile the application (ant smartbuild)
- Restart Tomcat

- As Openbravo Admin go to Financial Management || Accounting || Setup || Document Sequence
- Realize that there is a sequence to DocumentNo/Value for C_Bpartner
- Go to Financial Management || Accounting || Setup || Document Type
- Create a new recrod:
    - G/L category: None
    - Document Category: **New**
    - Table: C_BPartner
    - Document Sequence: DocumentNo_C_BPartner
    - check Sequenced Document
- Go to Master Data Management || Business Partner
- Create a new record.
- Realize that the field 'Search Key' is empty
No tags attached.
related to feature request 0004416 scheduled iciordia Autogenerate Search Key values 
Issue History
2010-08-05 10:33networkbNew Issue
2010-08-05 10:33networkbAssigned To => adrianromero
2010-08-05 10:39networkbDescription Updatedbug_revision_view_page.php?rev_id=648#r648
2010-08-05 10:39networkbSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=650#r650
2010-08-09 11:34psarobeRelationship addedrelated to 0004416
2010-08-09 16:39iciordiaAssigned Toadrianromero => iciordia
2010-08-09 16:49iciordiaNote Added: 0029852
2010-08-09 16:49iciordiaStatusnew => closed
2010-08-09 16:49iciordiaResolutionopen => no change required
2010-08-10 00:00anonymoussf_bug_id0 => 3042144

Notes
(0029852)
iciordia   
2010-08-09 16:49   
Summary of rationale to reject this issue:
-since openbravo 2.35 (more than 3 years ago) columns of type Search Key (Value) behave in a standard manner without using the sequence created to autogenerate values
-some months ago we reviewed this behaviour and agreed on keeping it as it is to avoid changing the behaviour of current stable instances
-the proper way to solve this issue would be add a new configuration option so you can decide if Search Key columns (and any other) are automatically filled with sequence generators. This way it would not create any disruption, the new behaviour only happens if you configure your instance to do so)
-this feature is not planned in the short term roadmap. It would be possible to push this feature through collaborative development
-as a work-around you can implement yourself the behaviour using a callout or a trigger