Openbravo Issue Tracking System - Retail Modules | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0056737 | Retail Modules | Web POS | public | 2024-10-10 16:13 | 2024-10-10 16:13 |
Reporter | kchoperena | ||||
Assigned To | Retail | ||||
Priority | normal | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | |||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0056737: CRM Connector Configuration: Display in Selector Result List is not working for "API property for Address" | ||||
Description | The Display in Selector Result List is not working for "API property for Address". The values shown in the result list are hardcoded | ||||
Steps To Reproduce | 1.- In the back-end, configure a CRM Connector as Type of Integration: "Customer and Address Endpoint Configuration" 2.- Configure the organization you are going to use in the POS to use the CRM configured in the previous step 2.- In the API Property for Address, configure some properties as 'Display in Selector Results List' and set a sequence number for each one 3.- Refresh the masterdata on the POS 4.- Assign a client and navigate to the address management popup (address selector) RESULT: As you can see, each item of the selector is not following the configured rules | ||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2024-10-10 16:13 | kchoperena | New Issue | |||
2024-10-10 16:13 | kchoperena | Assigned To | => Retail | ||
2024-10-10 16:13 | kchoperena | Triggers an Emergency Pack | => No |
There are no notes attached to this issue. |