Child Delimiter Type (Node Property of Flat File Schemas)
Use the Child Delimiter Type property to configure, on a per-record basis, how an alternative child delimiter string will be expressed in the Child Delimiter property and in the underlying XSD representation, or whether the default child delimiter string will be used.
Applies to Nodes of Type
Category
Flat File
Allowed Values
Drop-down list choice | Description |
---|---|
Character | Specifies that you will provide a child delimiter string as characters in the Child Delimiter property, which will be formatted as characters in the XSD representation of the schema. |
Hexadecimal | Specifies that you will provide the hexadecimal value ("0xNNNN") of a child delimiter string in the Child Delimiter property, which will be formatted as a hexadecimal value in the XSD representation of the schema. |
Default Child Delimiter | Specifies that the delimiter specified using the Default Child Delimiter property will be used. |
None | Removes the corresponding annotation in the XSD representation of the schema, if any, specifying that there is no child delimiter for this Record node. If more than one child node is specified in the schema, this setting will result in a warning during compilation. |
Default Value
None, resulting in no annotation being added to the XSD representation of the schema.
XSD Persistence
As the value of the child_delimiter_type (="char", "hex", or "default") attribute of the element/annotation/appinfo/recordInfo annotation element.
Remarks
You can examine and set this property in the Visual Studio Properties window when you have:
Selected a Record node (including a root Record node) in BizTalk Editor
Set the Structure property of the selected Record node to Delimited
Configured the Flat File Extension option for the Schema Editor Extensions property of the Schema node
If you configure this property with a value of Character or Hexadecimal, then you can configure the Child Delimiter property in one of these two formats.
See Also
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for