Open. Indicates that the data in the document instance does not totally adhere to the structure of the specification.

Empty. Indicates that the root node cannot contain subelements.

Text Only. Indicates that the root node can contain text and not subelements.

Note:

One. Indicates that one and only one of the constituent elements can appear.

Sequence. Indicates that the constituent elements must appear in the order specified.

Open. Indicates that the data in the document instance and the specification structure do not match.

Empty. Indicates that the record cannot contain sub- elements.

Text Only. Indicates that the record can contain text and not subelements.

One. Indicates that one and only one of the constituent elements can appear.

Sequence. Indicates that the constituent elements must appear in the order specified.

Note:

Element

Open. Indicates that the data in the document instance and the specification structure do not match.

Note:

If this property value is left blank, the default value is Open.

Note:

The Content property is available only for a field with its Type value set to Element.

Important:

If the Standard property value on the Reference tab is set to X12, EDIFACT, or Custom, you can assign a Custom Data Type value on the Parse tab. If you specify a Custom Data Type value, the value in the Data Type field is automatically changed to match the selection that you specified for the Custom Data Type value. If you already have a value specified in the Custom Data Type field and then specify a value in the Data Type field on the Declaration tab, the value specified in the Custom Data Type field is cleared.

In a specification, if you create a field with the Data Type property set to IDREF or IDREFS, you must create another field in that specification with the Data Type set to ID.

Note:

Note:

Note:

XML for creating a specification based on Extensible Markup Language (XML).

X12 for creating a specification based on X12.

EDIFACT for creating a specification based on EDIFACT.

Note:

Note:

Note:

Note:

Arabic (1256)

Baltic (1257)

Central-European (1250)

Cyrillic (1251)

Greek (1253)

Hebrew (1255)

Japanese-Shift-JIS (932)

Korean (949)

Little-Endian-UTF16 (1200)

Simplified-Chinese-GBK (936)

Thai (874)

Traditional-Chinese-Big5 (950)

Turkish (1254)

Vietnamese (1258)

Western-European (1252)

Note:

This property field displays only if the Standard field on the Reference tab (for the root node) is set to Custom.

UTF7 (65000) and UTF8 (65001) are not supported by BizTalk Server.

Yes. Indicates that the specification is to be used as an inbound receipt document. A correlator component (X12, EDIFACT, or CUSTOM) is expected to correlate the receipt document to the outbound document that it acknowledges (in other words, something previously sent to the sender of the receipt).

No. Indicates that the specification is not to be used as an inbound receipt document.

Notes:

If the receipt value is left blank, the default value is No.

Yes. Indicates that the specification is an interchange specification.

No. Indicates that the specification is not an interchange specification.

Note:

Note:

Note:

If you type an asterisk (*), the record is considered to be a looping record. If this specification is used in BizTalk Mapper, it compiles this record as a loop. If you type 1, BizTalk Mapper does not consider this record to be a looping record.

Yes. Indicates that the field is required.

No. Indicates that the field is not required.

Note:

Note:

Note:

Note:

For a non-XML file, such as a flat file, you can type a Source Tag Identifier property to identify any tag that might exist in the original file.

Prefix. A prefix delimiter appears before each component, and each member of a component in a series. For example, where * is the delimiter: *a*a*b*c.

Postfix. A postfix delimiter appears after each component and each member of a component in a series. For example, where * is the delimiter: a*a*b*c*.

Infix. An infix delimiter appears between components and members of components in a series. For example, where * is the delimiter: a*a*b*c. This is the inherent field order for all EDI documents.

Note:

Default Record Delimiter. Indicates that the delimiter is the value of the Default Record Delimiter property, which is defined in the document instance.

Default Field Delimiter. Indicates that the delimiter is the value of the Default Field Delimiter property, which is defined in the document instance.

Default Escape Character. Indicates that the escape character is a value defined in the document instance.

An escape character is useful if you have a character in your field data that is also used as the delimiter character for the field's parent node. For example, if your field data is

Browne,Peter,1231,yes

