Allowing Undefined Data

Building Your Event-Driven Architecture : Service Development Help : Working with Flat Files : Creating Flat File Schemas : Allowing Undefined Data

You can configure how Integration Server handles undefined data errors that are generated at any location in the flat file schema.

When the convertToValues service processes an undefined record, it puts a placeholder named unDefData in the resulting IS document and stores the record as a string in the pipeline.

Note:

If the file is encoded using a multi-byte encoding, and if you use a fixed length or variable length parser, the service puts two placeholders into the pipeline: unDefData and unDefBytes.

To specify how Integration Server handles undefined data

1. In the Package Navigator view of Designer, open the flat file schema to which you want to specify how you want Integration Server to handle undefined data.

2. In the Properties view next to Allow undefined data, choose one of the following options:

Select...	To...
True	Allow undefined data. If you select this option, you can choose whether to allow undefined data at the record level.
False	Not allow undefined data in any location in this flat file schema. This is the default. If the validate variable of the convertToValues service is set to true, the convertToValues service will generate errors when undefined data is encountered.

3. Save the flat file schema.

Contact Support | Community | Feedback