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 16 Nov 2026 at 01:34 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 15 Nov 2026 at 22:07 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 (63)

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

  1. 16 Nov 2026 · 01:34:04 UTC General availability targetOctober CY2026 → Not stated
  2. 16 Nov 2026 · 01:34:04 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  3. 16 Nov 2026 · 01:34:04 UTC Source coverage: merill-message-center-archiveCurrent
  4. 16 Nov 2026 · 01:34:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  5. 16 Nov 2026 · 01:34:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573365 → No longer listed in this observation
  6. 16 Nov 2026 · 01:34:04 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items
  7. 16 Nov 2026 · 01:34: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. 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. 16 Nov 2026 · 01:23:36 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  9. 5 Nov 2026 · 18:04:05 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  10. 5 Nov 2026 · 17:01:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  11. 4 Nov 2026 · 15:02:25 UTC General availability targetNot stated → October CY2026
  12. 4 Nov 2026 · 15:02:25 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  13. 4 Nov 2026 · 15:02:25 UTC Source coverage: microsoft-365-roadmapCurrent
  14. 4 Nov 2026 · 15:02:25 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items → No longer listed in this observation
  15. 4 Nov 2026 · 15:02:25 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  16. 4 Nov 2026 · 15:02:25 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573365
  17. 4 Nov 2026 · 15:02:25 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…
  18. 4 Nov 2026 · 13:26:53 UTC General availability targetOctober CY2026 → Not stated
  19. 4 Nov 2026 · 13:26:53 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  20. 4 Nov 2026 · 13:26:53 UTC Source coverage: merill-message-center-archiveCurrent
  21. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  22. 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
  23. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items
  24. 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.
  25. 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  26. 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → October CY2026
  27. 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  28. 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
  29. 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
  30. 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  31. 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573365
  32. 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…
  33. 4 Nov 2026 · 10:01:18 UTC General availability targetOctober CY2026 → Not stated
  34. 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  35. 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
  36. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  37. 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
  38. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items
  39. 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.
  40. 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  41. 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  42. 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  43. 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
  44. 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  45. 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  46. 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM573365
  47. 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  48. 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  49. 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  50. 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  51. 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  52. 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  53. 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  54. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  55. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  56. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  57. 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  58. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  59. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  60. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  61. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  62. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  63. 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