Openbravo Issue Tracking System - POS2
View Issue Details
0047028POS2POSpublic2021-06-08 17:102022-04-27 12:37
AugustoMauch 
AugustoMauch 
urgentminorhave not tried
closedfixed 
5
 
 
No
0047028: JIRA 3013 Undeterministic resolution of keymap if two keymaps use the same search key
If two keymaps use the same searchkey, and the organization where those keymaps are defined is part of the natural tree of a store organization, then the store will display any of those keymaps, and not necessarily the one selected in the Organization -> Schema table
In the backoffice:
- Log in
- Create two keymaps with the same searchkey. One in the store organization, another one in *.
- Reference one of the two keymaps in Organization -> Schemas

In WebPOS:
- Log in
- Select the new schema. There is a 50% change that the keymap displayed is the one selected in Organization -> Schemas, and a 50% change that the keymap displayed is the other one with the same search key
Use the keymap Id to look for keymaps instead of using the keymap searchkey in loadKeymapConfigurations.

Remove the searchkey fields if they are not needed
No tags attached.
depends on backport 0047038TAP closed hernan-dp JIRA 2013 - Undeterministic resolution of keymap if two keymaps use the same search key 
Issue History
2021-06-08 17:10AugustoMauchNew Issue
2021-06-08 17:10AugustoMauchAssigned To => AugustoMauch
2021-06-08 17:10AugustoMauchTriggers an Emergency Pack => No
2021-06-08 17:19jmelinPrioritynormal => urgent
2021-06-08 17:19jmelinSeverityminor => critical
2021-06-09 11:52AugustoMauchStatusnew => scheduled
2021-06-09 11:53dmiguelezResolution time => 1623708000
2021-06-09 11:54AugustoMauchSeveritycritical => minor
2021-06-09 11:54AugustoMauchNote Added: 0129249
2021-06-14 12:36dmiguelezResolution time1623708000 => 1625004000
2021-06-21 13:31guilleaerSummaryUndeterministic resolution of keymap if two keymaps use the same search key => JIRA 3013 Undeterministic resolution of keymap if two keymaps use the same search key
2021-06-29 03:45hgbotNote Added: 0129881
2021-06-30 10:55hgbotResolutionopen => fixed
2021-06-30 10:55hgbotStatusscheduled => closed
2021-06-30 10:55hgbotNote Added: 0129994
2021-06-30 10:55hgbotNote Added: 0129995
2022-04-22 17:56guilleaerStatusclosed => new
2022-04-22 17:56guilleaerResolutionfixed => open
2022-04-22 17:57guilleaerNote Added: 0136690
2022-04-27 12:31AugustoMauchStatusnew => scheduled
2022-04-27 12:31AugustoMauchStatusscheduled => resolved
2022-04-27 12:31AugustoMauchResolutionopen => fixed
2022-04-27 12:32AugustoMauchStatusresolved => closed
2022-04-27 12:37AugustoMauchIssue cloned0049151
2022-04-27 12:48guilleaerNote Deleted: 0136690

Notes
(0129249)
AugustoMauch   
2021-06-09 11:54   
Criticity set to minor because there is a clear workaround (avoid duplicated keymap searchkeys)
(0129881)
hgbot   
2021-06-29 03:45   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/581 [^]
(0129994)
hgbot   
2021-06-30 10:55   
Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^]
Changeset: 398f8200ffa30d0e16936dea3a83d521744e6c4e
Author: hernan-dp <h.de.prada1@gmail.com>
Date: 2021-06-30T09:32:15+02:00
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/398f8200ffa30d0e16936dea3a83d521744e6c4e [^]

fixed ISSUE-47028: Retrieve schema with unique id instead of searchkey.

---
M web-jspack/org.openbravo.pos2/src/configurations/keymapConfiguration/__test__/getKeymapInformation.test.js
M web-jspack/org.openbravo.pos2/src/configurations/keymapConfiguration/getKeymapInformation.js
M web-jspack/org.openbravo.pos2/src/configurations/keymapConfiguration/loadKeymapConfigurations.js
---
(0129995)
hgbot   
2021-06-30 10:55   
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/581 [^]