(Resolved) Known Issue: ConnectWise SQL Error during Procurement/Inventory Sync

Status

Resolved

Issue

A ConnectWise SQL Error occurs when syncing Procurement / Inventory after applying the patch 58617.

How do we know this is an issue? Scroll down to see more information and for updates.

Version Affected

ConnectWise Manage Version v2018.6 (58617 - 58651) - > Current Version (2019.2).

What we're doing about it

We've logged this with ConnectWise. See updates below.

Updates

8 October 2018	Ticket logged with ConnectWise. #11033681 ConnectWise acknowledge receipt of issue. The error could be replicated by the ConnectWise Platform team and has been escalated to Development for correction.
10 October 2018	We've followed up ConnectWise for an update.
11 October 2018	ConnectWise have made an update in the backend and have asked us to see if the issue is resolved. If you have been affected by this error, please attempt Procurement Sync. Contact support@wise-sync.com if you're still experiencing the error.
15 October 2018	Partners reporting this error occurring on the latest v2018.6 patch (58651). It has been explained that error is caused by a problem with the GL Entries that were generated for the purchase order. A workaround has been provided, scroll down for more information. A permanent solution to mitigate the SQL Error has not been found.
16 October 2018	No update.
17 October 2018	Workaround provided, scroll down for more information. Expectations of when we should expect a permanent solution wasn't provided, we've chased this up.
24 October 2018	ConnectWise have not found the root cause to this problem, so cannot provide a permanent solution at this stage. We now have reports that the workaround provided by ConnectWise on the 17th October is not working in all cases. Contact support@wise-sync.com if you are experiencing this error. ConnectWise have asked us to advise them of partners that report the problem as they come through, which we will do as they trickle in, however we strongly recommend that if you are experiencing this error, that you contact ConnectWise Support quoting the ticket number #11033681 to follow up a permanent solution.
11 December 2018	ConnnectWise closed the ticket without providing a permanent solution. We've re-opened a ticket to chase this up.
2 February 2019	ConnectWise have advised that a fix for this issue is now in QA.
6 February 2019	Fix has passed QA. No date set for release just yet.
12 March 2019	Request for update, still impacting partners on v2019.2
9 April 2019	Request for update was submitted in a new ticket #11777110.
11 April 2019	We've been advised by ConnectWise that a fix is currently in Pilot (v2019.3). Once rolled out to general release, the error should no longer occur.