Hi
We are using ProDataSets and DataSets to exchange data between OpenEdge and .NET applications. The approach we use is to:
- Design the DataSet in Visual Studio
- Use BPROXSDTO4GL to create a .i to use with OpenEdge
- Use the serialise utilities in both .NET and OpenEdge to dump/load the dataset/prodataset
Before I load the XML from sent from OpenEdge into the .NET DataSet I attempt to validate it against the original Schema (XSD) and it fails for optional fields. If the field contains no value, OpenEdge writes out:
<BinEnclosed xsi:nil="true"/>
Which causes the XML to fail validation against the schema.
.NET just leaves the columns with DBNull value out when it serialises the DataSet.
This is because the Visual Studio DataSet editor does not support setting the nillable="true" attribute on the element definition (and if you put it in manually the editor will remove it next time you edit something).
This appears to be an incompatibility between the ProDataSet and DataSet.
Does anyone know if there is a fix or work aroung for it?
Thanks
Steve
We are using ProDataSets and DataSets to exchange data between OpenEdge and .NET applications. The approach we use is to:
- Design the DataSet in Visual Studio
- Use BPROXSDTO4GL to create a .i to use with OpenEdge
- Use the serialise utilities in both .NET and OpenEdge to dump/load the dataset/prodataset
Before I load the XML from sent from OpenEdge into the .NET DataSet I attempt to validate it against the original Schema (XSD) and it fails for optional fields. If the field contains no value, OpenEdge writes out:
<BinEnclosed xsi:nil="true"/>
Which causes the XML to fail validation against the schema.
.NET just leaves the columns with DBNull value out when it serialises the DataSet.
This is because the Visual Studio DataSet editor does not support setting the nillable="true" attribute on the element definition (and if you put it in manually the editor will remove it next time you edit something).
This appears to be an incompatibility between the ProDataSet and DataSet.
Does anyone know if there is a fix or work aroung for it?
Thanks
Steve