Table of Contents

Search

  1. Preface
  2. Workflow Manager
  3. Workflows and Worklets
  4. Sessions
  5. Session Configuration Object
  6. Tasks
  7. Sources
  8. Targets
  9. Connection Objects
  10. Validation
  11. Scheduling and Running Workflows
  12. Sending Email
  13. Workflow Monitor
  14. Workflow Monitor Details
  15. Session and Workflow Logs
  16. Appendix A: Session Properties Reference
  17. Appendix B: Workflow Properties Reference

Workflow Basics Guide

Workflow Basics Guide

Null and Empty Strings

Null and Empty Strings

You can choose how the Integration Service handles null data or empty strings when it writes elements and attributes to an XML target file. By default, the Integration Service does not output element tags or attribute names for null values. The Integration Service outputs tags and attribute names with no content for empty strings.
To change these defaults, you can change the Null Content Representation and Empty String Content Representation XML target properties. For attributes, change Null Attribute Representation and the Empty String Attribute Representation properties.
Choose one of the following values for each property:
Properties
Property Value
Integration Service Behavior
Null Content or Empty String Content
  • No Tag
  • Tag with Empty Content
  • Does not output a tag.
  • Outputs the XML tag with no content.
Null Attribute or Empty String Attribute
  • No Attribute
  • Attribute Name with Empty String
  • Does not output the attribute.
  • Outputs the attribute name with no content.
You can specify fixed or default values for elements and attributes. When an element in an XML schema or a DTD has a default value, the Integration Service inserts the value instead of writing empty content. When an element has a fixed value in the schema, the value is always inserted in the XML file. If the XML schema or DTD does not specify a value for an attribute and the attribute has a null value, the Integration Service omits the attribute.
If a required attribute does not have a fixed value, the attribute must be a projected field. The Integration Service does not output invalid attributes to a target. An error occurs when a prohibited attribute appears in an element tag. An error also occurs if a required attribute is not present in an element tag. The Integration Service writes these errors to the session log or the error log when you enable row error logging.
The following table describes the format of XML file elements and attributes that contain null values or empty strings:
Type of Output
Type of Data
Target File
Element
Null
<elem></elem>
-
Empty string
<elem></elem>
Attribute
Null
<elem>...</elem>
-
Empty string
<elem attrib=“”>...</elem>

0 COMMENTS

We’d like to hear from you!