Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. B2B transformation
  7. Aggregator transformation
  8. Cleanse transformation
  9. Data Masking transformation
  10. Data Services transformation
  11. Deduplicate transformation
  12. Expression transformation
  13. Filter transformation
  14. Hierarchy Builder transformation
  15. Hierarchy Parser transformation
  16. Hierarchy Processor transformation
  17. Input transformation
  18. Java transformation
  19. Java transformation API reference
  20. Joiner transformation
  21. Labeler transformation
  22. Lookup transformation
  23. Machine Learning transformation
  24. Mapplet transformation
  25. Normalizer transformation
  26. Output transformation
  27. Parse transformation
  28. Python transformation
  29. Rank transformation
  30. Router transformation
  31. Rule Specification transformation
  32. Sequence Generator transformation
  33. Sorter transformation
  34. SQL transformation
  35. Structure Parser transformation
  36. Transaction Control transformation
  37. Union transformation
  38. Velocity transformation
  39. Verifier transformation
  40. Web Services transformation

Transformations

Transformations

Preserve incoming fields

Preserve incoming fields

When you add incoming struct and array fields to the output, you can preserve the incoming field. When you preserve the incoming field, it's copied to hierarchical output without changing the structure.
When you add a nested array and select "Preserve incoming fields", the data source configuration for the output group determines how the records are created.

Example of preserving incoming fields

You want to extract the description information from a nested array of maintenance records. The description information is in an array of strings. You want the output data to also be in an array of strings.
Add the description array to the output group and choose
Preserve Incoming Field
.
The following image shows the incoming and output fields:
The image shows the Hierarchy Processor tab of the Hierarchy Processor transformation. The Incoming Fields panel contains one input group with the following field: vehicle (array). The vehicle array contains the following fields: make (string), model (string) insurance (struct), and maintenance (array). The insurance struct contains the following fields: company (string) and policy_num (string). The maintenance array contains the following fields: date (string) and description (array of strings). The Output Fields panel contains the following field: description (array of strings).
When
Data Integration
creates the output array, it sets the data source for the description array to
Input.vehicle.vehicle.maintenance.maintenance.desc.elem
, indicating that the information for the output array comes from the elements in the desc array in the Input group. The data source for the Output group determines the structure of the output records.
By default,
Data Integration
sets the data source for the Output group to
Input
. When you run the mapping,
Data Integration
collates all descriptions into one output record. To write the descriptions to separate records for each vehicle, set the data source to
Input.vehicle.vehicle
. To write the descriptions to separate records for each maintenance record, set the data source to
Input.vehicle.vehicle.maintenance.maintenance
. For more information about data source configuration, see Configuring data sources.

0 COMMENTS

We’d like to hear from you!