(0149770)
|
hgbot
|
2023-05-16 09:25
|
|
Directly closing issue as related merge request is already approved.
Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^]
Changeset: 57fbe1a57423cc0271f9b6fca1f2bce4131fbb5c
Author: Augusto Mauch <augusto.mauch@openbravo.com>
Date: 16-05-2023 07:25:30
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/57fbe1a57423cc0271f9b6fca1f2bce4131fbb5c [^]
Fixes ISSUE-52346: When saving keymap editor changes, update existing row if possible
The KeymapLoader was already trying to update an existing row instead of creating a new one that would result in a database
contraint not being met, and an Error While Importing being generated. This worked fine when the id of the existing record
was the same as the id of the record being saved from the frontend. That is the most common case, but if the terminal did
not have the latest keymap information data, it could be that a equivalent record to an another one in the backend was created
(different ID, but same unique properties).
For those entities that do not have subtabs (that is, no other entities reference them), instead of creating the duplicated record
we can apply the new changes coming from the frontend to the existing record in the frontend, even if they have different IDs
---
M src/org/openbravo/pos2/KeymapLoader.java
---
|
|