Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Data Engineering Integration
  3. Mappings
  4. Mapping Optimization
  5. Sources
  6. Targets
  7. Transformations
  8. Python Transformation
  9. Data Preview
  10. Cluster Workflows
  11. Profiles
  12. Monitoring
  13. Hierarchical Data Processing
  14. Hierarchical Data Processing Configuration
  15. Hierarchical Data Processing with Schema Changes
  16. Intelligent Structure Models
  17. Blockchain
  18. Stateful Computing
  19. Appendix A: Connections Reference
  20. Appendix B: Data Type Reference
  21. Appendix C: Function Reference

Rules and Guidelines for Complex Data Type Definitions

Rules and Guidelines for Complex Data Type Definitions

Consider the following rules and guidelines when you work with complex data type definitions:
  • A struct port or a struct element in a complex port must reference a complex data type definition.
  • You cannot reference a complex data type definition in one mapping to a complex port in another mapping.
  • You cannot reference a recursive data type definition to a struct port or a struct element in a complex port.
  • Changes to the elements in a complex data type definition are automatically propagated to complex ports that reference the complex data type definition.
  • If you change the name of the type definition library or the complex data type definition, you must update the name in expressions that use complex functions such as STRUCT_AS, RESPEC, and CAST.
  • In a midstream parsing mapping, the source string that contains JSON or XML elements is defined with a complex data type definition. For more information, see Midstream Parsing of Hierarchical Data.


Updated September 28, 2020