eConnect is an essential tool for integrations to Dynamics GP. Please enhance and add to the target object set for new features and functions added to GP. This tool has not been enhanced for a long time.
Microsoft completely forgot about eConnect. It must need to improve add new schemas for other modules and screen.
e.g. BOM and Manufacturing module is completely missing from eConnect.
It is must to improve !
Have an additional eConnect method that will create the link between a sales order and a purchase order. So you use eConnect to create the sales order and the purchase order now we need one more method that will create the records in SOP60100. You can pass down the SO and PO numbers and this will find the lines and the headers and populate SOP60100. The current method does not behave this way.
Getting error message "Error Number = 6270 Stored Procedure= taRMUnapplyTransaction Error Description = Document number (DOCNUMBR) does not exist." with eConnect call for the taRMUnapplyTransaction where the invoice has the child customer number and Payment has national customer number.
It does not appear eConnect RMUnapply was designed to work with National Accounts. We had a particular requirement to register payments under a national account customer and apply those payments to customer invoices. We did not run into issues with the econnect methods of taRMCashReceiptInsert and taRMApply with national accounts. Also, the payment can be unapplied manually in GP. Therefore it was a surprise that the taRMUnapplyTransaction would not work with national accounts.
When working with National Accounts, taRMUnapplyTransaction econnect call would return one of the following errors:
1. Error Number = 6270 Stored Procedure= taRMUnapplyTransaction Error Description = Document number (DOCNUMBR) does not exist.
2. Error Number = 6293 Stored Procedure= taRMUnapplyTransaction Error Description = Apply document number does not exist.
3. Error Number = 8328 Stored Procedure= taRMUnapplyTransaction Error Description = There are no documents to unapply.
I've seen this request a number of times for the years but each time I go to check on it, it's gone.
It's not crazy to think that businesses need to be able to integrate returns in the same manner that they integrate receipts.
Please provide us w/ an out of the box eConnect integrate to integrate purchase returns!
The taRMVoidTransaction schema allows for voiding Credit Memos, Returns, or Cash receipts on the receivables side. It does not, however, provide functionality to void a debit memo. On the SOP side, eConnect provides the ability to void Invoices.
It would be helpful if eConnect also provided the same Void functionality for the Debit Memo document type in receivables. Currently, eConnect lacks this functionality.
We are able to apply receivables transactions with currency other than functional within the GP interface, but eConnect is unable to do the same. Improvement is needed within the eConnect procedures to handle the application of multicurrency documents of the same originating currency.