Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.
Cite this versionField-level log (54)
Up to 100 recent field edits are shown; older edits may be outside retention.
- 5 Nov 2026 · 17:01:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 4 Nov 2026 · 15:02:25 UTC General availability targetNot stated → October CY2026
- 4 Nov 2026 · 15:02:25 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
- 4 Nov 2026 · 15:02:25 UTC Source coverage: microsoft-365-roadmapCurrent
- 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
- 4 Nov 2026 · 15:02:25 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
- 4 Nov 2026 · 15:02:25 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573345
- 4 Nov 2026 · 15:02:25 UTC SummaryBusiness Value → Business Value Subcontractors need clear instructions about the work they must perform. Reentering that information on purchase orders takes time and can introduce differences between the routing, production order, and purchasing documents. Details Subcontracting comments and attachments now follow the operation into the purchase order. The purchasing document keeps the production context needed by the vendor while allowing you to review and adjust the information before sending the order. The Subcontracting Comments action is available from standard tasks, routing lines, routing version lines, and production order routing operations. Comments follow the production flow: Add subcontracting comments to a standard task or routing operation. When you assign the standard task, its comments copy to the routing operation. When you create or refresh a production order, routing comments copy to the production order routing operation. When you create a subcontracting purchase order directly or from the Subcontracting Worksheet, the comments become descriptive purchase lines attached to the related subcontracting line. Both Description and Description 2 flow through the process. If you chan…
- 4 Nov 2026 · 13:26:53 UTC General availability targetOctober CY2026 → Not stated
- 4 Nov 2026 · 13:26:53 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
- 4 Nov 2026 · 13:26:53 UTC Source coverage: merill-message-center-archiveCurrent
- 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
- 4 Nov 2026 · 13:26:53 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573345 → No longer listed in this observation
- 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items
- 4 Nov 2026 · 13:26:53 UTC SummaryBusiness Value Subcontractors need clear instructions about the work they must perform. Reentering that information on purchase orders takes time and can introduce differences between the routing, production order, and purchasing documents. Details Subcontracting comments and attachments now follow the operation into the purchase order. The purchasing document keeps the production context needed by the vendor while allowing you to review and adjust the information before sending the order. The Subcontracting Comments action is available from standard tasks, routing lines, routing version lines, and production order routing operations. Comments follow the production flow: Add subcontracting comments to a standard task or routing operation. When you assign the standard task, its comments copy to the routing operation. When you create or refresh a production order, routing comments copy to the production order routing operation. When you create a subcontracting purchase order directly or from the Subcontracting Worksheet, the comments become descriptive purchase lines attached to the related subcontracting line. Both Description and Description 2 flow through the process. If you chan… → Business Value
- 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → October CY2026
- 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
- 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
- 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
- 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
- 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573345
- 4 Nov 2026 · 11:04:04 UTC SummaryBusiness Value → Business Value Subcontractors need clear instructions about the work they must perform. Reentering that information on purchase orders takes time and can introduce differences between the routing, production order, and purchasing documents. Details Subcontracting comments and attachments now follow the operation into the purchase order. The purchasing document keeps the production context needed by the vendor while allowing you to review and adjust the information before sending the order. The Subcontracting Comments action is available from standard tasks, routing lines, routing version lines, and production order routing operations. Comments follow the production flow: Add subcontracting comments to a standard task or routing operation. When you assign the standard task, its comments copy to the routing operation. When you create or refresh a production order, routing comments copy to the production order routing operation. When you create a subcontracting purchase order directly or from the Subcontracting Worksheet, the comments become descriptive purchase lines attached to the related subcontracting line. Both Description and Description 2 flow through the process. If you chan…
- 4 Nov 2026 · 10:01:18 UTC General availability targetOctober CY2026 → Not stated
- 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
- 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
- 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
- 4 Nov 2026 · 10:01:18 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573345 → No longer listed in this observation
- 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365 Business Central/roadmap?topic=Dynamics%20365%20Business%20Central&period=all#items
- 4 Nov 2026 · 10:01:18 UTC SummaryBusiness Value Subcontractors need clear instructions about the work they must perform. Reentering that information on purchase orders takes time and can introduce differences between the routing, production order, and purchasing documents. Details Subcontracting comments and attachments now follow the operation into the purchase order. The purchasing document keeps the production context needed by the vendor while allowing you to review and adjust the information before sending the order. The Subcontracting Comments action is available from standard tasks, routing lines, routing version lines, and production order routing operations. Comments follow the production flow: Add subcontracting comments to a standard task or routing operation. When you assign the standard task, its comments copy to the routing operation. When you create or refresh a production order, routing comments copy to the production order routing operation. When you create a subcontracting purchase order directly or from the Subcontracting Worksheet, the comments become descriptive purchase lines attached to the related subcontracting line. Both Description and Description 2 flow through the process. If you chan… → Business Value
- 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 28 Oct 2026 · 08:37:56 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/microsoft-365/roadmap?id=573345 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=573345
- 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM573345
- 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
- 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 14 Oct 2026 · 11:22:42 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete