Share
Report
40Hi all,
I'm a nube when it comes to Dynamics but have been working on IBM AS/400's for over 20 years. I am managing the establishment of e-trading facilities for a client. The client is running Dynamics GP V.10 utilising SQL Server 2007 for the DB. Here's what we've done so far.
- We have setup e-connect to extract Invoice doc's from the Dynamics DB and send them as an XML message to an MSMQ on another server, which we refer to as the e-comm server.
- We have developed a little in house app which runs as a service and extracts the XML message from the MSMQ on the e-comm server and places the XML message into a text file in a folder.
- We then have a software app called TradeRoute by XMLYes, which handles picking up the message and forwarding it onto the relevant EDI service provider used by the trading partner in question, on the invoice.
This all seems to be working fine, the only piece of the puzzle missing is how we determine which invoice doc's to send, as not all customers will be utilising this facility!
We want to rollout the e-trading solution one business partner at a time. Currently, the SQL stored procedures established by the e-connect installation is sending every invoice document created to the e-comm server, regardless of customer.
We understand that e-connect offers a way to introduce some customisation via pre & post event mechanisms, which could invoke some custom code in the stored proc's to achieve what we want. However, before going and building a custom app the manage this, we were interested to know what other businesses have done to address this requirement.
Any information or feedback will be greatly appreciated!
Cheers!
*This post is locked for comments
All responses (
Answers (
