Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Recorded 4 Nov 2026 at 13:26 UTC. This is what ChangeIntel recorded, including the title, summary, facts and links. It is not a statement of the source's current position. See the latest record.

Dynamics 365 Business Central: Adapt faster with Power Platform - Map new Dataverse fields in Business Central

This feature simplifies how administrators keep Business Central and Dataverse aligned as Dataverse schemas evolve. Previously, exposing new or existing custom Dataverse fields required creating or updating a table extension (PTE) in the integration layer. Based on partner and customer feedback, this update removes that dependency.

What it said

Roadmap ID
573365
Status
Launched
General availability target
Not stated
Preview target
Not stated
Products
Dynamics 365 Business Central
Clouds
Worldwide (Standard Multi-Tenant)
Release phases
General Availability
Platforms
Web
Added to the roadmap
30 Sep 2026 23:31 UTC
Last changed
30 Sep 2026 23:31 UTC

Source evidence when recorded

merill-message-center-archive
Complete at observationRead 4 Nov 2026 at 13:06 UTC

Coverage describes the sources at this observation. A complete read then does not establish their current position.

Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (46)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 4 Nov 2026 · 13:26:53 UTC General availability targetOctober CY2026 → Not stated
  2. 4 Nov 2026 · 13:26:53 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  3. 4 Nov 2026 · 13:26:53 UTC Source coverage: merill-message-center-archiveCurrent
  4. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  5. 4 Nov 2026 · 13:26:53 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573365 → No longer listed in this observation
  6. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items
  7. 4 Nov 2026 · 13:26:53 UTC SummaryThis feature simplifies how administrators keep Business Central and Dataverse aligned as Dataverse schemas evolve. Previously, exposing new or existing custom Dataverse fields required creating or updating a table extension (PTE) in the integration layer. Based on partner and customer feedback, this update removes that dependency. When a new field is added in Dataverse—such as a custom field in Dynamics 365 Sales—you can now map the field directly from the Integration Table Mappings page. You can refresh the Dataverse field list, add the field to an existing mapping, select the corresponding Business Central field, define the synchronization direction, and enable it for data synchronization. Once enabled, the field participates in sync without modifying extensions or recreating mappings. This enhancement reduces configuration overhead and supports faster adoption of custom Dataverse fields, especially for organizations that frequently customize their Dataverse environments. Business Value: As an administrator, you can map newly added Dataverse fields without recreating table extensions or writing code, reducing configuration effort and supporting faster adoption of custom fields… → This feature simplifies how administrators keep Business Central and Dataverse aligned as Dataverse schemas evolve. Previously, exposing new or existing custom Dataverse fields required creating or updating a table extension (PTE) in the integration layer. Based on partner and customer feedback, this update removes that dependency.
  8. 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  9. 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → October CY2026
  10. 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  11. 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
  12. 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items → No longer listed in this observation
  13. 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  14. 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573365
  15. 4 Nov 2026 · 11:04:04 UTC SummaryThis feature simplifies how administrators keep Business Central and Dataverse aligned as Dataverse schemas evolve. Previously, exposing new or existing custom Dataverse fields required creating or updating a table extension (PTE) in the integration layer. Based on partner and customer feedback, this update removes that dependency. → This feature simplifies how administrators keep Business Central and Dataverse aligned as Dataverse schemas evolve. Previously, exposing new or existing custom Dataverse fields required creating or updating a table extension (PTE) in the integration layer. Based on partner and customer feedback, this update removes that dependency. When a new field is added in Dataverse—such as a custom field in Dynamics 365 Sales—you can now map the field directly from the Integration Table Mappings page. You can refresh the Dataverse field list, add the field to an existing mapping, select the corresponding Business Central field, define the synchronization direction, and enable it for data synchronization. Once enabled, the field participates in sync without modifying extensions or recreating mappings. This enhancement reduces configuration overhead and supports faster adoption of custom Dataverse fields, especially for organizations that frequently customize their Dataverse environments. Business Value: As an administrator, you can map newly added Dataverse fields without recreating table extensions or writing code, reducing configuration effort and supporting faster adoption of custom fields…
  16. 4 Nov 2026 · 10:01:18 UTC General availability targetOctober CY2026 → Not stated
  17. 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  18. 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
  19. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  20. 4 Nov 2026 · 10:01:18 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573365 → No longer listed in this observation
  21. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items
  22. 4 Nov 2026 · 10:01:18 UTC SummaryThis feature simplifies how administrators keep Business Central and Dataverse aligned as Dataverse schemas evolve. Previously, exposing new or existing custom Dataverse fields required creating or updating a table extension (PTE) in the integration layer. Based on partner and customer feedback, this update removes that dependency. When a new field is added in Dataverse—such as a custom field in Dynamics 365 Sales—you can now map the field directly from the Integration Table Mappings page. You can refresh the Dataverse field list, add the field to an existing mapping, select the corresponding Business Central field, define the synchronization direction, and enable it for data synchronization. Once enabled, the field participates in sync without modifying extensions or recreating mappings. This enhancement reduces configuration overhead and supports faster adoption of custom Dataverse fields, especially for organizations that frequently customize their Dataverse environments. Business Value: As an administrator, you can map newly added Dataverse fields without recreating table extensions or writing code, reducing configuration effort and supporting faster adoption of custom fields… → This feature simplifies how administrators keep Business Central and Dataverse aligned as Dataverse schemas evolve. Previously, exposing new or existing custom Dataverse fields required creating or updating a table extension (PTE) in the integration layer. Based on partner and customer feedback, this update removes that dependency.
  23. 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  24. 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  25. 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  26. 28 Oct 2026 · 08:37:56 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/microsoft-365/roadmap?id=573365 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=573365
  27. 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  28. 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  29. 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM573365
  30. 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  31. 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  32. 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  33. 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  34. 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  35. 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  36. 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  37. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  38. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  39. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  40. 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  41. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  42. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  43. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  44. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  45. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  46. 14 Oct 2026 · 11:22:42 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 08:58 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current