Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0052076 | Openbravo ERP | A. Platform | public | 2023-04-05 18:12 | 2023-05-11 09:11 |
|
Reporter | jlopez | |
Assigned To | jlopez | |
Priority | normal | Severity | major | Reproducibility | have not tried |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | PR23Q3 | |
Merge Request Status | approved |
Review Assigned To | |
OBNetwork customer | No |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0052076: Sort By Field In Selectors |
Description | The main functional requirement is to provide the ability to display the values shown in the drop down of a selector sorted by a property in particular.
Currently it is not possible to define the order by field of selector references (OBUISEL_Selector). By default the records shown in this kind of selectors are sorted by the field marked as “display field”. And in case the display field is not defined for a given selector, its records are sorted using the record identifier.
https://openbravo.atlassian.net/browse/RM-4584 [^]
|
Steps To Reproduce | * |
Proposed Solution | The main idea is to provide a new optional field named “Sort By Field” in the Defined Selector subtab. This will be a combo that will allow us to select one of the fields defined in the “Selector Field” subtab, in the same way the “Display Field” does. When defined, that field will be used by the data sources to sort the fetched records.
This configuration will be limited to selector’s drop down only: it will not be taken into account in the selector’s grid view. So, the new field may be named accordingly. |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0050971 | | closed | adrianromero | POS2 | In the Dev Backoffice, Values of combos have to be sorted in ascending numbers by sequence number |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2023-04-05 18:12 | jlopez | New Issue | |
2023-04-05 18:12 | jlopez | Assigned To | => jlopez |
2023-04-05 18:12 | jlopez | OBNetwork customer | => No |
2023-04-05 18:12 | jlopez | Modules | => Core |
2023-04-05 18:12 | jlopez | Triggers an Emergency Pack | => No |
2023-04-05 18:32 | hgbot | Merge Request Status | => open |
2023-04-05 18:32 | hgbot | Note Added: 0148319 | |
2023-04-11 20:17 | jlopez | Relationship added | related to 0050971 |
2023-05-11 09:10 | hgbot | Merge Request Status | open => approved |
2023-05-11 09:11 | hgbot | Resolution | open => fixed |
2023-05-11 09:11 | hgbot | Status | new => closed |
2023-05-11 09:11 | hgbot | Fixed in Version | => PR23Q3 |
2023-05-11 09:11 | hgbot | Note Added: 0149595 | |
2023-05-11 09:11 | hgbot | Note Added: 0149596 | |