Table of Contents


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



Hierarchy Parser rules and guidelines

Hierarchy Parser rules and guidelines

When you use the Hierarchy Parser transformation, consider the following rules and guidelines.

Source file size

The Hierarchy Parser transformation can process source files that are up to 1.5 GB in size. To process files that are larger than 1.5 GB, use an intelligent structure model. For more information about intelligent structure models, see

Handling of Boolean data types

The Hierarchy Parser transformation always returns 0 for Boolean data type input.

Hierarchical schema that is based on an XSD file

When you associate a hierarchical schema that is based on an XSD file with a Hierarchy Parser transformation, note that you can't use the Hierarchy Parser transformation with the following XSD component types:
  • xsd:any
  • xsd:type
  • mixed
  • xsi:type
  • default values
  • fixed values
  • no type, for example
    <xs:element name="A" maxOccurs="unbounded"/>
To parse large or complex XSD files that contains more than 10,000 elements and attributes, recursive elements, or complex deep hierarchies, use the Structure Parser transformation. For more information, see Structure Parser transformation.

Using a Hierarchy Parser transformation in a Mapplet transformation

When you use a Hierarchy Parser transformation in a mapplet, to prevent runtime errors, be sure that the combined Mapplet transformation name doesn't exceed 80 characters. For more information, see Mapplet transformation names.


We’d like to hear from you!