MS Power Automate Flow - Connecting Planner and ValueStreamer - Backup

1-7

8-15

15-15.1.1.4 / 15.1.2.3

15-15.2.1.6.1.1 / 15.2.1.6.2.3

15-15.2.2.6

Flow is triggered.

Trigger:

No Connector,

Manually Trigger a flow

-

Request data from Valuestreamer containing the tasks from a certain team.

HTTP:

HTTP,

HTTP reqeust to GET all tasks from VS Team

Parse the response of step 2 in a JSON-Object.

Parse JSON:

Data Operations,

Parse JSON for tasks

Create new variable called userID with datatype String and no value.

Initialize Variable:

Variables,

Initialize Variable userID

Create new variable called userEmail with datatype String and no value.

Initialize Variable:

Variables,

Initialize Variable userEmail

Create new variable called HelpGetPlannerUserId with datatype String and no value.

Initialize Variable:

Variables,

HelpGetPlannerUserID

For-each-Loop: Iterate over all returned tasks from VS, using the JSON-Object from step 3.

For each:

Control,

For each

Set variable UserID to Assignee from current task.

Set variable:

Variables,

Set variable userId to JSON response

Set variable HelpGetPlannerUserId to null (to delete values from previous iterations)

Set variable:

Variables,

Set helperVariable to null

Set variable userEmail to null (to delete values from previous iterations)

Set variable:

Variables,

Set userEmail to null

List rows from User-Table that belong to the current UserID (the variable was set in step 8)

List rows
Microsoft Dataverse,

List rows of user table

For-each-Loop: Iterate over all returned rows from step 11.

In step 11 only one row should be returned, because each user exists only once in the table. However PowerAutomate does not know this and therefore the For-Each-Loop is needed.

For each:

Control

Iterate over returned rows of user table

Compare current UserID from step 8 to userId from the returned rows in step 11. If equal, then task from Valuestreamer has an assignee and that assignee exists in user table (true).

If true: Go to step 13.1.1

If false: Go to step 13.2.1

Condition:

Control

Condition userId is equal to userId of user table

13.1.1

For-each-Loop: Iterate over all returned rows from step 11.

For each:

Control

Iterate over returned rows of user table (2)

13.1.2

Set variable userEmail to email of current iteration of step 13.1.1

Set variable:

Variables,

Set varaible userEmail

13.2.1

Set variable userEmail to null.

Set variable:

Variables,

Set variable userEmail to null

14.

List rows from Task-Table that belong to the current UserID (the variable UserID was set in step 8)

List rows
Microsoft Dataverse,

List rows of task table

15.

Compare the amount of rows returned in step 14 to 0.

If the amount is 0, then the task does not exist in the task table (true).

If the amount is 1 or higher, then the task does exist in the task table (false).

If true: Go to step 15.1.1

If false: Go to step 15.2.1

For each:

Control,

Condition Task does not exist in table yet

15.1.1

Compare the value of userID (set in step 8) to 0.

If the value is not 0, then it is not empty and the task does have an assignee (true).

If the value is 0, then it is empty and the task does not have an assignee (false).

If true: Go to step 15.1.1.1

If false: Go to step 15.1.1.2

For each:

Control,

Condition UserId is not empty

15.1.1.1

Current situation: Case 1:
Task only exists in Valuestreamer
Task in Valuestreamer is assigend

Task has to be created in task table. Therefore a new row is added, with the values of the current task of the iteration of step 7

Add a new row:

Microsoft Dataverse,

Add new row with user

15.1.1.2

Task has to be created in Planner.

Create a task:

Planner,

Create a task

15.1.1.3

ID from newly created Planner task (step 15.1.1.2) has to be written into task table.

Update a row:

Microsoft Dataverse,

Update a row

15.1.1.4

Inform user via teams that a new task has been created in planner and assigned to him.

End of iteration - jump back to step 7

Post message in a chat or channel:

Microsoft Teams,

Post message in a chat or channel

15.1.2.1

Current Situation: Case 2:
Task only exists in Valuestreamer
Task in Valuestreamer is NOT assigend

Task has to be created in task table. Therefore a new row is added, with the values of the current task of the iteration of step 7. The task has no assignee, therefore the user remains empty.

Add a new row:

Microsoft Dataverse,

Add new row with assignee = null

15.1.2.2

