Covast are organizing an event in Rotterdam, The Netherlands, especially for Microsoft Solutions Sales and Technical Sales people in EMEA. The main theme of the event will be “Selling BizTalk in the B2B Space”.
Please come and join us December 1 and 2.
For more information, contact petra.kroesen@covast.com.
Did you know that setting the allow_early_termination=”yes” attribute on a flat file record only allows early termination of the last field in the record? So, in case of:
PositionalRecord
-Field1
-Field2
-Field3
-Field4
-Field5
-PositionalRecord1
–Field6
–Field7
–Field8
Only Field8 can early terminate.
Bummer!
I heard (from a trusted source in Redmond) that this issue will be addressed in BizTalk Server 2006.
I’ve been asked a lot by our larger (publicly listed) customers about getting a SOX compliant implementation of the EDI Accelerator for BizTalk Server. I wrote a white paper on that topic, which is still in its pre-release stage. Let me know if you’re interested and I’ll mail it to you. Comments are welcome!
Did you know that you can actually suppress empty nodes for inbound flat files. If you have empty fields in a flat file and you don’t want them to end up as empty nodes in your XML instances generated from that, you can specify the attribute suppress_empty_nodes=”true” as part of the b:schemaInfo element in the flat file schema.
For generating empty elements in flat files if their XML counterpart nodes are not available in the instance, specify the attribute generate_empty_nodes=”true” as part of the b:schemaInfo element in the flat file schema.
