Pervasive DataSolutions Logo

Difference Between Sync With Quickbooks Button and Scheduled Datasync?

Last post 02-22-2010 2:51 PM by nmendlik. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 02-22-2010 2:45 PM

    Difference Between Sync With Quickbooks Button and Scheduled Datasync?

    Answer

    In regards specifically to the scope of one account or opportunity, is there a limited amount of information synced when using the "Sync to Quickbooks" button versus running a datasync session.

    I am running some tests, and I have a lot of data cleansing to do, so I dont want QB and Salesforce to completely run right now.  Therefore I have kept Datasync setting to NEVER.  However, for the purposes of testing the integration I am using the only the Sync To Quickbooks.  While the hidden key fields like Transaction TXnID are showing back into salesforce none of the other fields as you outlined in the field sync guide are coming back.

    For example in a opportunity invoice set to closed/won, I have pressed the "Sync To Quickbooks" button.  All the following fields DID NOT sync:

    Invoice Number, Shipping Address, Billing Address, Ship Method, QB Total Amount, Ship Date, Terms Code......

    Please provide clarification.  Thanks

  • 02-22-2010 2:51 PM In reply to

    Re: Difference Between Sync With Quickbooks Button and Scheduled Datasync?

    Answer

    When you use the button, it will only sync that specific record. The Transaction TXnID as well as the QB Transaction Date should return. The others return the next time that the full sync from QB to SFDC runs. So, you will see that information come back but not until you complete a sync from QB to SFDC.

Page 1 of 1 (2 items)

Copyright © 2009 Pervasive Software, Inc. All Rights Reserved. All Pervasive brand and product names are trademarks or registered trademarks of Pervasive Software Inc. in the United States and other countries. All other marks are the property of their respective owners. Your transaction secured by high-grade AES-256 encryption.