So are you saying that this table can no longer be updated?
From the first response, I thought that just running populate once would solve the issue, so I did remove the integration from QB, relink them, and then populated the databases before syncing.
Only using Populate is not an acceptable option. From your website, your software is designed to: “to perform a QuickBooks sync to and from an external database”. If we are only allowed to use Populate to avoid errors, then it is not a to and from service.
In addition, a huge issue with that solution is it take SIGNIFICANTLY longer to run a populate action than a sync. But more importantly, the entire purpose of the integration is to be able to push information from our web application into Quickbooks, if we can only populate it completely defeats the purpose of using OpenSync!
Log files are attached. I ran the “Force” tasks starting the evening of the 25th. The Force tasks populate from QB to the MySQL Databases. The “Sync” tasks do the bi-directional sync back and forth between QB and the MySQL databases.
I spent about 3 hours last night opening each of my client QB files, removing the application integration, went back in and reauthorized each of the files, and then let it spend all night going through and repopulating all of the QB files. I just did my first set of full syncs and came back with 344 errors between all of my companies with the same error of “This feature is not enabled or not available in this version of QuickBooks.”
I’ve been waiting for 2 weeks for a response on this issue. This is continuing to cause numerous problems. Any updates?
The only log file I see is the one attached, but it doesn’t seem to have much information. If there is a different log file you need, please explain where I would find it and I would be happy to send it.
This is still a problem, and turning into a larger problem for us. Open Sync / QuickBooks is no longer updating the billpaymentcheck table, and therefore changes to transactions are getting missed.
The situation most often occurring is that we are using OpenSync to integrate our web application with Quickbooks. Our web application also integrates with Bill.Com. Bill.Com pays a bill, our web app pushes it into QB. However, for large transactions, bill.Com will confirm the payment today, but not assign a check number until tomorrow. So temporarily we put the check into QB with a placeholder in the reference field. Then tomorrow or the next day, Bill.Com will give us the check number, and we need to turn around and update the billpaymentcheck table with the reference number, but now because of this error, it is not getting updated, so many transactions are showing up in QB without proper reference numbers.
Plus, if anyone makes changes to something on our web app, those changes are not getting synced over to QB.
Is this a QB limitation in 2020 or something that OpenSync needs to fix, and if it is OpenSync, when will it get fixed?
Is there a way this could get fixed in your software? Our workflow requires that we go through all of the errors and double-check to make sure things are correct or if we need to fix anything, and I’m getting 60+ of these errors a day that I need to deal with.
Then why are you still advertising it as a feature of version 3.0 on your homepage? See https://synergration.com/software/opensync/
This is false advertising!
This really is unacceptable. I was told in November of 2017 that this functionality was supposed to be working (See https://synergration.com/forums/topic/identifying-new-id-after-syncing/). We’ve been waiting for over a year and a half to get this feature and you continue to advertise it as a feature of your newest version. This is not only extremely disappointing but also false advertising and terrible customer service.
Have you found a solution to this, as I’ve run into this issue as well. Thanks!
I’ve run into this issue as well, and would love to see a solution if you’ve found one?
Support — PLEASE provide some support on how we can match these more accurately. There must be a simple way to do this.
Synergaration Support — do you have any additional details about how/if/when the TxnID or ListID numbers numbers could be change?
That might work for Vendor, but it wouldn’t work well for a bill or a check. For example, I ran into a problem last night where after my web app inserts a bill record, it then tries to match the bill based on vendor and amount, but there were two bills with the same vendoer and amount, so later, when it tried to push in the billpaymentcheck, it failed because it was trying to apply it to the wrong bill, which had already been paid.
I have been linking things together using the TxnID or the ListID, but if those could potentially change at some point in the future, this is going to cause cascading errors of this sort in the future.