Default Escape Character Type (Node Property of Flat File Schemas)
Use the Default Escape Character Type property to configure, for the entire schema, how an alternative default escape character will be expressed in the Default Escape Character property and in the underlying XSD representation.
Applies to Nodes of Type
Category
Flat File
Allowed Values
Drop-down list choice | Description |
---|---|
Character | Indicates that you will provide a default escape character as a character in the Default Escape Character property, which will be formatted as a character in the XSD representation of the schema. |
Hexadecimal | Indicates that you will provide the hexadecimal value ("0xNN") of a default escape character in the Default Escape Character property, which will be formatted as a hexadecimal value in the XSD representation of the schema. |
None | Removes the corresponding annotation in the XSD representation of the schema, if any, specifying that there is no default escape character for the entire schema. You must explicitly specify an appropriate escape character for every Record node within the schema. Selecting Default Escape Character for the value of the Escape Character property of any of the Record nodes within the schema will result in a compilation error. |
Default Value
None, resulting in no annotation being added to the XSD representation of the schema.
XSD Persistence
As the value of the escape_char_type (="char" or "hex") attribute of the schema/annotation/appinfo/schemaInfo element.
Remarks
You can examine and set this property in the Visual Studio Properties window when you select the Schema node in BizTalk Editor and you have configured the Flat File Extension option for the Schema Editor Extensions property of that node.
If you configure this property with a value of Character or Hexadecimal, then you can configure the Default Escape Character property in one of these two formats.
This value may be overridden for particular Record nodes by using the Escape Character and Escape Character Type properties.
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