Table of Contents

Search

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

Transformations

Transformations

Mapping hierarchical fields

Mapping hierarchical fields

To map hierarchical fields in the request mapping, the hierarchies of the incoming fields and request schema fields must match.
For example, the following image shows a request schema in an API collection:
An API collection has a request schema that contains two structs. The first struct represents a full name with first name and last name elements. The following struct represents an address with state, place, and ZIP code elements.
The following image shows incoming fields in a Machine Learning transformation with a hierarchy that matches the request schema:
The Incoming Fields tab is selected in a Machine Learning transformation. The tab lists two structs. The first struct represents a full name with first name and last name elements. The following struct represents an address with state, place, and ZIP code elements.
The following image shows the request mapping between the incoming fields and the request schema fields:
The Request Mapping tab is selected in a Machine Learning transformation. The Incoming Fields side contains two structs that represent a full name and an address, respectively. The incoming fields are mapped to corresponding structs on the Request Schema Fields side.
If the hierarchies don't match, use a Hierarchy Processor transformation before the Machine Learning transformation to restructure the incoming data according to the request schema fields. For more information, see Hierarchy Processor transformation.

0 COMMENTS

We’d like to hear from you!