Salesforce and Business Central
Accounts, contacts, orders and invoices kept in step between the CRM your sales team lives in and the ERP that bills the work.
Connector
Read and write your Business Central data without writing code. Cloud, Microsoft-hosted and on-premise installations all use the same connection.
Rapidi connects to Dynamics 365 Business Central through the Business Central OData connection. It reads and writes records, so customers, items and orders can move both ways. Cloud, Microsoft-hosted and on-premise installations are all supported, and the same connection also covers Dynamics NAV 2016 through 2018.
The short version: Business Central publishes the tables you choose as web services, and Rapidi reads and writes them over that channel. Nothing is installed inside Business Central itself.
| Records it moves | Anything Business Central publishes as a web service or an API page. Customers, items, orders and posted transactions are the usual set. The Customer Card, page 21, is the standard first one. |
|---|---|
| Direction | Both ways. Reading is supported, and so is writing, which covers inserting, updating and deleting records. |
| How records are matched | Chosen per transfer when you map the fields, so the same customer in both systems stays one customer. |
| How often it runs | On a schedule you set. The shortest interval depends on your plan, from one hour on Entry down to one minute on Unlimited. |
| Versions supported | Microsoft Dynamics 365 Business Central, Dynamics 365 Business Edition, Dynamics NAV 2018 and 2017 in full, and Dynamics NAV 2016 read-only. |
| Where it can run | Azure-based installations, Microsoft-hosted online deployments, and local installations on your own hardware. |
| How it signs in | A user name and password, or OAuth2 using an app key and tenant ID from your Azure Active Directory. |
| What you set up once | Publish the pages you want as web services in Business Central, grant consent to the Rapidi app, and copy the OData V4 URL into MyRapidi. |
Every Rapidi integration with Business Central on one side runs through this connection. These are the pairs we have templates for today.
Accounts, contacts, orders and invoices kept in step between the CRM your sales team lives in and the ERP that bills the work.
Companies, deals and orders shared between HubSpot and Business Central, so marketing and finance see the same customer.
Two Microsoft systems joined without custom development, so a quote in Sales becomes an order in Business Central.
Business Central runs in three different places, and the connector handles all three. What changes is whether anything is installed on your side.
| What you are comparing | Business Central in the cloud | Hosted by Microsoft | On your own server |
|---|---|---|---|
| How Rapidi reaches it | Straight to the OData endpoint | Straight to the OData endpoint | Through RapidiConnector |
| Installed on your side | Nothing | Nothing | RapidiConnector, a small piece of software on a machine that can see the ERP |
| Ports opened to the internet | None | None | None. RapidiConnector calls out, so nothing is opened inward |
| Set-up on your side | Publish the web services, approve the app | Publish the web services, approve the app | The same, plus installing RapidiConnector once |
| Direction of the data | Both ways | Both ways | Both ways |
A new OData connection arrives with a RapidiConnector already attached. If your Business Central is in the cloud and you want Rapidi to reach it directly, that connector is removed from the connection in one click.
In their own words
“We have worked with Rapidi for more than 10 years. They connected our Salesforce to NAV 2018, and when we migrated to 365 Business Central, I did not have to worry about the integration. Rapidi handled it.”
That is the case this connector is built for. The mapping was written once against NAV, and the upgrade to Business Central re-pointed it rather than rebuilt it, because the records being mapped are the same records.
The full connector list, from Dynamics and Salesforce to SQL Server, Oracle and plain REST.
Four plans, priced per subscription rather than per connector. Adding Business Central does not change the licence.
What changes in an upgrade, what carries across, and how long it usually takes.
Tell us which version you run and where it runs, and we will say plainly whether this connector covers it.
Yes. Business Central is reached through the Business Central OData connection, and the transfer is configured from a template rather than written as code.
Both. Reading is supported, and so is writing, which covers inserting new records, updating existing ones and deleting them.
Microsoft Dynamics 365 Business Central, Dynamics 365 Business Edition, Dynamics NAV 2018 and Dynamics NAV 2017 in full. Dynamics NAV 2016 is supported read-only.
No. You publish the pages you want as web services and approve the Rapidi app. If Business Central runs on your own server, a small piece of software called RapidiConnector goes on a machine that can see it, and that machine calls out rather than accepting connections in.
With a user name and password, or with OAuth2, where the password is the key from an app registered in your Azure Active Directory and the domain is your tenant ID.
On a schedule you set. The shortest interval comes from your plan, from one hour on Entry down to one minute on Unlimited, and different record types can run at different frequencies.
Nothing on its own. Rapidi is priced per subscription plan rather than per connector, so adding Business Central does not change the licence.
Tell us the version and where it runs, and we will tell you plainly whether this connector covers it and what the setup involves.
Tell us which systems you run and we will tell you plainly whether Rapidi is the right tool.
Free, 17 pages
How the integration is built, what the RapidiConnector secures, the pre-configured templates, and the eight transfers most customers start with.