Method Community

Hi,

Just found that not only VendorCreditLineItem has this issue, but also CreditMemoLine has same issue. 

It has become a blocking bug to whole system, please come out a solution soon, or we can not turn on synchronization engine and that impact project schedule a lot.

--

Alex

Hi Alex,

Thank you for informing me of this. I have added to the ticket that this issue also exists for the CreditMemoLine table. I expect that this will be addressed at the same time. As always, I’ll keep you posted on any updates that I receive.

-Audisho

any update to these issues? Or, can you share something about it? How about giving us a ballpark estimate so we can decide to wait for your solution or find other solutions.

--

A

Any update?

We also found that RecordID of CreditMemo/VendorCredit/CreditMemoLine/VendorCreditLine will be modified after synchrinzing with QBs. Seems like you delete record in Method again and insert a new one? 

--

Alex

Hi Alex,

Thank you. I have also confirmed that the RecordID of the line is changed after the initial sync and have added this information to the ticket. 

As I have mentioned several times previously, I will post back here as soon as I receive an update. As of right now, I have nothing new to report.

-Audisho

Is it possible to disable integration engine to synchronize Credit Memo and Vendor Credit but still allow other transaction?

--

Alex

Hi Alex,

Yes, you can do this by changing your transaction history. Navigate to QuickBooks > Synchronize, select Show options per transaction type, change both Credit Memo and Vendor Credit to None and select Save Settings. Run a full sync for the changes to take effect. I hope this helps.

-Audisho

Hi Alex,

Good news! We deployed an update yesterday that corrected this issue. When a CreditMemoLine or VendorCreditLineItem record initially posts to QB, the RecordID is no longer being changed by the sync. This results in the custom field data being retained instead of lost.

Test this out and post back to let me know if you believe this to be still an issue.

I hope this helps.

-Audisho

Hi Audisho,

Sorry for late, it took me a while to remove some workaround codes to test. Everything now runs beautifully! Thank you and your teams.

Regards,

Alex