Openbravo Issue Tracking System - Modules | |||||||||||||||||||||
| View Issue Details | |||||||||||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||||||||||
| 0053588 | Modules | External Data Integration | public | 2023-10-04 11:35 | 2023-10-04 17:13 | ||||||||||||||||
| Reporter | caristu | ||||||||||||||||||||
| Assigned To | Triage Platform Conn | ||||||||||||||||||||
| Priority | high | Severity | minor | Reproducibility | have not tried | ||||||||||||||||
| Status | new | Resolution | open | ||||||||||||||||||
| Platform | OS | 5 | OS Version | ||||||||||||||||||
| Product Version | |||||||||||||||||||||
| Target Version | Fixed in Version | ||||||||||||||||||||
| Merge Request Status | |||||||||||||||||||||
| Regression date | |||||||||||||||||||||
| Regression introduced by commit | |||||||||||||||||||||
| Regression level | |||||||||||||||||||||
| Review Assigned To | |||||||||||||||||||||
| Support ticket | |||||||||||||||||||||
| OBNetwork customer | |||||||||||||||||||||
| Regression introduced in release | |||||||||||||||||||||
| Summary | 0053588: Add missing checks to ensure the correct definition of the property mappings | ||||||||||||||||||||
| Description | 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 | . | ||||||||||||||||||||
| Proposed Solution | 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 | ||||||||||||||||||||
| Additional Information | |||||||||||||||||||||
| Tags | No tags attached. | ||||||||||||||||||||
| Relationships |
| ||||||||||||||||||||
| Attached Files | |||||||||||||||||||||
| Issue History | |||||||||||||||||||||
| Date Modified | Username | Field | Change | ||||||||||||||||||
| 2023-10-04 11:35 | caristu | New Issue | |||||||||||||||||||
| 2023-10-04 11:35 | caristu | Assigned To | => Triage Platform Conn | ||||||||||||||||||
| 2023-10-04 11:35 | caristu | Summary | Add import/export is supported check on property mapping definition => Add missing checks to ensure the correct definition of the property mappings | ||||||||||||||||||
| 2023-10-04 11:35 | caristu | Relationship added | related to 0053564 | ||||||||||||||||||
| 2023-10-04 17:12 | caristu | Proposed Solution updated | |||||||||||||||||||
| 2023-10-04 17:13 | caristu | Relationship added | related to 0051028 | ||||||||||||||||||
| There are no notes attached to this issue. |