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

Restrictions on the Key

Restrictions on the Key

The
unique_fields
must be nested within the
recurring_element
. They can be attributes of the element, they can be nested elements at any level of nesting, or they can be attributes of the nested elements.
For example, this means that
Persons/Person/SocialSecurity/@Number
can be a valid key for
Persons/Person
, because
@Number
is nested within
Persons/Person
. On the other hand,
Persons/Child
is not a valid key for
Persons/Person
because it is not correctly nested.
The
unique_fields
must identify the closest ancestor that can have multiple occurrences. For example, if both
Parent
and
Child
are multiple-occurrence elements, then
Parent/Child/@name
can be a valid key for
Parent/Child
but not for
Parent
.
The
unique_fields
must have simple data types. They cannot be structures.


Updated September 26, 2018