Creating a Custom Serialization Assembly for eConnect for Microsoft Dynamics GP 2010

Chris Roehrich - Click for blog homepageThis is a reposting of an article Chris Roehrich originally wrote on my Developing for Dynamics GP blog.

The eConnect Programmer’s guide discusses creating a custom XML node and stored procedure so developers can process new types of data.   For example, a custom or 3rd party table could be updated when integrating a master record like a Customer or a transaction like a Sales Invoice using eConnect.   The strategy that I will discuss below is for developers out there that would like to go one step further by referencing their own custom assembly.  This assembly can be referenced in their Visual Studio project which would allow them to serialize the eConnect XML document with the custom node.

Continue reading

The Smartlist Builder GoTo won’t open my window

Patrick Roth - Click for blog homepageThis is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.

In a Microsoft Forums post a few days ago, an ISV had created a custom window and a table to store parallel data to the Item Serial Number Master table.

Her goal was to use Smartlist Builder (SLB) to make a Smartlist to show the GP & custom data in one Smartlist.  That part was successful.

The 2nd goal was to make a GoTo to drill back to the custom window to display the Item & Serial Number (her parallel key) and display the custom data that goes with it.

Continue reading

Serializing CDATA tags in eConnect XML Documents

Chris Roehrich - Click for blog homepageThis is a reposting of an article Chris Roehrich originally wrote on my Developing for Dynamics GP blog.

I had a recent support incident where the customer was trying to update a field to a blank value using the eConnect serialization assembly and the value was not being removed.  Specifically, they were attempting to remove the existing value in the ADDRESS2 column of the RM00101 table by setting the string value to a blank value.  The reason why this was happening was really by design with the eConnect stored procedures.   If you do not pass a value, eConnect will use the setup in Dynamics GP to default the value if one exists.   This works great because then as a developer you do not have to worry about passing everything in with the XML document.   That would be painful to have to pass everything in the XML document for being fearful of having data being removed.

Continue reading