Hi,
We're currently using e-connect to integrate CW and GP. When attempting to transfer Procurement Items, We get the following error message:
Now, regardless of the error message the transfer goes through but is not recognizing the decimal places. If the quantity is 2 then GP reads 200 and so on.
Any clues as to what can be causing this issue? I reviewed a couple of forums looking for an answer but can't seem to get the workaround for it.
*This post is locked for comments
Yup, we verified the logs and they all seem to be passing the same values. We had a similar case with one of our sites, and at that time we fixed the issue by comparin MC40000 and dynamics..MC40200...but this time is not doing the trick for us.
That's weird, I think it is something to do with the Connect Wise acting differently for each user. May be you should check the Event Viewer to see if it is passing any values differently.
Thxs Srini, i will try that, but you know what's weird about this issue, that it happens to a few users. For instance I'm able to send information to GP without any issue. At first i thought of regional settings but then I verified the systems and set them alike and while my transfer was done successfully the user beside me got the error message.
Hello,
As Mariano suggested, have you tried by setting AUTOCOST property to zero in header and lines? In case If you don't have access to Autocost property from CW, you can set the default values in taPopRcptHdrInsertPre and taPopRcptLineInsertPre stored procedures.
Best,
Srini
Hi,
We still have issues with this error message. Now after the procurement transaction goes through and additional to the error message the quantity on GP are not right.
For instance, if the posted procurement had a quantity of 2 it will show 200 and so on.
Please HELP! i really need to get this fixed.
Hi,
I reviewed all regional settings towards my PC vs the one giving the issue and they are the same. Now, what I did as a test, is that I removed the unit cost from the purchase order and set it to 0.00 and it passed. What could the issue be?
Hi Mariano,
Per the engineer that's e-connect savy in our company, the issue is not autocost related, as Connectwise is not actually using it.
How likely is that to happen to 1 of our sites and the rest be working completely fine? Let me give you the entire scenario: We have 7 sites on different countries. So far we implemented the integration on 3 of them and we initially received the usual messages on certain fields (site name, class ID, etc).
Now, with our last implementation, we faced the issue exposed and we still can't determine if it's something with the regional settings on the workstations or if it's elsewhere the issue.
Regards,
You will want to set the AUTOCOST property to zero (0 - Manual) to force eConnect to use the values you are providing.
You should consider setting the AUTOCOST property on the header as well to zero. If you do this, you will want to set the SUBTOTAL property to zero so all your calculations are based on the line items you enter on the receipt.
I suspect the decimals issue is a direct result of not setting the AUTOCOST property, so make those changes and let me know if it works.
#1
André Arnaud de Cal...
291,391
Super User 2024 Season 2
#2
Martin Dráb
230,445
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
