How to flatten composite records from Rest Source
Many real-world applications need to handle data structures which can't be represented with a simple flat table. A good example is an invoice record where each record contains a sub-list of line item records. For each main object, which identifies the customer invoice, there can be any number of child records, which identify each of the items being billed. These child records are also known as composite records.
Action:
When Rest Source have outputs for composite records and needed to be flatten to have them with the main objects in one table:
Solution:
- In Rest Source, Go to columns tab and choose the composite records output.
- Then verify if all the columns are check marked or not. If not then you need to check marked all the columns. See below screen capture for reference where there is only single composite record output available.
If only single composite record ouput available:
- Choose the composite record output from drop down list and then make sure all the columns are check marked. If not then you need to manually check marked all the columns. See below screen capture where the composite record output has been selected and the child records columns are initially unchecked highlighted yellow.
- Check mark all the columns as mentioned in the below screen capture, So they are available at the destination when we connect source to destination.
- Connect Rest Source with Destination and choose the output that contains composite record. See below screen capture for reference.
- Now you will have the composite records flatten with the main objects.
If multiple composite record ouputs are available:
- If you have multiple composite record outputs available in the drop down list then choose each composite output and check mark all the columns that are initially unchecked.
- Then using merge join you can join composite records into one flatten table as mentioned in the below screen capture.
The composite record output contains not only fields from the composite record, but also the parent records. The output will be populated with sets of rows, one set for each parent record. Each set of rows is separated with blank row (all NULLs).Book a Presales Call
Are you new to COZYROC and evaluating our solutions?
Book a Presales Call with us now and get 5% off SSIS+.
Book a Presales Call with us now and get 5% off SSIS+.
Related Articles
How to work with composite records handling in a REST source component.
The composite record output contains not only fields from the composite record, but also the parent records. The output will be populated with sets of rows, one set for each parent record. Each set of rows is separated with blank row (all NULLs). ...How to work with composite records handling in a rest destination component.
The composite record input accepts sets of rows, one set for each parent record. Each set of rows must be separated with blank row (all NULLs). The parent record will not finish processing its record, until all composite record children have received ...How to work with composite records handling in a Dynamics GP source component.
The composite object output contains not only properties from the composite record, but also the parent record. The output will be populated with sets of records, one set for each parent record. Each set of records is separated with blank row (all ...How to work with composite records handling in a Sage source component.
The composite record output contains not only properties from the composite entity, but also the parent entities. The output will be populated with sets of records, one set for each parent record. Each set of records is separated with blank row (all ...How to work with composite records handling in a Netsuite source component.
The composite record output contains not only fields from the composite record, but also the parent records. The output will be populated with sets of rows, one set for each parent record. Each set of rows is separated with blank row (all NULLs). For ...