Salesforce – InterWeave Help

There are two types of issues/errors related to: Data or Connection

WAHEED QAMAR — Wed, 29 May 2024 13:51:30 +0000

Data errors must be fixed by customer or by us (if company profile setup has issues). Connection issues are reviewed below.
The accounts without connection errors are running well, and wise versa. There is no need in analysing the accounts (customers) because we know what these permanent issues of the integration system currently are:

QUICKBOOKS DESKTOP

1. Quickbooks Desktop application/database is not reliable and crashing from time to time. The are a few reasons:

1.1 QB company file size is too big
1.2 QB installation was done “inaccurate”
1.3 QB file is corrupted (usually over time)
1.4 Intuit account login popup window in QB UI
1.5 QB Has stopped working/Unrecoverable/Fatal Errors (for unknown reasons)
1.6 QB Warning popup window “The system Theme Settings have changed…” (I have no idea how to suppress it)
1.7 QB software update popup window
1.8 QB user switches company file into exclusive use mode without stopping flows

2. QODBC Driver issues:

2.1 QRemote app is crashing for unknown reason from time to time
2.2 PING in QRemote (still happening after the fix but much less then before)

QUICKBOOKS ONLINE

Connection to Intuit server is lost from time to time (usually it fixes by itself)
Connection authorization is limited to 180 days and must be reconnected (sometimes the period is less or much less then 180 days for unknown reasons)

SALESFORCE

Usually, we have no issues with Salesforce connection if SF integration user’s password is not changed.

DR Utilities – Date Range Utilities from QuickBooks to Salesforce

WAHEED QAMAR — Tue, 28 May 2024 19:53:50 +0000

These settings would pick up Items from 01/01/2021 to 05/31/2021 (Put in next day to make sure we cover all of today).

The DR/DRS utility is used when you need to run a batch of a specific object. DR utilities are single run utilities that used for a small date intervals (couple of days top). DRS utilities are used to bulk load any amount of records. Parameters for both types are:

StartDate or StartDateTime – beginning of the interval (exclusive)
EndDate or EndDateTime – end of the interval (inclusive)
Return String (optional) – has to be ignored
Besides, DRS flows have additional parameter
BatchSize – number of records for one batch load
Recommended Batch Sizes may vary from 4 to 50 depending on record size
Also DRS flows must start with a value 0 in a Counter Column

For example to load invoices from 1/1/2021 to 5/31/2021 you can use QBInvoices2SFAcctOppDRS with

Batch Size 8
Start Date format of 2020-01-01 00:00:00
End Date format of 2020-05-31 00:00:00

These settings would pick up Items from 01/01/2021 to 05/31/2021 (Put in next day to make sure we cover all of today).

Repetition Protection and your InterWeave Flows

bmagown@interweave.biz — Fri, 22 Mar 2024 08:17:33 +0000

Repetition Protection and your InterWeave Flows

To avoid unnecessary processing of the same records in bi-directional sync we use a mechanism called Repetition Protection. All records, which are last updated in your CRM by the CRM User that is specified in the company profile, are skipped when querying your CRM for the records ready to be processed. This mechanism is included into scheduled flows and bulk load utility flows. It is not applicable if integration is unidirectional or the operations from your Financial Application to your CRM are set to None.

How to Move Changes from Sandbox to Production in Salesforce

bmagown@interweave.biz — Fri, 22 Mar 2024 08:16:59 +0000

Methods

There are several methods for moving changes from a Sandbox environment to a Production environment, and the best method depends on the nature of the changes and the type of software you are using.

Here are some common methods:

Change Sets: If you are using Salesforce, you can use Change Sets to move customizations, configurations, and data from a Sandbox environment to a Production environment. Change Sets are a collection of metadata components that you can package together and deploy to another Salesforce org.

Metadata API: If you are using Salesforce, you can also use the Metadata API to move changes from a Sandbox environment to a Production environment. The Metadata API is a set of APIs that allow you to retrieve, deploy, create, update, or delete customizations for your Salesforce org.

Version Control Systems: If you are using version control systems like Git, you can version your code in a Sandbox environment and then merge it with the Production environment using a pull request.

Manual Deployment: You can also manually deploy changes by copying the files from the Sandbox environment to the Production environment. However, this method is not recommended because it can be error-prone and time-consuming.

