Also notice how each parameter specifies the data type and size for that parameter. Set the default to a value that allows the document to be successfully created or updated in the Dynamics GP database.
When you specify input parameters, use the same type and size as the data field in the Dynamics GP database. The parameters also include two output parameters named @O_i Error State and @o Err String.
When you add your document type to e Connect, you need to create a SQL stored procedure that performs each of these steps.
To complete a create, update, or delete operation, the Dynamics GP Service framework sends an XML document to e Connect.
The use of this naming convention makes it easier to see how the input parameters are used in the stored procedure.
While not required, you should adopt a similar convention that makes it easier to update and maintain your stored procedure.
Add SQL statements that specify the name of the stored procedure, add it to the stored procedures of a Dynamics GP company database, and define the input and output parameters of the stored procedure.
The following sample shows how to create a stored procedure named sample Lead Create Update.This stored procedure is used when e Connect performs create or update operations for the IG_Lead_MSTR table (IG001).Notice the naming convention used with the input parameters.The XML document specifies the name of the SQL stored procedure and contains XML nodes that supply data for the input parameters of the stored procedure.To add a new document type to the Dynamics GP Service platform, you need to add SQL stored procedures that create, and update documents in the Dynamics GP database.The name of each input parameter specifies a data field from the IG001 table.