--- title: "Dynamics 365 and SQL Server firm releases vs forecasts" description: "Dynamics 365 forecasts and firm releases reach SQL Server as separate categories with plant, part, period and version kept, so totals stay explainable." canonical: https://www.stacksync.com/blog/automotive-dynamics-sql-server-firm-release-forecast last_modified: 2026-09-18 --- # Automotive suppliers: separate firm releases and forecasts in Dynamics and SQL Server > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md A planning view that shows forecast, requested and accepted quantities side by side, with the accepted total explained from documented customer rules rather than a SQL sum. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 4 min read DATA ENGINEERING ## The operating decision An automotive supplier’s Dynamics-to-SQL Server planning view should preserve whether a quantity represents forecast context, a requested release or an accepted commitment. Keep customer plant, part, period and version in the identity. Two-way sync should transport the selected records without changing their demand meaning. A consolidated dashboard is useful only when planners can tell which numbers may drive execution and which require interpretation or approval under the customer’s agreed process. Explore the complete [automotive components integration and automation hub](https://www.stacksync.com/industry/manufacturing/automotive-components) for the systems and processes around this guide. ![Summary card: Dynamics 365 and SQL Server firm releases vs forecasts](https://www.stacksync.com/images/blog-highlights/icp-automotive-dynamics-sql-server-firm-release-forecast.webp) ## What this looks like in automotive components A supplier receives a broad demand outlook and separate near-term releases. A SQL report currently joins both to the same customer part and date bucket, then adds their quantities. The resulting total overstates demand and obscures a revised release that reduced the firm requirement. The improved model retains each source category and version, presents them separately, and shows the accepted planning view as an explicit business calculation. The team can compare outlook and commitment without accidentally manufacturing the sum of both. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Demand source | Customer operations | Retain the incoming document or record category and the meaning agreed with the customer. | | Plant-part-period key | Planning | Preserve the customer site, item reference and applicable time bucket or release identity. | | Source version | Integration operations | Record the version or sequence needed to distinguish current information from a late replay. | | Accepted planning interpretation | Planning | Keep the business-approved demand calculation separate from raw source quantities. | ![Record ownership diagram: Demand source, Plant-part-period key, Source version](https://www.stacksync.com/images/blog-diagrams/icp-automotive-dynamics-sql-server-firm-release-forecast.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Write the interpretation rules before the query Ask planning which source categories overlap, replace or supplement one another. Document the customer-specific convention. A SQL aggregation cannot determine whether two similar quantities are independent demand or different views of the same requirement. 2. 02 Preserve the source grain Model forecasts and releases at their actual line, period or schedule grain. Keep company and customer-plant context in the joins. Reconcile a small sample manually before broadening the dataset so duplicate joins do not become accepted planning totals. 3. 03 Select and test entity changes Identify the Dynamics entities carrying the relevant records. Test quantity, date and version changes independently, including child-level changes. If a source lacks reliable incremental coverage for the required field, define the approved refresh and freshness expectation explicitly. 4. 04 Publish an explainable planning view Show raw source categories, accepted interpretation and source age. Let planners inspect why a quantity is actionable. A proposed interpretation change should have an owner and effective scope rather than silently changing all historical comparisons. 5. 05 Validate replay and supersession Deliver an older version after a newer accepted one and confirm that the current view does not regress. Reconcile the selected period after a restart. Keep superseded source evidence available so the team can explain why the active commitment changed. ![5-step operating sequence: Dynamics 365 and SQL Server firm releases vs forecasts](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-automotive-dynamics-sql-server-firm-release-forecast.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Two sources cover the same date range Apply the reviewed customer rule; do not sum them simply because their labels differ. ### A plant code cannot be resolved Hold the affected demand for mapping review instead of assigning it to the default customer site. ### An older release arrives after a correction Retain it in history while protecting the newer accepted state from rollback. ## What to verify before expanding - Forecast and firm quantities remain separately visible before any business calculation. - The accepted planning total can be explained from documented source rules. - A late older version cannot replace the current accepted release. - Plant and period joins do not multiply the source quantities. ## Connect this process to the rest of your operation [Explore Stacksync two-way sync](https://www.stacksync.com/two-way-sync) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real demand source example and the exception your team handles most often, for example two sources cover the same date range. - [Dynamics 365 Finance and SQL Server two-way sync for automotive suppliers](https://www.stacksync.com/use-case/automotive-dynamics-sql-server-two-way-sync) - [NetSuite and Postgres two-way sync for automotive component evidence](https://www.stacksync.com/use-case/automotive-netsuite-postgres-two-way-sync) - [Automotive components: connect NetSuite shipments to Postgres lot evidence](https://www.stacksync.com/blog/automotive-netsuite-postgres-lot-shipment-traceability) - [Automotive component engineering cutovers: coordinate open demand and existing inventory](https://www.stacksync.com/blog/automotive-engineering-cutover-open-orders-workflow) - [Automotive supplier delays: build recovery plans around firm customer releases](https://www.stacksync.com/blog/automotive-supplier-delay-firm-release-recovery) - [Keeping Dynamics 365 Finance & Operations and PostgreSQL in Step](https://www.stacksync.com/blog/two-way-sync-microsoft-dynamics-365-finance-operations-postgresql) - [Bi-Directional Sync vs CDC Duplicates: Reliability Guide](https://www.stacksync.com/blog/bi-directional-sync-vs-cdc-duplicates-reliability-guide) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Microsoft: data entities overview](https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/data-entities) FAQ ## Frequently asked questions Should SQL Server be the authority for firm demand? Only if the business explicitly assigns that role. Often it is a projection of accepted application records with a separate planning interpretation. Can forecast changes trigger purchasing? That is a defined planning policy, not an automatic consequence of synchronization. Preserve the policy and approval boundaries governing the selected purchasing action. Which test prevents the largest misunderstanding? Use overlapping forecast and release quantities for the same plant and period, then revise one. Verify that the view follows the agreed interpretation rather than adding everything together. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [integration Dynamics 365 F&O and SQL Server integration](https://www.stacksync.com/integrations/dynamics-365-finance-operations-and-sql-server) - [connector Dynamics 365 F&O integrations](https://www.stacksync.com/connectors/dynamics-365-finance-operations) - [connector SQL Server integrations](https://www.stacksync.com/connectors/sql-server) - [platform Two-way sync](https://www.stacksync.com/two-way-sync) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Building-products manufacturing: build a Dynamics-to-SQL Server ready-to-ship view 4 min read read](https://www.stacksync.com/blog/building-products-dynamics-sql-server-ready-to-ship) [Data engineering Dynamics 365 Finance and SQL Server: keep manufacturing order lines current 4 min read read](https://www.stacksync.com/blog/manufacturing-dynamics-finance-sql-server-order-lines) [Data engineering Metal fabrication: link Dynamics order demand and material certificates in SQL Server 4 min read read](https://www.stacksync.com/blog/metal-fabrication-dynamics-sql-server-material-certificate-links) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)