• Chapter 1: Getting Started with Stylus Studio®
• Chapter 2: Editing and Querying XML
• Chapter 3: Converting Non-XML Files to XML
  • Introduction
  • DataDirect XML Converters
  • Custom XML Converters
  • The Custom XML Conversion Definition Editor
  • Parts of an Input File
    • Regions
    • Rows
    • Fields
      • Component and Sub-Component Fields
  • Working with Regions
  • Working with Fields
  • Controlling XML Output
  • Creating a Custom XML Conversion Definition
  • Using Custom XML Conversion Definitions in Stylus Studio
  • Working with EDI Conversions
  • The Converter URL Scheme
  • Custom XML Conversion Definitions Properties Reference
• Chapter 4: Working with XSLT
• Chapter 5: Creating XSLT Using the XSLT Mapper
• Chapter 6: Debugging Stylesheets
• Chapter 7: Defining XML Schemas
• Chapter 8: Defining Document Type Definitions
• Chapter 9: Writing XPath Expressions
• Chapter 10: Working with XQuery in Stylus Studio
• Chapter 11: Composing Web Service Calls
• Chapter 12: Working with WSDL Documents
• Chapter 13: Building XML Pipelines
• Chapter 14: Publishing XML Data
• Chapter 15: Integrating with Third-Party File Systems
• Chapter 16: Extending Stylus Studio
• Chapter 17: The Stylus Studio Java API
• Chapter 18: Stylus Studio GUI Reference

Home > Online Product Documentation > Table of Contents > Fields

Fields

A field is one or more columns in a row that contains data. Each different row type has its own independent set of fields. An example of a field in an employee record is employee_id.

Stylus Studio supports many data types (string, Boolean, number, date, time, and so on) and recognizes many different input formats (like different date formats, for example). Properties vary based on data type - the Base property, for example, is applicable only to Number data types.

You can define your own fields in fixed-width input files. See Defining Fields for more information.

Component and Sub-Component Fields

Some file formats, including many EDI dialects, allow fields to be subdivided into arrays, sub-fields, or composite fields. Collectively, these fields are referred to as component fields in custom XML conversion definitions, and they are fully supported, both in terms of recognition and output. You can name the container element using the Component Element Name and Sub-Component Element Name properties.