and you have chosen a comma as the delimiter value of the node that contains the field, BizTalk Editor interprets the comma after “Browne” to be a delimiter, even if you intend for it to be part of the field data. A solution for this is to place an escape character directly preceding the delimiter character that you want to include in the field data. For example, if your escape character is specified as a backslash, you can place a backslash directly preceding a delimiter character as in the following example:

Browne,Peter,1231,yes

The comma after the backslash is interpreted by BizTalk Editor as field data rather than a delimiter character. Using the preceding example, the field data would be Browne, Peter

Note:

Yes. Indicates that when the serializer reaches the record delimiter, the serializer automatically appends a new line (LF,0x0A).

No. Indicates that when the serializer reaches the record delimiter, the serializer continues on the same line for the following record.

Note:

Yes. Tells the parser to skip the carriage return (CR) value after a delimiter.

No. Tells the parser not to skip the CR value after a delimiter.

Note:

Yes. Tells the parser to skip the line feed (LF) value after a delimiter.

No. Tells the parser not to skip the LF value after a delimiter.

Note:

Yes. Tells the parser or the serializer not to count this record when counting the total number of records in the specification.

No. Tells the parser or the serializer to count this record when counting the total number of records in the specification.

Notes:

When a document instance is submitted to BizTalk Server, if the number of records in the document instance does not match the calculated number of records in the specification, a parsing failure results.

String (AN). AN is for alphanumeric fields.

Binary Hexadecimal (B). B is for binary fields.

Date (CY). CY is for four-digit date fields.

Number (D0-D4). D0 through D4 (inclusive) are for decimal fields. The single-digit number represents the number of digits to the right of the decimal.

Date (DT). DT is for date fields.

String (ID). ID is for identification fields.

Number (N). N is for integer fields.

Number (N0-9). N0 through N9 (inclusive) are for implied decimal fields (the decimal character does not appear in the data). The single-digit number represents the number of digits to the right of the decimal.

Number (R). R is for real number fields.

Number (R0-R9). R0 through R9 (inclusive) are for real number fields. The single-digit number represents the number of digits to the right of the decimal.

Time (TM). TM is for time fields.

Important:

If you specify a Custom Data Type value, the value in the Data Type field on the Declaration tab is automatically changed to match the selection that you specified for the Custom Data Type value. For example, if you change the Custom Data Type on the Parse tab to Date (CY), the Data Type value on the Declaration tab automatically changes to Date. If you specify a value in the Data Type field on the Declaration tab, the value specified in the Custom Data Type field is cleared.

Notes:

If you specify Date (DT), Date (CY), or Time (TM) for the Custom Data Type property, you must also set a value for the Custom Date/Time Format property.

Notes:

Left. Aligns data to the left in positional files when the data is less than the maximum field length. Also aligns data to the left in delimited files when the amount of data is less than the minimum length requirement.

Right. Aligns data to the right in positional files.

Notes:

Browne,Peter,1231,yes

and you have chosen a comma as the delimiter value of the node that contains the field, BizTalk Editor interprets the comma after “Browne” to be a delimiter, even if you intend for it to be part of the field data. A solution for this is to define a value for the wrap character property and then enclose the field data in the wrap character. For example, you can set the wrap character property to double quotation marks for the first field and then type your field data as in the following example:

“Browne,Peter”,1231,yes

The comma between the double quotation marks is interpreted by BizTalk Editor to be field data rather than a delimiter value.

Notes:

If your field data includes characters that are also used as the wrap character, you must enclose those characters in another set of wrap characters.

For example, with the wrap character value set to double quotation marks,

“Browne,Peter “”Pete”””

is parsed by BizTalk Editor to appear as

Browne,Peter “Pete”

Notes:

This property is available only if the pad character is set for that field.

Delimited. Indicates that the root node is based on a delimited file structure. Records can be individually based on delimited or positional file structures.

Select one of the following options for Record properties:

Delimited. Indicates that the record is based on a delimited file structure. Descendant records can be individually based on delimited or positional file structures.

