|View Issue Details
|[Modules] External Data Integration
|have not tried
|Triage Platform Conn
|Fixed in Version
|Fix in branch
|Fixed in SCM revision
|Regression introduced by commit
|Review Assigned To
|Regression introduced in release
0053588: Add missing checks to ensure the correct definition of the property mappings
|Currently the check to determine if a mapping is supported in an import or export flow is being done when the property mapping itself is processed.
But it would be nice to have an early detection when the mapping is being defined so that we can help to prevent the creation of wrong mapping definitions.
Currently we have not almost any check for this apart from the specific check we added with 0053564 for the OrganizationDateTimeDirectPropertyMapping
|Steps To Reproduce
|Add checks in the src/org/openbravo/service/external/integration/handler/PropertyMappingInstanceEventHandler.java to ensure that the property mapping is properly defined. Some checks to be added are:
1) if according to the type of the property, the mapping class can be used.
2) if the mapping references another entity mapping, ensure that both are for the same integration direction, this can help to avoid problems like the one reported in 0051028
|No tags attached.
|=> Triage Platform Conn
|Add import/export is supported check on property mapping definition => Add missing checks to ensure the correct definition of the property mappings
|related to 0053564
|Proposed Solution updated
|related to 0051028
|Copyright © 2000 - 2009 MantisBT Group