--- title: "Dynamics 365 and SQL Server material certificates by heat" description: "Join Dynamics 365 receipts and order demand to reviewed certificates in SQL Server by heat or lot, with quality acceptance kept as a separate state." canonical: https://www.stacksync.com/blog/metal-fabrication-dynamics-sql-server-material-certificate-links last_modified: 2026-09-18 --- # Metal fabrication: link Dynamics order demand and material certificates in 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 material-evidence view tells planners which received heat each certificate covers and which order demand uses it, so a file on record never stands in for a quality decision. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 4 min read DATA ENGINEERING ## The operating decision For metal fabricators, a Dynamics-to-SQL Server material-evidence view should connect order demand, received material and reviewed certificate references at the correct lot or heat grain. A certificate attachment is not proof that the material assigned to a job is approved. Two-way sync can keep selected records aligned, while quality retains authority over evidence acceptance. Preserve the material identity and review state before exposing a readiness indicator to planners or customer service. Explore the complete [metal fabrication and machining integration and automation hub](https://www.stacksync.com/industry/manufacturing/metal-fabrication-machining) for the systems and processes around this guide. ![Summary card: Dynamics 365 and SQL Server material certificates by heat](https://www.stacksync.com/images/blog-highlights/icp-metal-fabrication-dynamics-sql-server-material-certificate-links.webp) ## What this looks like in metal fabrication and machining A fabricator buys the same alloy from two suppliers and stores certificates in a shared document location. A planner sees a certificate against the purchase order and assumes every received bundle is covered. One bundle actually belongs to a different heat, and another document is still awaiting review. The operational view needs to show which received material each document supports and which demand uses that material. The goal is a traceable review queue, not an integration-generated assertion that a part complies with a customer requirement. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Material receipt | Receiving | Preserve item, supplier, receipt line and the recorded lot or heat identifiers. | | Certificate reference | Quality | Keep the source document location, supplier reference and material scope without replacing the original evidence. | | Evidence review | Quality | Record who accepted or rejected the document, when and for which material identity. | | Demand allocation | Planning | Link the material assigned to a job or order line without copying one certificate to unrelated quantities. | ![Record ownership diagram: Material receipt, Certificate reference, Evidence review](https://www.stacksync.com/images/blog-diagrams/icp-metal-fabrication-dynamics-sql-server-material-certificate-links.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Define the evidence relationship Ask quality which identifier connects a certificate to received material in this process. Record whether the relationship is one document per heat, receipt or another agreed scope. Avoid adopting a convenient file-folder structure as the business identity. 2. 02 Map receipts and demand separately Select the approved Dynamics entities needed for receipts, material identity and order demand. Build explicit relationships in SQL Server and preserve company context. Reconcile quantities before joining documents so a many-to-many join does not make one receipt appear to cover several independent lots. 3. 03 Expose reviewed and missing states Present document present, review pending, accepted and rejected as different states. A planner should see why readiness is blocked and who owns the next action. Keep the source evidence accessible to authorized reviewers without inventing a certification conclusion from parsed text. 4. 04 Test changed assignments and reviews Move an allocation to another recorded lot in the test process and verify that the evidence view follows the new relationship. Then reject a previously pending document. Confirm that derived readiness changes while historical assignments and decisions remain traceable. ![4-step operating sequence: Dynamics 365 and SQL Server material certificates by heat](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-metal-fabrication-dynamics-sql-server-material-certificate-links.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### One certificate covers several recorded lots Require quality to confirm its scope and represent the approved relationships explicitly. Do not infer coverage from similar supplier descriptions. ### The receipt lacks a heat identifier Route the material to the defined identification process and keep evidence readiness unresolved. ### A document is replaced with a corrected version Retain the superseded reference and review the new document’s applicable scope before updating the current evidence status. ## What to verify before expanding - An order line shows evidence for its assigned material rather than any matching item. - A missing heat or lot reference remains visible as an exception. - Document presence and quality acceptance appear as separate states. - Changing the assigned material changes the required evidence without erasing earlier review history. ## 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 material receipt example and the exception your team handles most often, for example one certificate covers several recorded lots. - [Salesforce and Acumatica two-way sync for metal fabricators](https://www.stacksync.com/use-case/metal-fabrication-salesforce-acumatica-two-way-sync) - [NetSuite and Postgres two-way sync for machining operations](https://www.stacksync.com/use-case/metal-machining-netsuite-postgres-two-way-sync) - [Metal fabrication: connect Salesforce quotes to Acumatica job-ready orders](https://www.stacksync.com/blog/metal-fabrication-salesforce-acumatica-quote-job-handoff) - [Metal fabrication outside-processing delays: route late returns to the right job owner](https://www.stacksync.com/blog/metal-fabrication-outside-processing-late-return-workflow) - [Machining drawing revisions: review a change against work already released](https://www.stacksync.com/blog/metal-machining-drawing-revision-released-job-workflow) - [How to Parse EDI Files Into a SQL Database](https://www.stacksync.com/blog/parse-edi-files-sql-database) - [Acumatica API Integration: A Practical Guide](https://www.stacksync.com/blog/acumatica-api-integration-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 Can automation verify the certificate’s technical adequacy? It can assemble evidence and perform defined checks, but quality must set the acceptance criteria and handle uncertain or consequential conclusions. Do not infer approval from an attachment’s existence. Why preserve legal-entity context in the SQL view? Receipt and order identifiers can overlap across entities. Context prevents a document or allocation from being joined to the wrong transaction. What should quality and planning measure about certificate evidence? Track time spent finding evidence, unresolved evidence age and incorrect material-document associations discovered during review. Do not report improved product conformity merely from faster document retrieval. 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 Automotive suppliers: separate firm releases and forecasts in Dynamics and SQL Server 4 min read read](https://www.stacksync.com/blog/automotive-dynamics-sql-server-firm-release-forecast) [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) ## 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/)