Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Create an example on how a user could change the organizer of a recurring meeting to a new organizer #56

Open
lordneeko opened this issue Aug 22, 2023 · 0 comments

Comments

@lordneeko
Copy link

Premise: We are constantly fighting the battles of having to cancel recurring meetings so that a new organizer can take it over. This causes all sorts of headaches, but it just plain a pain to do.

The Need: A PowerApp and sets of PowerAutomate flows which the "old organizer" initiates. The old organizer selects the meeting they want to re-assign and then enters the new organizer's information. The App/Flow then creates a "Draft" meeting invite with all the exact same information as the previous invite (including To, CC, subject, body, and Teams invite links/phone number) and sends the draft to the new organizer (somehow) who then just has to "send" it out (suspect a manual interactio of some sort here). Except, the "Send it out" action also cancels the old invite, so it all seems to happen simultaneously.

Ideally, the "Cancel" action and the "New" action would not send an email to everyone. Their calendars would just update with the new item.

Also Ideally, the user would not need to install their own flows or anything, the whole solution would be created as an exported PowerApp that would just "Work" for the entire enterprise once imported into the environment.

Side note: This should be an out of the box feature, quite honestly, in a business/enterprise environment. This capability should be build into Outlook/Exchange, rather than creating a workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant