Method Community

 

Sync of Finalduedate and GenericName

Last post 10-04-2018 9:05 AM by Laks_Method. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 04-26-2018 6:41 AM

    Sync of Finalduedate and GenericName

    Hi,

    We create salesorders from our Webshop via MethodAPI in method.

    They are synced to Quickbooks but two fields, FinalDueDate and GenericName, which we use as a workaround for various data, are not synced when the sync is done for the first time.

    As soon as I save the salesorder in method again (without having changed anything), the two fields are synced.

    Why are they not synced the first time and is there anything I can do about it?

    Regards,

    Dieter

  • 04-30-2018 2:10 PM In reply to

    Re: Sync of Finalduedate and GenericName

    Hello Dieter,

    Are you calling MethodAPIActionSendToDesktopV2 after populating data in FinalDueDate and GenericName fields for the respective SalesOrder? If not, doing so should solve the issue.

    Laks Sahayaprasath
    Product Manager
    Method CRM
  • 05-02-2018 3:58 AM In reply to

    Re: Sync of Finalduedate and GenericName

    Hi Laks,

    MethodAPIActionSendToDesktopV2 doesn't do the job proberly anyway. I found a post somewehere in the forum which says that it doesn't work properly with Quickbooks Desktop.

    And that is the experience we have, We get the data synced only when we update (any field of) salesorder after the insert of salesorder and salesorderline. (That somehow concludes the process of inserting a complete salesorder) And then it's 'only' a changes-only-sync, not a Push which syncs immediately.

    With this process we get method to sync the salesorder.

    But it doesn't sync these two fields I mentioned, only after saving the salesorder manually in method again. But they are definitely in the method table salesorder with the right values.

    Best,

    Dieter


  • 05-02-2018 12:44 PM In reply to

    Re: Sync of Finalduedate and GenericName

    Hello Dieter,

    MethodAPIActionSendToDesktopV2 does 2 things

    A. Setting up the record so that it can be picked up by the method integration engine with the next sync

    B. Pushing the record to Quickbooks

    We have an issue with Step B which you are working around by doing a changes only sync, but we still need MethodAPIActionSendToDesktopV2 to do Step A. Below steps should sync sales orders fine without going through the process of updating fields.

    1.Insert Sales Order

    2.Insert Sales Order Line

    3.Call MethodAPIActionSendToDesktopV2 for the SalesOrder RecordID

    4.Perform full or changes only sync (you could also wait for the next auto sync)

    If you are populating these 2 fields - Finalduedate and GenericName before Step 3, it should sync fine. 

    Laks Sahayaprasath
    Product Manager
    Method CRM
  • 10-04-2018 9:05 AM In reply to

    Re: Sync of Finalduedate and GenericName

    For anyone following this thread, the bug with MethodAPIActionSendToDesktopV2 for QuickBooks Desktop sync has been fixed. You should now be able to sync transactions real time with this endpoint.

    Laks Sahayaprasath
    Product Manager
    Method CRM
Page 1 of 1 (5 items)