User error message:The system is reporting the following error:Document’s contents was not correct: Interchange syntactically incorrect. Bizlink

So, previously I laid out how to define the metadata for capturing data so you can search on it.

I learned something new. If perchance you are trying to capture some data from say a W05.

I had definitions for W0501, W0502

Then a partner sent some data in W0503

I figured it would just ignore the data since I wasn’t trying to capture it… nope. You need to define all elements that you might potentially get data sent on. Otherwise you will get the error “Document’s contents was not correct: Interchange syntactically incorrect.”

And there you have it, define all the things.


Bizlink, creating new doc types for tracking metadata

So for what ever reason bizlink is set up with some of the more common doc types say 850’s and 810’s etc… to grab the useful metadata and index so you can search on it…. but it neglects to do this for all types… seriously, it would not be hard for them to do this correctly. Anyways when you contact them about it, they so kindly refer you to their professional service$ dept.

So, I am going to try and tease it out on my own.

The manual is at least kind enough to let you know that the xml files live in


Clicking around the genst_GP looks as likely of a template as any for my 945, so I make a copy of it and rename it genst_945

I think the ST and SE should be boiler plate so I’m focusing more inside the ‘G01’

So instead of a G01 I want data from the W06


<Record Name=”G01″ Comment=”Beginning Segment for Invoice” MinOccur=”1″ MaxOccur=”1″ Optional=”M”>
<Element Name=”G0100″ Comment=”Segment Id” Optional=”M” Validator=”G01″ Saved=”SegmentName”/>


<Record Name=”W06″ Comment=”Beginning Segment for warehouse transfer advice” MinOccur=”1″ MaxOccur=”1″ Optional=”M”>
<Element Name=”W0600″ Comment=”Segment Id” Optional=”M” Validator=”W06″ Saved=”SegmentName”/>

Now looking at this line

<Element Name=”W0601″ Comment=”Date” EdiCode=”373″ Optional=”M” VisableAttrs=”EdiCode”/>

I need to change the EDI code to a 514 that I have in my edi spec for the W06

so becomes

<Element Name=”W0601″ Comment=”Reporting Code” EdiCode=”514″ Optional=”M” VisableAttrs=”EdiCode”/>


<Element Name=”W0602″ Comment=”Invoice Number” EdiCode=”76″ Optional=”M” VisableAttrs=”EdiCode” Saved=”SigId2″/>


<Element Name=”W0602″ Comment=”Depositor Order Number” EdiCode=”285″ Optional=”M” VisableAttrs=”EdiCode” Saved=”SigId1″/>

(Changed it to SigId1 since that is the Document Number 1 I want to populate)

So I’m going to continue this editing and then bring in a 945 and see if it does anything useful for me. (I also created the 945 doc type on the Setup / Doc Types screen and pointed it to /genst_945.xml)

Bizlink install process part 1

The Bizlink install was a very straightforward process and it took me about an hour to complete. Go to the download site



I choose the 64bit version. It was pretty much a next, next, next install. I choose BizLink, New Installation, and installed onto a single machine. If you were going distributed I think the install could get much more complicated 🙂 I accepted all of the default ports. I made a quick MS SQL database for it as well.

Next you need to install all of the various parts to run as a service, this is pretty easy you just go into the dir you installed bizlink, then app3.3.0\bin then do the below



Next, I had to license it. To do so you go to Setup > Licenses, Click Add, choose upload license file, and then give it a name.

One slightly tricky thing was I wanted to patch 3.3.0 to current. So I clicked on Software Patches, hmmm I see I think that’s what I want. I can never figure out if I have Bizlink or BizManager or whatever… anyways… hmm how to install. Oh yeah if I download BM_33017_Release_Notes.pdf  (that BM stands for BizManager and not bowel movement I guess) there are the instructions. Unzip the patch to /app3.3.0 and the go into /app3.3.0/bin/ and Run as Administrator on the installpatch.bat

Easy peasy. Next post, how to get AS2 up and running