Salesforce Connector for Business Central

Recursos Principais

Bi-directional Account ↔ Customer sync with configurable field mapping and Salesforce ID stored on the BC Customer record via a table extension

Opportunity sync that converts closed-won Salesforce opportunities into BC Sales Quotes or Sales Orders

Quote-to-order automation — Salesforce quote lines mapped to BC sales lines with item and unit-price resolution

Inventory availability and price-list exposure pushed to Salesforce so reps quote against live BC item data

Invoice and payment status write-back from Posted Sales Invoices to the originating Salesforce record

Scheduled batch mode via the BC Job Queue plus near-real-time mode driven by AL event subscribers

OAuth 2.0 connected-app authentication to the Salesforce REST and Bulk APIs (no stored passwords)

Page extensions adding a 'Salesforce' factbox and sync-status fields on Customer, Item, Sales Order, and Posted Invoice pages

Dedicated sync log table and page recording every record, direction, status, and error for full auditability

Configurable conflict resolution, automatic retry with back-off, and per-entity enable/disable toggles

Dedicated permission sets so only authorized roles can configure or trigger synchronization

Setup wizard page for endpoints, mapping, sync direction, and schedule — no code edits needed to reconfigure

Feito sob encomenda, pronto para você

Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.

Você faz o pedido

Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.

Nós criamos e instalamos

A ECOSIRE cria, configura e instala no seu Dynamics 365 Business Central.

No ar + suporte

Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.

Sobre este Produto

The Salesforce Connector for Business Central is a per-tenant AL extension that ECOSIRE builds, installs, and supports on your Microsoft Dynamics 365 Business Central environment. It closes the gap between where your sales team works (Salesforce) and where your finance and operations team works (Business Central), so accounts, opportunities, quotes, sales orders, and invoices stay aligned without manual re-keying.

This is not an instant AppSource download. After purchase, ECOSIRE scopes your Salesforce objects and field mappings, develops the extension, and deploys it to your sandbox first, then production — installed as a per-tenant extension (or, where you prefer, packaged for your own AppSource private listing).

Under the hood the connector uses Business Central's REST/OData v4 APIs and AL event subscribers, paired with the Salesforce REST and Bulk APIs (OAuth 2.0 connected app). Integration runs through the BC Job Queue for scheduled batches and via event-driven triggers for near-real-time updates. We add table and page extensions to surface Salesforce IDs and sync status directly on Customer, Item, Sales Quote, Sales Order, and Posted Sales Invoice pages, plus a setup page, a sync log, and dedicated permission sets.

Typical flows: a closed-won opportunity in Salesforce becomes a Sales Quote or Order in BC; item availability and price-list data flow back to Salesforce so reps quote accurately; and when an invoice is posted and paid in BC, the payment status writes back to the originating Salesforce record. Conflict handling, retry/back-off, and field-level mapping are all configurable.

You get a documented, owned extension on your tenant — built around your actual process, not a generic template you bend to fit. ECOSIRE handles the build, the install, BC version-update compatibility, and ongoing support.

O que você ganha

A per-tenant AL extension (.app) installed to your Business Central sandbox then production, or packaged for your private AppSource listing if you prefer

Source code (AL project) with table/page extensions, event subscribers, API integration codeunits, and Job Queue setup

Configured Salesforce connected app guidance and OAuth 2.0 setup for secure API access

Field-mapping configuration covering your specific Salesforce objects and BC entities

Permission sets and a setup/configuration page for ongoing self-service adjustments

A sandbox UAT cycle plus production go-live, with admin documentation and a short handover walkthrough

Para quem é isso

Operations / Sales Ops Manager

Owns the handoff between sales and fulfillment and is tired of reps re-keying closed deals into Business Central. Wants opportunities to become orders automatically and accurate stock/pricing visible inside Salesforce.

Finance Controller

Needs invoice and payment status to reflect back in Salesforce so account managers stop asking 'has this been paid?' and revenue reporting reconciles cleanly across both systems.

IT Manager / BC Administrator

Responsible for the Business Central environment and wary of unsupported customizations. Wants a documented, permission-scoped per-tenant extension that survives BC update cycles and has a vendor on the hook for support.

Como Salesforce Connector for Business Central se compara

Critério	ECOSIRE	Construção personalizada	Concorrente
Built specifically for your Salesforce objects and BC process	Incluído	Incluído	Suporte parcial
Installed and supported on your tenant by the vendor	Incluído	Não incluído	Suporte parcial
Bi-directional account, opportunity, quote, order, and invoice sync out of scope-as-built	Incluído	Suporte parcial	Suporte parcial
Invoice/payment status write-back to Salesforce	Incluído	Suporte parcial	Suporte parcial
Inventory and price-list exposure to Salesforce	Incluído	Suporte parcial	Suporte parcial
Both scheduled (Job Queue) and near-real-time (event-driven) modes	Incluído	Suporte parcial	Suporte parcial
Survives BC updates via proper AL extension architecture	Incluído	Suporte parcial	Incluído
Source code and configuration handed over to you	Incluído	Incluído	Não incluído
Available instantly with no build lead time	Não incluído	Não incluído	Incluído

Perguntas frequentes sobre Salesforce Connector for Business Central

How long until the connector is live, and how is it delivered?

This is a build-to-order extension, not an instant download. After purchase we run a short scoping call to confirm your Salesforce objects, field mappings, and sync direction. Typical delivery is about 2 to 4 weeks depending on how many entities and custom fields are in scope. We develop and test in your Business Central sandbox first, run a UAT cycle with you, then install to production as a per-tenant extension.

What do ongoing support and updates include?

Support covers bug fixes, help with configuration, and keeping the extension compatible across Business Central's update cadence (the major/minor releases Microsoft ships). Because it is installed as a per-tenant extension on your environment, we can patch and redeploy without disrupting your data. We agree a support arrangement at handover; new features or additional Salesforce objects beyond the original scope are quoted as a small change request.

Does this sync in real time or on a schedule?

Both, and it is configurable per entity. Scheduled batch sync runs through the Business Central Job Queue at intervals you choose. Near-real-time sync is driven by AL event subscribers that fire when a relevant record is created or posted. Many customers run high-volume objects (like inventory and pricing) on a schedule and lower-volume, time-sensitive events (like a posted invoice's payment status) closer to real time.

How does it authenticate to Salesforce, and is it secure?

It connects through a Salesforce connected app using OAuth 2.0 — no usernames or passwords are stored in Business Central. Access to the connector's setup and sync actions is restricted by dedicated BC permission sets, and every sync operation is recorded in a sync log table for auditability. All Salesforce calls go over the standard REST and Bulk APIs.

Will this break when Microsoft updates Business Central or when we customize Salesforce?

Because it is built as a proper AL extension using table/page extensions and event subscribers rather than modifying base objects, it is designed to survive Business Central updates. We test against new BC releases as part of support. On the Salesforce side, field mapping is configuration-driven, so adding or renaming fields within your existing objects is usually a setup change rather than a code change; structurally new objects are handled as a change request.