InterWeave Help


How to Get Multiple Customer Ship To Address Using QODBC

When a customer has multiple Ship to Addresses, QODBC can only display only one Ship to Address which is set as the “Default” in QuickBooks.
How to Get Specified ShipToAddress in QODBC

Accessing QuickBooks remotely with the QODBC Connector

What is it?
The QODBC Connector is a distributable utility that connects calls from your InterWeave Smart Solution to your QuickBooks Company file (the database).

Managing Integration Timelines

How fast may I expect the Integration to be completed?
The integration timeline is at the customers speed — it is directly regulated by:
1. the quality and amount of your data, duplicates, special characters, loading historical data, etc., and the number of flows you have selected.
2. As we have over 100 flows and 300 configurable options to choose from, we recommend a phased approach so you may manage expectations.

How to Use Bulk Load Utility Flows in InterWeave Integration Manager

NOTE: Turn off Scheduled flows before starting Utility flows!!!
There are 2 types of Utility flows:
1. Bulk Load flows (with DR or DRS at the end of the flow name) DR = Date Range or DRS = Date Range & Size (Check radio button “Scheduled”)- for Bulk Load by period (Date Range) and batch size (S).
2. Single transaction flows (with N or NF at the end of the flow name) N = Name/Number (Check radio button “Single Run”) – for one time particular transaction sync or testing (Account/Opportunity/Product/Quote… etc.)

Adding a sub-folder in MS Office to catch QODBC errors as they are generated.

The Salesforce accounts that are not bound will not be able to connect with their QB Customer counterpart, so a QODBC error message will be produced and sent to the SF User identified in their InterWeave Solution. In addition, when invoices are run for this SF Account, additional error messages will be produced (there is no customer).

Binding issues with your Salesforce Objects

Regarding that SO – I see that either Customer is not in QB or nor bound. I do not believe that Customer is not in QB – it is rather something is wrong with the binding. Please check the following:

  • 1
  • 2