Task has to be created in Planner.

Create a task:

Planner,

Create a task with assignee = null

15.1.2.3

ID from newly created Planner task (step 15.1.2.2) has to be written into task table.

End of iteration - jump back to step 7.

Update a row:

Microsoft Dataverse,

Update a row 2

15.2.1

Compare the value of userID (set in step 8) to 0.

If the value is not 0, then it is not empty and the task does have an assignee (true).

If the value is 0, then it is empty and the task does not have an assignee (false).

If true: Go to step 15.2.1.1

If false: Go to step 15.2.2.1

Condition:

Control,

Condition UserId is not empty

15.2.1.1

Situation: Case 3:
Task exists in Valuestreamer and Planner.
Task is assigned in Valuestreamer

For-each-Loop: Iterate over returned rows in task-table from step 14.

For each:

Control,

Iterate over returned rows of task table

15.2.1.2

Task has to be updated in task table.

Update a row:

Microsoft Dataverse,

Updating an existing row

15.2.1.3

Task table has to be synchronized with tasks in Planner.

Get a task:

Microsoft Planner,

Get a task

15.2.1.4

Set variable HelpGetPlannerUserId to userId of task in Planner

(Loop will be created automatically, when value is set to userID)

Set Variable:

Variables,

Set variable HelpGetPlannerUserId

15.2.1.5

Compare the value of HelpGetPlannerUserId with 0.

If greater than 0, HelpGetPlannerUserId is not empty (true).

If not greater, HelpGetPlannerUserId is empty (false).

If true: Go to step 15.2.1.5.1.1

If false: Go to step 15.2.1.5.2.1

Condition:

Control,

Planner task has assignee

15.2.1.5.1.1

Get User profile from Office365-App

Get user profile (V2):
Office 365 Users,

Get user profile (V2)

15.2.1.5.1.2

Set variable HelpGetPlannerUserId to mail from returned value of step 15.2.1.5.1.1

Set variable:
Variables,

Set variable HelpGetPlannerUserId (2)

15.2.1.5.2.1

Set variable HelpGetPlannerUserId to null.

Set variable:
Variables,

Set variable HelpGetPlannerUserId (3)

15.2.1.6

Compare the value of userEmail to HelpGetPlannerUserId.

If equal, then both tasks have the same assignee (true).

If not equal, then assignees are different and the assignee in planner has to be changed (false).

If true: Go to step 15.2.1.6.1.1

If false: Go to step 15.2.1.6.2.1

Condition:

Control,

Planner assignee is same as valuestreamer task assignee

15.2.1.6.1.1

Update task in planner with values from valuestreamer.

End of iteration - jump back to step 7.

Update a task:
Microsoft Planner,

Update a task

15.2.1.6.2.1

Update task in planner to add a new assignee.

Update a task:
Microsoft Planner,

Update a task and adding a new assignee

15.2.1.6.2.2

Remove old assignees from task.

This has to be done by an extra action. The action “Update task in planner” also has the option to remove an assignee -however this did not work while programming this flow (Jan2024)

Remove old assignee from a task:
Microsoft Planner,

Remove assingees from a task

15.2.1.6.2.3

Inform user via teams that a task has been assigned to him.

End of iteration - jump back to step 7

Post message in a chat or channel:

Microsoft Teams,

Post message in a chat or channel

15.2.2.1

Situation: Case 4:
Task exists in Valuestreamer and Planner.
Task is NOT assigned in Valuestreamer

For-Each-Loop: Iterate over all returned tasks from step 14.

For each:

Control,

Iterate over all rows from task table

15.2.2.2

Update a row in task table.

Update a row:
Microsoft Dataverse

Update a row in task-table

15.2.2.3

Get task from Planner.

Get a task:
Microsoft Planner,

Get a task (2)

15.2.2.4

Set variable HelpGetPlannerUserId to userID from task in planner (step 15.2.2.3). (Creates automatically a loop).

Set Variable:
Variables,

Set variable HelpGetPlannerUserId to userID from task in planner

15.2.2.5

Update task in planner.

Update a task:
Microsoft Dataverse,

Update a task (2)

15.2.2.6

Remove assignee from task in planner.

End of iteration - jump back to step 7

Remove assignee from a task:
Microsoft Planner,

Remove assignees from a task (2)

3.

7.

8.

11.

13.