From 7154c823975f00835680a5916d5a6a7ce120ef63 Mon Sep 17 00:00:00 2001 From: Jennifer Showe Date: Tue, 26 Nov 2024 10:40:52 -0800 Subject: [PATCH 1/2] Update planner-overview.md Added a section to let customers know they can use change notifications for sync scenarios. --- api-reference/v1.0/resources/planner-overview.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/api-reference/v1.0/resources/planner-overview.md b/api-reference/v1.0/resources/planner-overview.md index 66be7ef564d..10ff40855b4 100644 --- a/api-reference/v1.0/resources/planner-overview.md +++ b/api-reference/v1.0/resources/planner-overview.md @@ -76,6 +76,9 @@ Planner allows changes to older versions of resources, if the intended change do Each resource has a unique etag. Etag values for different resources, including those with containment relationships, cannot be compared. The client apps are expected to handle versioning related [error codes](/graph/errors) `409` and `412` by reading the latest version of the item and resolving the conflicting changes. +## Planner change notifications +An app may subscribe to [change notifications](/graph/change-notifications-overview) for all Planner resources. When a resource has changed, the app will receive a notification which includes the id of the resource which has changed and can use this to pull down the most recent version of the resource. For app developers needing to synchronize a copy of a tenant's Planner data to local storage this is the most efficient and recommended approach to avoid running into throttling limits. + ## Common Planner error conditions In addition to [general errors](/graph/errors) that apply to Microsoft Graph, some error conditions are specific to the Planner API. From 13d69c1c732149a5df15997688f50697ba6fa53c Mon Sep 17 00:00:00 2001 From: Jarbas Horst Date: Sun, 1 Dec 2024 23:53:45 +0100 Subject: [PATCH 2/2] Update planner-overview.md --- api-reference/v1.0/resources/planner-overview.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/api-reference/v1.0/resources/planner-overview.md b/api-reference/v1.0/resources/planner-overview.md index 10ff40855b4..8d5b6290e0a 100644 --- a/api-reference/v1.0/resources/planner-overview.md +++ b/api-reference/v1.0/resources/planner-overview.md @@ -77,7 +77,8 @@ Each resource has a unique etag. Etag values for different resources, including The client apps are expected to handle versioning related [error codes](/graph/errors) `409` and `412` by reading the latest version of the item and resolving the conflicting changes. ## Planner change notifications -An app may subscribe to [change notifications](/graph/change-notifications-overview) for all Planner resources. When a resource has changed, the app will receive a notification which includes the id of the resource which has changed and can use this to pull down the most recent version of the resource. For app developers needing to synchronize a copy of a tenant's Planner data to local storage this is the most efficient and recommended approach to avoid running into throttling limits. + +An app may subscribe to [change notifications](/graph/change-notifications-overview) for all Planner resources. When a resource changes, the app receives a notification that includes the ID of the changed resource, which you can use to get the most recent version of the resource. For app developers who need to synchronize a copy of Planner data from a tenant to local storage, this is the most efficient and recommended approach to avoid running into throttling limits. ## Common Planner error conditions