Update planner-overview.md to include reference to change notifications #9475
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added a section to let customers know they can use change notifications for sync scenarios.
|
Learn Build status updates of commit 7154c82: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 13d69c1: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
JarbasHorst
reviewed
Dec 1, 2024
| @@ -76,6 +76,10 @@ 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 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. | |||
There was a problem hiding this comment.
The https://learn.microsoft.com/en-us/graph/change-notifications-overview topic doesn't mention support for change notifications for Planner resources. How can an app subscribe to change notifications for a Planner resource?
JarbasHorst
added
the
needs author feedback
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a section to let customers know they can use change notifications for sync scenarios.
Important
Required for API changes:
Add other supporting information, such as a description of the PR changes:
ADD INFORMATION HERE
Important
The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.
After you've created your PR, expand this section for tips and additional instructions.
#feedback-addressedto the pull request.For more information, see the Content review process summary.