Skip to content

Conversation

jennifershowe
Copy link

Added a section to let customers know they can use change notifications for sync scenarios.

Important

Required for API changes:

  • Link to API.md file: ADD LINK HERE
  • Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): ADD LINK HERE

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.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

Added a section to let customers know they can use change notifications for sync scenarios.
Copy link

Learn Build status updates of commit 7154c82:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/resources/planner-overview.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit 13d69c1:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/resources/planner-overview.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:


## 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 JarbasHorst added the needs author feedback Waiting for author (creator) of issue to provide more info label Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs author feedback Waiting for author (creator) of issue to provide more info

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants