Unanswered

Update Dataverse table if status is X

(0) Share

Report

Posted on by Community Power Pla...

Hey there,

We are using Microsoft Dynamics 365 and we are experiencing that users find it difficult to 'complete' their phonecalls.

Therefor I would like to do the following and create a scheduled flow that does the following:

- Get all the rows from table 'Phone Calls' and a filter on column 'StateCode' where the content equals status 0 ('Open').

- Update these rows to status 1 ('Completed')

For the first step I had the following in mind. I would use the function List Rows and filter with: StateCode eq '0'.

But for the second step: I'm not sure on how to reach my goal there.

What would be handy?

Thanks!

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

Hi @Robbertoo

You could use the Update record action within an Apply to Each loop, to Update each Phone Call record and set the Status and Status Reason accordingly.

However, I wouldn't build this to work on a scheduled basis with such open filters, as it could in potentially close records that should not be closed. Furthermore, the could be a delay (depending on your schedule interval) between the phone call actually being completed to when it is actually closed. I would suggest adding an additional filter when you identify the records for closure (eg. Scheduled Date is older than 1 week).

Alternatively, you could introduce additional columns on the Phone Call table and form (if users find populating columns on the form easier and/or more prominent than the Close command bar buttons (if this is in the context of a Model Driven App)). You could then trigger your Cloud Flow/Workflow of this additional column value being set, rather than relying on a scheduled process. This approach which close each Phone Call as a a dedicated process whenever the uses chooses to close it.

Was this reply helpful? Yes No
MarioRing 541 Super User 2024 Season 1 on at

Like (1)

Report

The idea behind Dynamics Activities records, like Phone Calls, is to plan something to do and then register in the system if something was done. An open Phone Call means that someone has to call somebody for some reason, this record is just a reminder to do that. Closed as completed means the call was made (and obviously an activity can be alternatively closed as canceled).

From this point of view, your flow will close all the tasks of phone calls as done, which may not be true.

Instead of creating this workflow, I suggest creating a view or dashboard, where your users can see all their open phone calls which are waiting to be made and closed. Each user should manually close their activities, fortunately, it is possible to do this using bulk editing.

Was this reply helpful? Yes No