Flow to send email to different individuals based off SharePoint List

%3CLINGO-SUB%20id%3D%22lingo-sub-2114611%22%20slang%3D%22en-US%22%3EFlow%20to%20send%20email%20to%20different%20individuals%20based%20off%20SharePoint%20List%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2114611%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All!%20I%20will%20attempt%20to%20state%20the%20following%20as%20clearly%20as%20possible%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20flow%20set%20up%20to%20send%20me%20a%20notification.%20It's%20triggered%20when%20the%20SharePoint%20List%20column%20'Development%20Date'%20(date%20format)%20hits%2090%20days%20past%20the%20specified%20date.%20At%20times%20this%20can%20be%20multiple%20line%20items%20that%20have%20the%20same%20Development%20Date.%20This%20works%20well%20with%20no%20problems.%20My%20next%20goal%20I%20am%20hoping%20can%20be%20accomplished%20is%20to%20have%20the%20flow%20send%20an%20email%20to%20the%20individual%20who%20is%20tied%20to%20that%20respective%20line%20item%2Frow.%20It%20is%20a%20column%20in%20the%20List%2C%20'Point%20of%20Contact'.%20I%20don't%20see%20an%20issue%20with%20this%20if%20there%20was%20ONLY%20one%20line%20item%20that%20hits%20the%20%2B90%20day%20'Development%20Date'%2C%20but%20this%20sounds%20tricky%20when%20there%20are%20multiple%20line%20items.%20My%20hope%20is%20to%20have%20the%20automation%20look%20at%20the%20first%20column%2C%20'Opportunity'%2C%20and%20send%20an%20email%20to%20the%20Point%20of%20Contact%20that%20is%20tied%20to%20that%20Opportunity%20without%20including%20the%20other%20line%20items%20that%20DO%20NOT%20pertain%20to%20that%20specific%20individual.%20The%20email%20context%20will%20be%20the%20same%20other%20than%20those%20dynamic%20field.%20I%20was%20thinking%20that%20I%20couldn't%20leverage%20the%20Switch%20Control%20condition%20because%20the%20'Opportunity'%20does%20not%20equal%20the%20same%20every%20time.%20Opportunity%20names%20change%20and%20Point%20of%20Contacts%20change%20per%20opportunity.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20let%20me%20know%20if%20I%20can%20further%20clarify%20any%20of%20the%20above!%20Thanks%20in%20advance%20and%20much%20appreciated!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2114611%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20List%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2119978%22%20slang%3D%22en-US%22%3ERe%3A%20Flow%20to%20send%20email%20to%20different%20individuals%20based%20off%20SharePoint%20List%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2119978%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F955698%22%20target%3D%22_blank%22%3E%40MatanG6%3C%2FA%3E%26nbsp%3Buse%20the%20SharePoint%20%3CSTRONG%3EGet%20items%3C%2FSTRONG%3E%20action%20with%20a%20filter%20query%20for%20the%20development%20date%20%2B90%20days%26nbsp%3B%3CEM%3E(and%20if%20there%20are%20likely%20to%20be%20more%20than%20100%20returned%20from%20your%20list%20go%20to%20settings%20for%20this%20action%2C%20turn%20on%20the%20pagination%20toggle%20and%20increase%20the%20threshold).%20%3C%2FEM%3EThen%20add%20an%20%3CSTRONG%3EApply%20to%20each%3C%2FSTRONG%3E%20control%20and%20select%20%3CSTRONG%3Evalue%3C%2FSTRONG%3E%20from%20the%20dynamic%20content%20box.%20Next%2C%20inside%20the%20apply%20to%20each%20you%20can%20add%20the%20Send%20an%20email%20(v2)%20action%20and%20select%20the%20Point%20of%20Contact%20column%20from%20the%20SharePoint%20list%20in%20the%20To%20field.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERob%3CBR%20%2F%3ELos%20Gallardos%3CBR%20%2F%3E%3CFONT%20size%3D%222%22%20color%3D%22%23006400%22%3EMicrosoft%20Power%20Automate%20Community%20Super%20User%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2119682%22%20slang%3D%22en-US%22%3ERe%3A%20Flow%20to%20send%20email%20to%20different%20individuals%20based%20off%20SharePoint%20List%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2119682%22%20slang%3D%22en-US%22%3EThe%20first%20filter%20is%20based%20on%20the%2090%2B%20days.%20I%20am%20not%20clear%20on%20what%20you%20are%20trying%20to%20achieve%20with%20'Opportunity'%20field.%20Once%20the%20items%20are%20filtered%20you%20can%20loop%20in%20the%20items%20and%20send%20an%20email%20based%20on%20one%20of%20the%20fields%20to%20the%20respective%20users.%20The%20complication%20is%20when%20you%20try%20to%20collate%20all%20the%20items%20for%20a%20person%20to%20send%20all%20the%20relevant%20items%20in%20one%20email.%20If%20you%20are%20sending%20multiple%20emails%20then%20I%20don't%20think%20there%20is%20a%20problem.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20it%20helps%2C%20please%20like%20it%20or%20mark%20it%20as%20a%20solution%20if%20it%20resolves%20your%20clarification%20or%20issue%3CBR%20%2F%3E-Sudharsan%20K...%3C%2FLINGO-BODY%3E
Occasional Visitor

Hi All! I will attempt to state the following as clearly as possible :) 

 

I have a flow set up to send me a notification. It's triggered when the SharePoint List column 'Development Date' (date format) hits 90 days past the specified date. At times this can be multiple line items that have the same Development Date. This works well with no problems. My next goal I am hoping can be accomplished is to have the flow send an email to the individual who is tied to that respective line item/row. It is a column in the List, 'Point of Contact'. I don't see an issue with this if there was ONLY one line item that hits the +90 day 'Development Date', but this sounds tricky when there are multiple line items. My hope is to have the automation look at the first column, 'Opportunity', and send an email to the Point of Contact that is tied to that Opportunity without including the other line items that DO NOT pertain to that specific individual. The email context will be the same other than those dynamic field. I was thinking that I couldn't leverage the Switch Control condition because the 'Opportunity' does not equal the same every time. Opportunity names change and Point of Contacts change per opportunity.

 

Please let me know if I can further clarify any of the above! Thanks in advance and much appreciated!

2 Replies
The first filter is based on the 90+ days. I am not clear on what you are trying to achieve with 'Opportunity' field. Once the items are filtered you can loop in the items and send an email based on one of the fields to the respective users. The complication is when you try to collate all the items for a person to send all the relevant items in one email. If you are sending multiple emails then I don't think there is a problem.

Hope it helps, please like it or mark it as a solution if it resolves your clarification or issue
-Sudharsan K...

@MatanG6 use the SharePoint Get items action with a filter query for the development date +90 days (and if there are likely to be more than 100 returned from your list go to settings for this action, turn on the pagination toggle and increase the threshold). Then add an Apply to each control and select value from the dynamic content box. Next, inside the apply to each you can add the Send an email (v2) action and select the Point of Contact column from the SharePoint list in the To field.

 

Rob
Los Gallardos
Microsoft Power Automate Community Super User