Project:
| View Revisions: Issue #58262 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0058262: UpdatedDate of the inventory lines is not correctly filled while importing big Inventories through API | ||
| Revision | 2025-03-17 17:55 by kchoperena | ||
| Description | https://livebuilds.openbravo.com/context/retail_pos2_modules_pgsql/api?urls.primaryName=Business+API+-+Transactional+Data#/Inventory/Import_Inventory [^] The IMPORT inventory API allows us to import from an external system inventories. Normally, in an initial data load the inventories are so big because the client synchronizes the whole inventory between the systems In these cases, we notice that the UpdatedDate is not filled correctly as there are registers with a creation date later than the updated one The side problem of this issue, which has a big impact, is that the stock transactions are triggered using the Multiple Record Event Triggering Process which checks the updated date to decide which records need to be triggered. So what can happen is that when the inventory is importing and at the same time the process running, some records are not sent to the external system |
||
| Revision | 2025-03-17 17:52 by kchoperena | ||
| Description | https://livebuilds.openbravo.com/context/retail_pos2_modules_pgsql/api?urls.primaryName=Business+API+-+Transactional+Data#/Inventory/Import_Inventory [^] The IMPORT inventory API allows us to import from an external system inventories. Normally, in an initial data load the inventories are so big because the client synchronizes the whole inventory between the systems In these cases, we notice that the UpdatedDate is not filled correctly as there are registers with a creation date later than the updated one |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |