Expense report action "Condition" failed.

[MsBooi]

Hi All, I'm trying the Expense Report sample power app. I've followed all the steps, and everything seems to work fine until I approve or reject a request flows sends back an error that reads  "An action failed. No dependent action succeed" this error rises from the "condition " action on my flows.

Then from the body it sends an error message that states " the phased-in field \"Cost_x0020_center\" could not be found\r\nclientRequestId... tried changing cost center from just "cost center" to "Cost center value" but still...ease kindly help.

[Expiscornovus]

Hi @MsBooi,

Can you share a couple of screenshots of the setup of your actions within your flow? 

[MsBooi]

Hi @Expiscornovus  and thank you for affording me your time, now what is happening is I deleted and entered a new "Get item" action, there is no more errors but flows is running without finishing also it is not changing the status to "approved or rejected" in SharePoint list.

The flow's snipshot is as follows:

[Expiscornovus]

Hi @MsBooi,

What I can see from the first screenshot is that the new Get Items 2 action is retrieving 4 list items. Those 4 items are retrieved from the expenses list?

So, I guess you have 4 items for which you are starting an approval process, correct? And for all 4 items you have either approved/rejected the requests in the Approval Center. And that bit worked?

[MsBooi]

@Expiscornovus yes that's sounds right.

[Expiscornovus]

Hi @MsBooi,

How have you configured your condition action, can you share a screenshot of that? 

And I would also be interested in the 4 items itself. It could be that there are some null values in one of the items. Maybe you can share the output of the Get Items 2 action?

And final question. Is this test data or already production? If it is still test, I would just cancel the current running flow instance and resubmit it from the history, if possible.

[MsBooi]

the condition action is as the following:

So its the same as on "if no" difference is just the status update.

With regards to the SharePoint items here is the snipshot of the list, problem is with status not changing and comments is indeed null

Yes it is still testing data, i tried cancelling and resubmitting and the data i tried that on is still running even now.

[Expiscornovus]

Hi @MsBooi,

In your screenshots I see two cost center fields. Maybe that is the reason why it is failing. One looks like an older field which only allows the selection of a single value.

And out of interest, why are you updating the Cost Center value? I would assume the Cost Center needs to be same as right before approval.

I think in the update item action you can just leave those cost center fields blank (those are not mandatory). Can you test that for me?

[MsBooi]

Thank you for your response please bear with me im a beginner, so i used  Expense Report sample and from the instructions they did not mention removing them.

Yes it is.

So i tried as your request like you can see:

i don't know why but now i am having this new error(see below), also i have noticed my flow always starts from the very first request to run every time i sent a request how do i fix that part?

[Expiscornovus]

Hi @MsBooi,

When I look at your last screenshot I see that the condition expression result is false, this means it won't execute the update item action.

I didn't notice before but I now see that you are using the Response field in the condition action. Can you try and use the outcome field instead?

Btw, can you also share the link to Expense Report sample instructions. This way I can also validate those.

[MsBooi]

@Expiscornovus  i cant seem to find the outcome field, what other field can i use?

Here is the link i used: https://github.com/MicrosoftDocs/powerapps-docs/commit/494e886298e35f2770ef2207b644a30efb4e89e4

[Expiscornovus]

Hi @MsBooi,

Thanks for sharing the link. That is actually a code commit (a change to the existing documentation) in GitHub. But I think I did find the original instructions:

https://github.com/MicrosoftDocs/powerapps-docs/blob/494e886298e35f2770ef2207b644a30efb4e89e4/powera...

I will take a bit of time to work through the setup that same example and see if I can reproduce the issue.

[MsBooi]

@Expiscornovus great then! you the right person😀 I will wait for you then but please assist here if i cant find the "outcome" field what do i use?

[Expiscornovus]

Hi @MsBooi,

I think I figured it out. I also found the related YouTube video from Todd Baginski, https://youtu.be/kJXZPILfbwU?t=782

This is a demo from 2018 which is using the start an approval action which is a deprecated action:

https://docs.microsoft.com/en-us/connectors/approvals/#start-and-wait-for-an-approval-[deprecated]

Did you import that flow or did you create it from scratch? When importing an old flow I guess technically you could still import old deprecated actions.

When you use the Start and wait for an approval action instead you should be able to use the outcome field as well: https://docs.microsoft.com/en-us/connectors/approvals/#start-and-wait-for-an-approval

[MsBooi]

Hi @Expiscornovus 

Apologies on going awol, i actually went through the shared vid it helped a lot.

It makes total sense when you say importing could result in importing old deprecated actions because of that I decided to start the flow from complete scratch works well running it from flows problem is I'm now experiencing issues connecting the new flow to that existing app resulting in the app itself to give me an error.