Error: A result set from ConnectWise contains more than one purchase order.
This may indicate that orphaned records are being returned.
The batch could not completed/posted.
This error specifically relates to the results being returned from ConnectWise are validated against the expected number of transactions. On occasion ConnectWise results can be blended even through we process single record batches. Wise-Sync validates the records to ensure that the expected number of transaction lines are in the batch. If there are more lines than expected the batch is terminated for further investigation.
The following are listed as being the known reasons for this anomoly, and how you might look to resolve the issue.
| Issue | Error Resulting |
| When Posting a Purchase Order that has leading or trailing spaces. | A common issue is where the Packing Slip ID has an illegal character, or has leading or trailing spaces. These are not easily identifiable, we suggest that you complete the following: In ConnectWise > Accounting Interface Unposted Procurement: Review the Picking Slips listed in the results, to determine if two separate records are being presented with similar PO Slips.
Leading Spaces are more readily identifiable as they will be separated in the Unposted Procurement Window. You can see in the screenshot above, that there is a leading space before the "Slip: 132" as opposed to the result below. To Resolve the above issue:
Trailing Spaces: Trailing spaces are not easily determined, as ConnectWise removes the trailing space from the unposted records, however when we compare the list against transactions in a PO, the results differ: To Resolve the above issue:
|
| When posting a Purchase order where a SlipID contains the longer '–' rather than '-' | Applies also to Error: ConnectWise has returned an incomplete record for When copying and pasting from word, the longer – will cause an error when records are being processed through the ConnectWise Accounting Interface. To resolve the issue, the Packing Slip ID needs to be updated for all items received so that the longer dash (–) is replaced with a standard hyphen (-). |
| When posting a Purchase Order where the SlipID contains a special character such as an & | When special characters are used in a Packing Slip ID such as an & can result in the batch failing for all purchase orders or invoices as the return string breaks the HTML request for the batch. To resolve the issue, open the Purchase Order or Invoice and remove the special characters. Special characters that are known to cause issues include:
|
