A build-to-order Business Central extension that connects Dynamics 365 Field Service / CE to your BC manufacturing data, so as-built BOMs, serial numbers, warranties and spare-parts inventory flow to technicians and service results flow back. Built, installed as a per-tenant extension, and supported by ECOSIRE. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $799.00 USD; request a quote for a scoped proposal.
示意预览A build-to-order Business Central extension that connects Dynamics 365 Field Service / CE to your BC
manufacturing data, so as-built BOMs, serial numbers, warranties and spare-parts inventory flow to technicians and service results flow back. Built, installed as a per-tenant extension, and supported by ECOSIRE.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
Manufacturers who service their own installed equipment usually run two disconnected worlds: production and inventory live in Business Central, while technicians, work orders and assets live in Dynamics 365 Field Service / CE on Dataverse. The result is re-keyed serials, guessed warranties, and spare parts that exist in the ERP but never reach the technician.
This extension closes that loop. ECOSIRE builds you a per-tenant AL extension on your Business Central environment that synchronizes the manufacturing context Field Service needs and writes service outcomes back into BC.
What it does: - Pushes as-built BOMs and serial/lot numbers from finished production orders into Field Service customer assets, so the technician sees the exact configuration shipped. - Tracks warranty and entitlement by serial number, derived from the production/sales date, so in-warranty vs. billable is decided automatically. - Links spare-parts inventory in BC items and locations to Field Service products, so parts availability and consumption are real, not estimated. - Creates a service-to-manufacturing return loop: a field replacement raises the matching return/repair document in BC. - Maintains an installed-base asset history that both systems can read.
Technically: AL table and page extensions surface the new fields and FactBoxes; event subscribers fire on production-order finish and posting; integration runs through the Dataverse virtual-tables / Business Central API (OData v4) rather than brittle CSV jobs; sync is scheduled on the BC job queue; access is governed by dedicated permission sets.
This is build-to-order, not an instant AppSource download. ECOSIRE scopes it to your entity mapping, builds it, installs it as a per-tenant extension, and supports it on your tenant.
Owns field technician productivity and first-time-fix rate at a manufacturer servicing its own installed equipment. Needs technicians to arrive knowing the exact as-built configuration, warranty status and available spare parts before they touch the machine.
Responsible for the BC environment and its extensions. Wants integration done as a clean per-tenant AL extension with proper permission sets, job-queue scheduling and error logging, not ad-hoc CSV exports or direct table writes.
Tracks warranty exposure and spare-parts revenue by installed unit. Needs entitlement decided automatically by serial number so in-warranty work isn't billed and billable work isn't given away.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Dynamics 365 Business Central 原生 |
|---|---|---|---|---|
| As-built BOM and serial sync from production to Field Service | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Warranty / entitlement tracking keyed by serial number | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Spare-parts inventory linked between BC and Field Service | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Service-to-manufacturing return/repair loop | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
| Built, installed and supported on your tenant (per-tenant extension) | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
| Mapped to your specific entity model (not a fixed schema) | 包含 | 包含 | 不包括在内 | 不包括在内 |
| Supported AL events / Dataverse / OData integration (no CSV jobs) | 包含 | 部分支持 | 部分支持 | 部分支持 |
| No in-house AL developer required to maintain | 包含 | 不包括在内 | 包含 | 包含 |
No. This is a build-to-order extension. ECOSIRE scopes it to your entity mapping and Field Service configuration, builds it as a per-tenant AL extension, and installs it directly on your Business Central tenant. There is no instant AppSource download for this product.
Typical delivery is about 3 to 5 weeks from the discovery call, depending on how many production-order, serial and warranty mappings you need and your Field Service / Dataverse setup. We install to a sandbox first for validation, then schedule the production cutover with you.
Every build includes a post-go-live support window for fixes and tuning. After that, ECOSIRE offers an optional support and maintenance plan covering Business Central monthly-release compatibility, Field Service / Dataverse schema changes, error-log monitoring and small enhancements. Because it is a per-tenant extension we own, we can patch and redeploy directly to your tenant.
Yes. Because we build to order, the field mapping is configured to your actual Dataverse tables and Field Service entities rather than a fixed schema. We integrate through supported APIs (Dataverse virtual tables / BC OData v4), so we adapt to your model instead of forcing you onto ours.
The extension is installed to a sandbox and validated before any production cutover. Sync is idempotent and writes through supported AL events and APIs with error logging and retry, never by raw SQL or direct table edits. Permission sets restrict who can see and change service and production data.
A build-to-order Business Central extension that connects Dynamics 365 Field Service / CE to your BC manufacturing data, so as-built BOMs, serial numbers, warranties and spare-parts inventory flow to technicians and service results flow back. Built, installed as a per-tenant extension, and supported by ECOSIRE.