Hi Everyone,
I have an issue while trying to add attendees to a planner task using a flow with calendar.
The flow is activated when a meeting is created on calendar of office 365, the action is create a planner task (in a previous bucket already created), then after all attendees accept the meeting, I receive this message on flow notifications: "Schema validation has failed. Validation for field 'Assignments', on entity 'Task' has failed: The assignee id is invalid.". I think that the issue is because of the way Flow try to add the attendees to Planner, by adding them as a normal "email string" (user1@domain.com;user2@domain.com; ), and Planner doesn’t recognize this format, ¿I am wrong?, or ¿I'm missing something?
The output of the failure message show this:
Status code: 400
Body:
{
"error": {
"code": "",
"message": "Schema validation has failed. Validation for field 'Assignments', on entity 'Task' has failed: The assignee id is invalid.",
"innerError": {
"request-id": "f3c53084-3262-4e8a-9c19-2a7bf6e0a3a0",
"date": "2018-03-12T09:52:45"
}
}
}
Thanks in advance,
Hi @Mario27
I just stumbled on your request. You've been waiting a while for a reply.
Were you able to solve it? Can you post the solution so that we can all learn from it?
If you still need help, please let me know what changed.
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Cheers
Manuel
Hey @manuelstgomes,
I am having the issue as well, my flow is pretty simple. It is basically when a new file is created in our documents, a new task is added to the planner.
{
"error": {
"code": "",
"message": "Schema validation has failed. Validation for field 'Assignments', on entity 'Task' has failed: The assignee id is invalid.",
"innerError": {
"request-id": "b237eaa5-94de-449c-83ea-39b330efe60a",
"date": "2020-01-28T13:56:06"
}
}
}
It would not let me add the picture of the flow to my reply so here it is
Hi @Anonymous and @Mario27
Instead of the "Display Name" use the "Email" field. That's the user's ID and that's why it's complaining that the "Assignee id" is not valid.
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Cheers
Manuel
Hey @manuelstgomes ,
That worked, Thanks a lot!!
I was wondering if there is a way to trigger this flow only when a document set is created
Thanks, Jay
Hi @Anonymous and @Mario27
Glad it works. 🙂
Regarding @Anonymous the Document Set isn't part of the metadata, sorry :(.
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Cheers
Manuel
Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!
Power Platform release plan for the 2021 release wave 1 describes all new features releasing from April through September 2021.
User | Count |
---|---|
13 | |
7 | |
4 | |
4 | |
4 |
User | Count |
---|---|
11 | |
8 | |
6 | |
5 | |
4 |