Specification question

In the CLP segment for our 835 files, our provider is not including a value for the Monetary Amount that is Reference = 05. Their documentation lists this as a situational field, and the XML for this field is written as "<CLP05 />" if no
value is supplied. However, in the Ansi-5010Specification.xml file, the type is listed as "R" with a MinLength of 1. As a result, the CLP table created includes 05 as a decimal field, while our XML is passing in a blank string and throwing an error.
Before changing anything on the Ansi-5010Specification.xml file, I wanted to make sure that this was working as expected.

Good catch. None of my test data had that scenario. I have added
changeset 25710 that will fix this. It will push null into the field when the field is a decimal type and the x12 has an empty value. I should have another release in the next week after I get some other changes finished.

Thanks for making this change! I am having a similar problem with the CAS segment for our 835 files. Most of the time, our provider is giving us CAS01, CAS02, and CAS03 only. That works fine since everything after that is optional. However in a few cases,
we are receiving values for CAS05 and CAS06, as well. In those cases, we have the XML for CAS04 written as "<CAS04 />" as no value is supplied. We have the same problem with errors as we did with CLP because the code interprets this value as
a blank string being entered into a decimal field. From your reply, I assume the change will fix this as well.

One last quick question: is the source code the same code as for the latest version of the dll? I am able to import our files (with a few temporary tweaks to the tables after they are created) using the code I downloaded from the source code tab. However, I
am getting an error when I use the latest dll. Some of the data is entered, but not really any from the various segments from what I can tell. The error is a SqlException with the following message: