If/Else Flow Possible?

[mstump]

Full disclosure, I'm not a programmer but am vaguely familiar with some of the concepts. I'm attempting to create a calendar item based on when a certain condition is met. I've tried going wide by creating conditions that say:

Condition: UserProfile.City = 'Jacksonville'

If Yes > Create calendar event in the Jacksonville Group

If No > Condition: UserProfile.City = 'Lantana'

If Yes > Create calendar event in the Lantana Group

If No > Condition: UserProfile.City = 'Tallahassee'

If Yes > Create calendar event in the Tallahassee Group

If No > Condition: UserProfile.City = 'Bismarck'

If Yes > ... y'all get the point.

Notes:

• UserProfile.City = Current user's listed City in their profile
• The value listed in the condition is just text.
• The UserProfile.City, Group and the text in the condition are three separate fields.
• You can assume each employees UserProfile.City value correlates to a matching group.

Now it gets so wide that Power Automate (PA) won't let me add any more actions ~after the 5th city (I need 7 iterations of this). I've been poking around for the past few days and have yet to find someone else who was looking for something similar. A programmer friend suggested this:

You’ll want something like For each profile

{ Switch profile.city

{

Case jax: Add to jax

Case lan: Add to lan

}}

Any direction or help would be greatly appreciated. Thank you!

[edgonzales · Accepted solution]

@mstump 

Hi there.  Check out the "Switch" action.  It lets you set a condition with a non-binary (true/false, yes/no) response.  Here's a quick article from @priyeshwagh777  I found:

Switch-Case in a Flow | Power Automate

Keep us posted.

-Ed

If you liked this reply, please give it a thumbs up! If this reply has answered your question or resolved your challenge, please consider marking it as a Solution. This helps other users find it more easily via search.

[Amanthaper]

Hi,

For someone who's non-technical, great attempt using conditional actions.

Can I suggest the following.

Since you will always create a cal event for the group which is the User's Profile City why not capture the city first thing in the flow and assign it to a string variable so you can use it anywhere later on in the flow, or directly reference the User profile's city in any other action downstream.

Not sure if this helps.

In this example, for simplicity's sake I've used the city in the cal event subject but it can be used anywhere else in the calendar action.

Unless there's something I'm missing, with this approach you would not need to use any conditions.

Cheers,

Aman T------------------------------------------------------------------------------------------------------
If my post helps you with your problem or answers your question, please mark it Solved or Answered. This helps anyone with similar challenges. If you like my response, please give it a Thumbs Up.
------------------------------------------------------------------------------------------------------

[mstump]

Ah that's great. I didn't know that function existed. I'm pretty sure this is exactly what I was looking for, but now having trouble with the actual dates that get added to the group. Having a hard time understanding why, but it has something to do with time zones. Not looking forward to troubleshooting that one. Anyways, it's outside the scope of this post, so I'll do some research and/or create another post.

Thanks for the suggestion!

[mstump]

I could be missing something, but I'm not sure your example helps what I'm trying to do. From your screenshot, it just looks as if you're pulling the city name of the user's profile, and inserting it into the Subject field of the group event (that you've already assigned).

The group the event gets added to will change based on the value of the users' City.

EDIT: My fault, I missed the part where I can add dynamic fields in the Calendar id by choosing "Custom ID". I'll try this and let you know how it goes.

--Okay I think this could work too, but not at this moment because I grouped too many things together into one step (it wants the variable at the top). I'm planning on creating the production flow later. Will keep this in mind. FYI - I got an error when trying to use the users' city as the custom group ID.