Openbravo Issue Tracking System - Modules
View Issue Details
0050376ModulesExternal Integration Infrastructurepublic2022-09-29 19:532022-10-03 13:24
AtulOpenbravo 
Triage Platform Conn 
normalmajoralways
acknowledgedopen 
5
 
 
0050376: Support avoiding object creation in import entity mappings
It is necessary to support skipping object creation in import entity mappings in some scenarios.

For eg:- Finding a Sales Order Line based on its lineNo and sales Order Document No. When this properties are added in separate entity mapping for OrderLine entity and this entity is referred in other entity then by default OrderLine property is fetched for filters as lineNo and documentNo properties in the request.

However when the input values for the new properties are such that no record is found, then default implementation tries to add new record for Order Line. This is not expected behaviour here. Expectation is that either find the record
by using new properties as filters or set it as null. So in such cases import entity mappings should support skipping or avoiding of object creation.
-
No tags attached.
Issue History
2022-09-29 19:53AtulOpenbravoNew Issue
2022-09-29 19:53AtulOpenbravoAssigned To => Triage Platform Base
2022-09-30 08:33caristuAssigned ToTriage Platform Base => Triage Platform Conn
2022-10-03 13:22caristuStatusnew => acknowledged
2022-10-03 13:22caristuTypedefect => design defect
2022-10-03 13:24caristuNote Added: 0141569

Notes
(0141569)
caristu   
2022-10-03 13:24   
Moved to design defect until we have more cases like the reported one to extract a common pattern to have a new platform mapping.

In the meantime, the proposed workaround is to implement it as a java property mapping.