Skip to end of metadata
Go to start of metadata



File schemas represent the "request" and "response" structures for interaction with a data resource. File schemas can be inherited from activities that are adjacent to a transformation, or they can be defined directly in the the transformation. A schema defined directly within the transformation takes precedence over a schema defined as part of an activity.

Whether a file schema is required depends on if the activity is being used as a source or target of a transformation. In some cases, such as in an operation designed to archive files from a data source to a target without a transformation, no file schemas are required; if they are specified, they are simply ignored.

These sections or pages are included in this topic:

  • Schema Basics
    This topic covers general information about schemas, including when to use a schema, how schemas are processed, how to regenerate schemas, and menu actions that are available for all schemas.
  • Schemas Defined in a Transformation
    These pages cover the various ways to create a schema directly in a transformation, including by creating a custom flat or hierarchical schema, by providing a sample file, by reusing an existing schema, or by mirroring (copying) a schema.
  • Schemas Defined in an Activity
    This page provides an overview of defining a schema within an activity. Schemas defined in an activity are not considered part of the transformation but are instead inherited by the transformation when a schema is not directly defined in the transformation.

Known Issue

  • An imported JSON schema file containing a property named length with a numeric value fails
    • Summary: A property named length with a numeric value causes an import failure.
    • Workaround: Modify the schema in Cloud Studio changing the property named length with a numeric value to a string value by quoting the value. For example, change:
      "length": 5.00 to "length": "5.00".

Search in This Topic


  • No labels