Skip to main content

Creating a Custom XML Node in an Existing eConnect Schema

by Gloria Braunschweig
President, Dorian Enterprises, Computeration, Inc.

This is the fifth in a series of articles covering eConnect for Microsoft Dynamics GP.

In this article we examine creating our own custom XML nodes for eConnect. This ability greatly enhances the potential to extend the current business logic within eConnect by allowing the creation of completely new procedures within an eConnect document type.

The creation of a new XML node consists of three steps:

  1. The creation of new stored procedure code containing the business logic that we wish to add to eConnect.
  2. Inserting the new stored procedure logic into the existing stored procedure
  3. Adding a new XML node to an eConnect schema that will utilize the new stored procedure.

For this week's example we will add an XML node to the RMCustomerMasterType schema which will store an IP address in a custom SQL table along with the corresponding customer ID. We utilized that schema in part 2 of this series of articles to capture the IP address from our e-commerce site.

Step 1 - Create the Stored Procedure used by the new XML node.

When creating ...

FREE Membership Required to View Full Content:

Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

About Gloria Braunschweig

Gloria has experience across the full spectrum of business operations and management. Decades of experience are documented in the book Rapid Implementation, establishing Gloria as a specialists using Microsoft SQL tools for implementation, integration, and business intelligence related to Microsoft Dynamics GP.

Gloria writes and presents on lean implementation concepts and business management systems for small and mid-size businesses.