It’s important to thoroughly test changes in the Sandbox environment before deploying them to Production to minimize the risk of negatively impacting Production data or functionality. Additionally, it’s also a good idea to have a backup of the Production environment before making any changes.

Steps

The steps to move changes from Sandbox to Production in Salesforce:

Prepare the Sandbox: Make sure that your changes are thoroughly tested and ready to be deployed in the production environment.
Export the Changes: Go to the Setup menu, then select Deploy and Export the changes from the Sandbox. This will create a .zip file containing all the changes you have made.
Import the Changes: Go to the Setup menu in the production environment, select Deploy and Import the changes from the .zip file you exported from the Sandbox.
Review the Changes: Salesforce will show you a summary of all the changes that will be made in production. Review the changes and make sure everything is correct before proceeding.
Deploy the Changes: Click the Deploy button to move the changes from the Sandbox to production. You may need to schedule the deployment to take place at a specific time, or you can deploy immediately.
Monitor the Deployment: Salesforce will display the status of the deployment process, and you can monitor the progress of the deployment.
Verify the Deployment: Once the deployment is complete, verify that all the changes have been made correctly in the production environment.

Note: Always have a backup of your data in case of any unexpected errors.

Referrals:

https://developer.salesforce.com/forums/?id=9062I000000ILcUQAW

https://help.salesforce.com/s/articleView?id=sf.changesets.htm&type=5

https://youtu.be/jcBRFpzTdAY

Could you please provide us with a rough outline of the sequential steps involved in supporting Production Flows? Specifically, understanding the timing for actions such as binding, bulk loading, and data synchronization.

bmagown@interweave.biz — Fri, 22 Mar 2024 08:16:17 +0000

We will be walking the Customer through the steps in supporting Production Flows, as every meeting we have will be a Training Session. In our help.interweave.biz website – InterWeave Help – The SmartIntegration Platform for CRM – there is the Knowledge Base and the Documentation for the Solution. We will be working with the Customer to Register them (and any others), so access to the Salesforce_QuickBooks Solutions Help & Training Guide.

Regarding Binding, Bulk Loading and Data Synchronization, the first two are detailed in our 8 Step Document attached. Binding is done right prior to going to Production, as we bind Accounts in Salesforce with Customers/Vendors in QuickBooks. We include Bulk Loading of data from QuickBooks to Salesforce for the current year and will show the Customer to load History. The data loading is regulated by the number of Salesforce API’s available – we work with the Customer in creating this schedule. Data Synchronization is part of the discussion at the Flow level and is part of the discussion when enabling the Production Flows.

30/60/90 not updating in my SF Accounts

bmagown@interweave.biz — Fri, 22 Mar 2024 08:13:01 +0000

If you are running InterWeave Smart Solutions Professional or Small Business, you will need to click on the QBtoSFAccounts on the SF Home Page (under Integration by InterWeave – top left). Clicking on this link will bring over the 30/60/90 information. You should do this every day. If you are running InterWeave Enterprise or Ultimate – this is an automated function.

How to determine Time Zone Shift

bmagown@interweave.biz — Fri, 22 Mar 2024 08:12:07 +0000

