cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Need help with setting a list value based on another value in same list

I have a list where the user selects a Discipline from a dropdown. I want the AssignedTo field to populate with a person based on the selected Discipline. There are 6 disciplines and 3 people that would be assigned:

 

Disc1=Person1

Disc2 or Disc3=Person2

Disc 4,5 or 6=Person 3

 

After I update the list with the correct AssignedTo value, I want to then reference that AssignedTo value in an email. However, using Dynamic Content I am given several options for AssignedTo Display name: from when the item was first created, from Update Item, Update Item 2, Update Item 3, etc (I've tried both Condition and Switch to determine the value of AssignedTo, both of which gave me numerous Update Item steps). In testing my email, the AssignedTo value comes back blank (unless it happened to be the same one used when I selected the Dynamic Content). Isn't there a way to grab the value of AssignedTo without having to choose which Update Item path was the one the flow used to set the value? Am I approching this in the wrong way? This seems like a basic thing for Flow, but I'm new to it and am stuck.

 

Thanks,

 

1 ACCEPTED SOLUTION

Accepted Solutions
MarkStokes
Skilled Sharer
Skilled Sharer

Hi Rick,

I feel your pain.

You have gotten yourself into a situation that is very easy to get into. But hard to get out of.

When bulmdjng Flows I try to reduce as much complexity as possible. Keep it simple.

What’s the most simple answer to your issue? Well, to just use one Update Action. But, how can you do this when you have multiple possible branches that might be followed?

What I recommend is to perform all your branch logic as you currently do, but rather than duplicating your Update actions, store some variable values. Then, when you drop out of your conditional branches, perform the Update action.

That way, when you get further down in the Flow you only need to check the one Update action, or even just your variables.

Regards,

- Mark

View solution in original post

2 REPLIES 2
MarkStokes
Skilled Sharer
Skilled Sharer

Hi Rick,

I feel your pain.

You have gotten yourself into a situation that is very easy to get into. But hard to get out of.

When bulmdjng Flows I try to reduce as much complexity as possible. Keep it simple.

What’s the most simple answer to your issue? Well, to just use one Update Action. But, how can you do this when you have multiple possible branches that might be followed?

What I recommend is to perform all your branch logic as you currently do, but rather than duplicating your Update actions, store some variable values. Then, when you drop out of your conditional branches, perform the Update action.

That way, when you get further down in the Flow you only need to check the one Update action, or even just your variables.

Regards,

- Mark
Anonymous
Not applicable

That's exactly what I needed, not sure why I didn't even think about variables. Works as intended, thank you for your help.

Helpful resources

Announcements
Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

New Ideas Forum MPA.jpg

A new place to submit your Ideas for Power Automate

Announcing a new way to share your feedback with the Power Automate Team.

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

MPA Licensing.jpg

Ask your licensing questions at the Power Automate AMA!

Join Priya Kodukula and the licensing team, super users and MVPs to find answers to your questions on Power Automate licensing.

Users online (2,192)