Positional. Indicates that the record is based on a positional file structure. Positional records cannot have child records.

Note:

For a document to be both delimited and positional, the root node must have its Structure property set to Delimited. You can then set the Structure property for individual records to Positional or Delimited, as necessary.

If you change from one structure to another, a message box appears. Click Yes to confirm the structure change. Some new properties might appear, and some existing properties might be removed.

If you right-click the Structure property value field of a positional record and click Clear Property, BizTalk Editor interprets the structure of the record as delimited. Some new properties might appear, and some existing properties might be removed.

Note:

For a non-XML file, such as a flat file, you can type a Source Tag Identifier property to identify any tag that might exist in the original file.

Prefix. A prefix delimiter appears before each component, and each member of a component, in a series. For example, where * is the delimiter: *a*a*b*c.

Postfix. A postfix delimiter appears after each component, and each member of a component, in a series. For example, where * is the delimiter: a*a*b*c*.

Infix. An infix delimiter appears between components, and members of components, in a series. For example, where * is the delimiter: a*a*b*c. This is the inherent field order for all electronic data interchange (EDI) documents.

Note

Character. Allows you to designate a delimiter value on the Parse tab. If you select Character, you must specify a delimiter value.

Default Record Delimiter. Indicates that the delimiter is the value of the Default Record Delimiter property, on the Reference tab for the root node.

Default Field Delimiter. Indicates that the delimiter is the value of the Default Field Delimiter property, on the Reference tab for the root node.

Character. Allows you to designate an escape character value on the Parse tab. If you select Character, you must specify an escape value.

Default Escape Character. Indicates that the escape character is the value of the Default Escape Delimiter property, on the Reference tab for the root node.

An escape character is useful if you have a character in your field data that is also used as the delimiter character for the field's parent node. For example, if your field data is

Browne,Peter,1231,yes

and you have chosen a comma as the delimiter value of the node that contains the field, BizTalk Editor interprets the comma after “Browne” to be a delimiter, even if you intend for it to be part of the field data. A solution for this is to place an escape character directly preceding the delimiter character that you want to include in the field data. For example, if your escape character is specified as a backslash, you can place a backslash directly preceding a delimiter character as in the following example:

Browne,Peter,1231,yes

Yes. Indicates that when the parser reaches the record delimiter, the parser must move to the next line and begin with the following record on that line.

No. Indicates that when the parser reaches the record delimiter, the parser must continue on the same line for the following record.

Note:

Yes. Tells the parser to skip the carriage return (CR) value after a delimiter.

No. Tells the parser not to skip the CR value after a delimiter.

Note:

Yes. Tells the parser to skip the line feed (LF) value after a delimiter.

No. Tells the parser not to skip the LF value after a delimiter.

Note:

Yes. Tells the parser or the serializer not to count this record when counting the total number of records in the specification.

No. Tells the parser or the serializer to count this record when counting the total number of records in the specifi-cation.

Note:

When a document instance is submitted to BizTalk Server, if the number of records in the document instance does not match the calculated number of records in the specification, a parsing failure results.

String (AN). AN is for alphanumeric fields.

Binary Hexadecimal (B). B is for binary fields.

Date (CY). CY is for four-digit date fields.

Number (D0-D4). D0 through D4 (inclusive) are for decimal fields. The single-digit number represents the number of digits to the right of the decimal.

Date (DT). DT is for date fields.

String (ID). ID is for identification fields.

Number (N). N is for integer fields.

Number (N0-9). N0 through N9 (inclusive) are for implied decimal fields (the decimal character does not appear in the data). The single-digit number represents the number of digits to the right of the decimal.

Number (R). R is for real number fields.

Number (R0-R9). R0 through R9 (inclusive) are for real number fields. The single-digit number represents the number of digits to the right of the decimal.

Time (TM). TM is for time fields.

Important:

