Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0025695 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| design defect | [Openbravo ERP] A. Platform | major | always | 2014-02-10 12:39 | 2023-07-04 12:33 | |||||||
| Reporter | jecharri | View Status | public | |||||||||
| Assigned To | Triage Platform Base | |||||||||||
| Priority | urgent | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| Review Assigned To | ||||||||||||
| Web browser | Google Chrome | |||||||||||
| Modules | Core | |||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0025695: Impossible to set a default value in tab customer | |||||||||||
| Description | Impossible to set a default value in tab customer | |||||||||||
| Steps To Reproduce | -set default values for fields "payment method, payment terms and price list" -go to ERP and create a BP Verify that columns are not filled with default values | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0064987) AugustoMauch (administrator) 2014-03-10 15:26 |
This issue has been changed to Design Defect because to fix this, the FIC should have to compute the default values of all the columns of the tab, even if there is not field associated in that table. This would have a performance impact in all Openbravo tabs, when the only tabs affected by this issue are those who has the same table as its parent tab. There is an easy workaround: to define in the parent tab the fields that need to have a default value in the child tab. Those fields can have Displayed = false and Show in Grid = false in the header tab. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2014-02-10 12:39 | jecharri | New Issue | |
| 2014-02-10 12:39 | jecharri | Assigned To | => AugustoMauch |
| 2014-02-10 12:39 | jecharri | Web browser | => Google Chrome |
| 2014-02-10 12:39 | jecharri | Modules | => Core |
| 2014-02-10 12:39 | jecharri | Resolution time | => 1394838000 |
| 2014-02-10 12:39 | jecharri | Triggers an Emergency Pack | => No |
| 2014-03-10 15:11 | AugustoMauch | Web browser | Google Chrome => Google Chrome |
| 2014-03-10 15:11 | AugustoMauch | Type | defect => design defect |
| 2014-03-10 15:11 | AugustoMauch | Target Version | PR14Q2 => |
| 2014-03-10 15:26 | AugustoMauch | Note Added: 0064987 | |
| 2016-08-04 09:03 | caristu | Relationship added | has duplicate 0030467 |
| 2016-08-04 09:03 | caristu | Assigned To | AugustoMauch => platform |
| 2016-08-04 09:06 | ngarcia | Issue Monitored: ngarcia | |
| 2022-02-01 08:07 | alostale | Assigned To | platform => Triage Platform Base |
| 2023-07-04 12:33 | jarmendariz | Web browser | Google Chrome => Google Chrome |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |