Integrate Salesforce ➡️ QuickBooks Online in 33 Minutes | 2024
Вставка
- Опубліковано 9 лип 2024
- Interested in consulting? www.1sync.co/contact
-----------------------------------
In this video, we discuss how to configure QIME (QuickBooks Integrations Made Easy), a Salesforce / QuickBooks Online Integration. QIME allows Salesforce Orgs to create invoices from opportunities, sync invoices from QuickBooks Online to Salesforce, sync payments, create customers from accounts, and more. We go over examples of how companies can use QIME to supercharge their Salesforce implementation, how to configure the appexchange package and install QIME, and how to schedule and bring over all QBO data.
-----------------------------------
Source Code: github.com/jawills/QIME
Write Up: www.1sync.co/integrate-quickb...
Export QBO Products: • Export ALL QBO Data fo...
QBO API: developer.intuit.com/app/deve...
Chapters:
0:00 Intro
1:53 Demo
3:44 Initial Configuration
7:40 Authentication Using Named Credential
17:33 Syncing Customers
21:43 Syncing Products
22:37 Using One Line Item Per Invoice
24:49 Syncing Invoice Terms
26:52 Syncing Invoices
30:05 Schedule Invoice Sync
31:00 Syncing Payments - Наука та технологія
Looking to get the latest version of QIME? Check out the link here: www.1sync.co/qime-sign-up
Additionally, this project is a free, open-source project, so feel free to make suggestions on what you need here: github.com/jawills/QIME
For those reading the document online (and watching this video), this needs do this instead of what is written creating the external named credential:
1.
The name should be "QB_External_Credential" not "QB External Credential"
2.
The "Authentication Provider" should be 'QB Auth Provider' instead of 'QBAuthProvider', which matches the name we gave the Auth. Provider
3.
"Permission Set Mapping" is no more. It has been replaced with "Principals"
a. Create a principal
b. Authenticate
c. Open the permission set
d. Assign the principal to the permission set
e. Save
If only you could integrate QB Desktop with SFDC in 33min... QB Web Connector causes pain for Lone Wolf Admins everywhere. Great video though - will keep it bookmarked in case this company ever gets a clue.
Unfortunately the QB Desktop and QBO API specs are completely different. A lot of companies I work with migrate from QB Desktop to QBO. This is not a small task and I know there are quite a few differences in the way the two softwares function.
Does invoice have to be created from an Opportunity or could I modify it to be created from a Custom Object?
The default automation creates the invoice from the opportunity. It is not required to relate an opportunity to the invoice object so you can build your own automation to create the invoice object
Fabulous! It works as needed. Justin thank you for doing a great job of showing us to to install, implement, configure and operate QIME. I am working on a shoestring budget no and this solution has saves us a lot of money. It has also showed me that Justing and G2Technologiesare knledgable and can get customer integrations done well. we will be moving forward with them for more complex integrations
Thank you very much for this content. I have a question at 15:45. If only one company can be connected to a quickbooks account, what is the workaround for testing this in sandbox environment then moving it into production?
Yes good question! When you have two qbo accounts, where one is a sandbox qbo account and one is a production qbo account, then you can test as you would expect in your sandbox/prod environments in Salesforce. This is because the routing to the correct QBO environment is done through the QB app's client / secret.
If you have multiple production QB accounts under the same email, you would either need to create a different user to authenticate the integration to, or change the email associated with that production account.
Hi Justin, thank you. How do you get the Memo across? e.g. if you want to put the Opportunity ID on the Memo in QB? I tried to just fill it in on the invoice but it isn't syncing to the QB side. Maybe I am misunderstanding how to map the other Invoice fields (in SF) to QB fields?
Hi,
I just pushed an update that fixes this, please install the latest version. Populating the 'Memo' field will push this information to QB.
@@JustinWills Hey justin, thanks so much. I'll look into this. On the Product side - are there any plans to include Inventory Price and/or Quantity On Hand from Quickbooks to sync to Salesforce?
@@MikeC-sf8vk I am looking to add support for product syncing next. If you make issues on Github I will prioritize that functionality.
Thank you very much@@JustinWills
@@MikeC-sf8vk I just added this functionality. Please check it out! Thanks for suggesting!
I was wondering if there is a way to go deeper on the product ID. I see that you can set the default, but what would I do if I wanted to be able to select a different service for the invoice instead of the default concrete. Is there a similar way to sync the service items like you did for the terms?
I also am getting "null null" on the shipping and billing address on the quickbook's invoice. Is this because there are multiple fields for the address in Salesforce, and just one field for it in quickbooks?
I'm not sure what you mean for selecting products. Do you use opportunity products?
For defaulting terms, you can set a default on the field in Salesforce
For the "null null" address, this was an issue fixed in the latest release. Please use the following link to find the latest version of the package for your environment: github.com/jawills/QIME
@@JustinWills No, sorry, I mean for creating multiple options for selecting a product/service for my invoice. For instance, when I go into custom metadata types and manage records on QIME Configs doesn't that default your invoice line item to just one service? I was wondering how the user could select a different service from the Invoice page Layout and see that reflected in Quickbooks.
Oh nice, that's awesome!
@@andrewmendonsa8962 Your interpretation of how the QIME config works is correct. If you want users to select the product, you can use the opportunity products to select a product, then when an opportunity is closed won an invoice will be created with your desired product.
@@JustinWills Cool, I am still having a little bit of trouble with it. I set up a product with it linked to it's respective QB Id, but the line item doesn't populate in Quickbooks. I did notice that it is able to populate in Salesforce on the invoice line item when I am syncing from Quickbooks to Salesforce. I noticed in the video at 29:27 that the product line item defaults to "services" despite setting the qime config default at 24:43 to line item 3 which should have been concrete. Is this a potential bug or am I missing something? Thank you very much for this, just looking into this as a potential use case for a non profit in my area
@@andrewmendonsa8962 The timestamps you listed are recorded at separate times so the sync of a single line item is not featured in the video.
Send me an email at justin@1sync.co and I will look at the configuration you have.
the QB_Auth_Provider type is no longer available
What part of the setup stage are you running into this? When creating the Auth. Provider the type is QBAuthProvider.
@@JustinWills Yes, while trying to choose this type it is no longer an available option to choose from
@@andrearojas2038 Email me here: justin@1sync.co and I will investigate for you
I am getting below error when I try to create an invoice 😮💨
Please use the existing Invoice
Error is in expression '{!createInvoice}' in component in page qime:opportunityvf: (qime)
An unexpected error has occurred. Your solution provider has been notified. (qime)
Are you creating an invoice from the opportunity? There is a limit of 1 invoice per opportunity, which is why this error occurs
@@JustinWills yes I am creating invoice from opportunity. And when I click Create Invoice w/ QB, I got this error,
The callout couldn't access the endpoint. You might not have the required permissions, or the named credential "QB_Named_Credential" might not exist.
Error is in expression '{!syncQB}' in component in page qime:qbcreateinvoicevf: (qime)
An unexpected error has occurred. Your solution provider has been notified. (qime
@@Zshafique1 Hi,
This is because the permissions for the named credential are not configured correctly. You can read more in depth here: www.1sync.co/salesforce-named-credential-example
To ammend ensure that:
1. The Name Credential API Name matches in the UI and in Apex code.
2. The named credential principal access to a permission set and assigned to a user.
3. The if the named credential is from a managed package, ensure Allowed Namespaces for Callouts includes the package namespace.