Good evening,
Please pardon my green'ness below. I do not know much about Accounting or GP.
I've been tasked with automating of my company's online products/services. At the moment we're using a hodgepodge of custom code wisked together with a few 3rd party tools. There is nothing other than the Web Services for GP Dynamics 2010 and/or eConnect service that I can repurpose.
So, I've created a Shopping Cart and a GP Item synchronizer that keeps our product offerings loosely coupled to GP. And, I can create a GP Sales Invoice and (after implementing my own eConnect WCF service) I can ask GP for the next available Document Number...so I don't have to make one up.
I've written custom code to create an Authorize.NET credit card transaction, passing in the SalesDocument Key.ID as the Invoice Number, and I am able to update the Sales Document in GP with the Authorize.NET Transaction and Authorization numbers.
Now then, I thought I was home free until I realized the Sales Document must be POSTed to GP prior to applying Payments. This is where I began to run into trouble. In order to understand how much "could be" automated, I POSTed the Sales Document and it's really no longer a Sales Document...it is a Receivables Invoice (I believe).
I can progammatically fetch the Receivables Invoice from GP (GetSalesInvoiceByKey(key, context)) and I attempt to apply a Payment to the invoice but this is where I begin to run into all manner of problems.
I was hoping someone could point me into the right direction with the following questions:
1) The GP Thick Client is capable of POSTing a Sales Invoice. Can I do this through eConnect? I would imaging the GP Thick Client is built atop eConnect. Or, is this simply an Accounting Security kind of violation to do this?
2) Can I programmatically apply a payment to a Sales Invoice prior to it being posted? How much crazy work would have to be done server-side to accomplish this?
3) What is the proper programmatic way of applying a payment to a POSTed Sales Invoice?
4) Does eConnect have any kind of "log all API calls" mode I can place it in so that I can understand how the GP Thick Client works when POSTing a Sales Invoice?
I ask these questions because I cannot seem to find any good resources online, in the product PDFs, or in the product print. Also, I'm scouring the Dynamics SQL database in an attempt to determine how posting is accomplished...but I'd rather stick with the eConnect API worse case.
Any direction would be greatly appreciated.
Thanks,
Don
*This post is locked for comments