Table of Contents

Search

  1. Preface
  2. Introduction to Data Transformation
  3. Data Processor Transformation
  4. Wizard Input and Output Formats
  5. Relational Input and Output
  6. XMap
  7. Libraries
  8. Schema Object
  9. Command Line Interface
  10. Scripts
  11. Parsers
  12. Script Ports
  13. Document Processors
  14. Formats
  15. Data Holders
  16. Anchors
  17. Transformers
  18. Actions
  19. Serializers
  20. Mappers
  21. Locators, Keys, and Indexing
  22. Streamers
  23. Validators, Notifications, and Failure Handling
  24. Validation Rules
  25. Custom Script Components

Data Transformation User Guide

Data Transformation User Guide

Mapping Mixed Content

Mapping Mixed Content

If the schema supports mixed content, each element has
before
and
after
data holders. For example, consider the following mixed content:
<Deal> We are pleased to offer you a price of <Price>34</Price> dollars. This is a special price for <Partner> <Name>Acme Gizmos, Inc.</Name> <ID>98765</ID> </Partner> valid only until December 31. </Deal>
This structure contains data holders in the following locations:
  • Immediately after the
    <Deal>
    tag, before any of the sub-elements.
  • Before the
    Price
    element
  • The
    Price
    element
  • After the
    Price
    element
  • Before the
    Partner
    element
  • The
    Partner/Name
    and
    Partner/ID
    elements
  • After the
    Partner
    element
  • Immediately before the
    </Deal>
    tag, after all the sub-elements.
You can map the text
"We are pleased to offer you a price of"
to the data holder before the
Price
element. You can map
"dollars. "
to the data holder after
Price
, and
"This is a special price for "
to the data holder before
Partner
.
The following example shows mixed content:
data_holder = /Deal/*s/Price/$text_before


Updated September 26, 2018