Create a new test Customer in QB
Run QBCust2SFAcctNF flow to send it to SF.
Find out what QB LastModified timestamp is (in SF) and copy it.
Update Customer in QB (e.g. change or add phone number).
Run flow QBCust2SFAcctDRS switching it to single run mode (5^thcolumn in IM) and using the following parameters:
1. BatchSize – 5
1. EndDateTime – 2022-01-01 00:00:00
1. StartDateTime – Paste the QB LastModified from #3 removing .0 at the end so format should be exactly as in #b above (YYYY-MM-DD HH:MM:SS)
1. Check if QB Lastmodified in SF has changed. If yes – you are done and no Time Zone Shift required
1. If it has not change – reduce StartDateTime for 1 hour (e.g. if it says 11:43:56 make it 10:43:56) and run the flow again.
1. The number of attempts (#7) until QB LastModified changes is your Time Zone Shift. If for example you reduced StartDateTime 4 times – your time zone shift is 4. The biggest number I’ve seen is 22. If you made 22 runs and no luck – please stop the process and let me know.

Managing Integration Timelines

bmagown@interweave.biz — Fri, 22 Mar 2024 08:09:55 +0000

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:

the quality and amount of your data, duplicates, special characters, loading historical data, etc., and the number of flows you have selected.
As we have over 100 flows and 300 configurable options to choose from, we recommend a phased approach so you may manage expectations.

Phase 1. Data de-dup in Salesforce is Job 1. Salesforce allows multiple Account names (not unique). QuickBooks Customers are always unique—so you need to run your reports or exports, compare and match them to QuickBooks. Clean data allows for a very clean Integration. Look on the InterWeave Exchange for a vendor to assist. Phase 2. Connect your QuickBooks. We have worked with many Managed Service Providers who host customers QuickBooks and customers who have the QuickBooks Company file running on their own internal server (ex. MS 2012 or 2016 Server). We work with a QuickBooks hosting company—www.trapponline.com—whose price points are excellent, and they know the applications (Salesforce/InterWeave/QuickBooks) very well. We highly recommend them. Phase 3. Salesforce encrypted fields and API limits. If you have selected the InterWeave Payment Gateway, contact your Salesforce Sales Representative and ask to have encrypted fields turned on. Secondly, if you will be loading history into Salesforce or bulk loading Salesforce from QuickBooks, contact your Salesforce Representative and ask to extend you daily API calls to 50,000 per day for 7 days. This should allow time to load your Salesforce. Phase 4. Group your flows in a logical/process manor (Salesforce/QuickBooks/Salesforce). When building out your configuration, there are logical groupings that allow you to test quickly are:

Basic Integration. Accounts to Customers, Opportunities to Invoices and Products to Items.
Advanced Integration 1. Additional flows (Opportunities to Sales Orders, Receipts, Estimates, etc.).
Advanced Integration 2. Account to Vendors, Opportunities to Purchase Orders.
Additional files. Add and integrate multiple QuickBooks Company files.

This approach allows you to set expectations internally and gives all a working plan to measure by. Phase 5. Bind and move to Production. If you have selected bi-directional integration, we bind Accounts, Opportunities and Products in Salesforce to Customers, Invoices and Items in QuickBooks. Then we move you to production. You set the timing of the flows and your Solution runs 24/7/365. Phase 6. Monitor and Customise. Now that you’re in production, to add custom fields in Salesforce connecting to QuickBooks, log in, stop your flows and then select Edit Company File to connect custom fields in Salesforce that you have created to fields in QuickBooks. Support is available for all customers via our support site, email, phone and Zoom calls. If you are having an issue, we have a full library available at https://help.interweave.biz/ – register and review at your leisure. Welcome to the award-winning, InterWeave, the on-demand service designed for you to manage your Solutions, integrate with other systems, and even build your own Solution.

Change your Password in your InterWeave Solution

bmagown@interweave.biz — Fri, 22 Mar 2024 08:06:53 +0000

Change your Password in your InterWeave Solution

Here you go:

Open www.interweave.biz
Click on Customer Login link. Integration Portal will open.
Click on Edit Company Profile link (left bottom corner of the image).
Enter your credentials and click “Load Company Profile” button.
After profile is loaded click on “Next” button and navigate (using “Next” button) to the last page that has “Save and Finish” button.
Change the SF password on that page,
Click “Save and Finish”

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

bmagown@interweave.biz — Fri, 22 Mar 2024 08:00:28 +0000

Adding a sub-folder in MS Office

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).

As a first step, please create a sub-folder in your MS Office with a rule to collect error messages.

The rule.

You may need to create Iw_Alert01@Interweave.biz – Iw_Alert10@interweave.biz in your Contacts to support these email IDs.

This will contain all messages into a sub folder.

This is an example of an error.

Hello!

The following Error occurred during the execution of the Transaction Flow SFOpp2QBInvN:

2014-04-21 14:33:01.576 IW 2.41 TS SFOpp2QBInvN dmiller@.com ERROR XmlsqParams.statement

[QODBC] Error: 3000 – The given object ID “” in the field “list id” is invalid.

Initial Query Start Time: 2006-06-29 09:00:00.0 Final Query Start Time: 2006-06-29 09:00:00.0

Please take a look.

Regards,

Interweave Support