If you specify a Custom Data Type value, the value in the Data Type field on the Declaration tab is automatically changed to match the selection that you specified for the Custom Data Type value. For example, if you change the Custom Data Type on the Parse tab to Date (CY), the Data Type value on the Declaration tab automatically changes to Date. If you specify a value in the Data Type field on the Declaration tab, the value specified in the Custom Data Type field is cleared.

Note:

Note:

Left. Aligns data to the left in positional files when the data is less than the maximum field length. This also aligns data to the left in delimited files when the amount of data is less than the minimum length requirement.

Right. Aligns data to the right in positional files.

Note:

If no value is selected for the Justification property, data is aligned to the left by default.

Browne,Peter,1231,yes

and you have chosen a comma as the delimiter value of the node that contains the field, BizTalk Editor interprets the comma after “Browne” to be a delimiter, even if you intend for it to be part of the field data. The solution to this is to define a value for the wrap character property and then enclose the field data in the wrap character. For example, you can set the wrap character property to double quotation marks for the first field and then type your field data as in the following example:

“Browne,Peter”,1231,yes

The comma between the double quotation marks is interpreted by BizTalk Editor to be field data rather than a delimiter value.

Note:

If you have characters in your field data that are also used as the wrap character, you must enclose those characters in another set of wrap characters.

For example, with the wrap character value set to double quotation marks,

“Browne,Peter “”Pete”””

is parsed by BizTalk Editor to appear as

Browne,Peter “Pete”.

Note:

This property can be set for a field only if the pad character is set for that field.

Positional. Indicates that the root node is based on a positional file structure.

Note:

A document with a positional root node can have no records.

If you right-click the Structure property value field of a positional root node and click Clear Property, BizTalk Editor interprets the structure of the root node as delimited. Some new properties might appear, and some existing properties might be removed.

Note:

For a non-XML file, such as a flat file, you can type a Source Tag Identifier property to identify any tag that might exist in the original file.

Yes. Indicates that when the parser reaches the record delimiter, the parser must move to the next line and begin with the following record on that line.

No. Indicates that when the parser reaches the record delimiter, the parser must continue on the same line for the following record.

Note:

Yes. Tells the parser to skip the carriage return (CR) value after a delimiter.

No. Tells the parser not to skip the CR value after a delimiter.

Note:

Yes. Tells the parser to skip the line feed (LF) value after a delimiter.

No. Tells the parser not to skip the LF value after a delimiter.

Note:

Yes. Tells the parser or the serializer not to count this record when counting the total number of records in the specification.

No. Tells the parser or the serializer to count this record when counting the total number of records in the specifi-cation.

Note:

When a document instance is submitted to BizTalk Server, if the number of records in the document instance does not match the calculated number of records in the specification, a parsing failure results.

String (AN). AN is for alphanumeric fields.

Binary Hexadecimal (B). B is for binary fields.

Date (CY). CY is for four-digit date fields.

Number (D0-D4). D0 through D4 (inclusive) are for decimal fields. The single-digit number represents the number of digits to the right of the decimal.

Date (DT). DT is for date fields.

String (ID). ID is for identification fields.

Number (N). N is for integer fields.

Number (N0-9). N0 through N9 (inclusive) are for implied decimal fields (the decimal character does not appear in the data). The single-digit number represents the number of digits to the right of the decimal.

Number (R). R is for real number fields.

Number (R0-R9). R0 through R9 (inclusive) are for real number fields. The single-digit number represents the number of digits to the right of the decimal.

Time (TM). TM is for time fields.

Important:

If you specify a Custom Data Type value, the value in the Data Type field on the Declaration tab is automatically changed to match the selection that you specified for the Custom Data Type value. For example, if you change the Custom Data Type on the Parse tab to Date (CY), the Data Type value on the Declaration tab automatically changes to Date. If you specify a value in the Data Type field on the Declaration tab, the value specified in the Custom Data Type field is cleared.

Note:

Note:

Left. Aligns data to the left in positional files when the data is less than the maximum field length. Also aligns data to the left in delimited files when the amount of data is less than the minimum length requirement.

Right. Aligns data to the right in positional files.

Note: