How to Implement Best Import Mapping Strategy for Complex JSON
0
Hi, We would like to import mapping a list of task content as outlined below, so that requests can be approved or rejected directly within the portal. However, we are encountering challenges at the import mapping stage. Key points of our situation: We have more than 10 systems to integrate. Each request type differs from the others. All form data is received within a contentData structure. We would prefer not to maintain a single, monolithic contentData entity, as scaling to 100+ attributes would make management difficult as new task sources are added (also manipulating json may consequent with errors). Instead, we would like to store contentData objects through different associations. Our question: How can we best import mapping this type of data? We are considering implementing specializations of contentData using inheritance, but we are not certain if this is the most effective approach. [ { "taskSource": "EmployeeLeave", "subject": "John Doe - Leave Form Approval", "summary": "John Doe- Leave Form First Manager Approval ", "contentData": { "formId": 3333 "employee": "John Doe", "employeeID": "4500" }, { "taskSource": "SAPTravel", "subject": "Jane Doe - Car Request Approval", "summary": "Jane Doe - Car Request First Manager Approval ", "contentData": { "requestid": 121 "requestor": "Jane Doe", "driver": "Transporter", "car":"2025 Honda Prologue", "date": "2025-11-05" }, ]