cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Action 'Send_an_email_(V2)' failed. Parameter 'To' cannot be null or empty.

Hi Everyone,

 

I encountered a very strange problem.

 

I am building a flow from sharepoint list for users to submit request and get approval. Since the approver delegation is very complicated, which I cannot combine the request and approver delegation into the same flow because it will be more than the allowed maximum 8 nesting. Thus I firstly create a flow to complete the approver delegation then use the update item function to write back to the sharepoint list for approver of each step. The approver delegation flow works well.

 

However, the question is on the subsequent flow for sending email, it is always failed, saying "To" is null and empty. I have tried recreating, but still failed, so I don't know what to do. Appreciate if anyone can help me out.

ShineTan123_1-1647404119245.png

 

ShineTan123_0-1647404097172.png

 

1 ACCEPTED SOLUTION

Accepted Solutions
KvB1
Solution Sage
Solution Sage

After the delay, add a new action: fetch sharepoint item. Use the same site and list as in the trigger. You need to add an id, use the dynamic content id of the trigger

 

Use the dynamic content mail column of the fetch sharepoint item action to populate the 'to' field, instead of using the dynamic content mail column of the trigger

View solution in original post

20 REPLIES 20
fchopo
Super User
Super User

Hi @ShineTan123 

Can you share your workflow in the "send an email action" ? Which value are you using in the "To" parameter?

Regards,

Ferran

Did I answer your question? Please consider to mark my post as a solution to help others.
Proud to be a Flownaut!
KvB1
Solution Sage
Solution Sage

whats in the condition, and what are you using as input for who to send the mail to?

Hi @fchopo 

"To" parameter is using dynamic content. This dynamic input is actually the output from the other flow.

I built the other flow to decide which should be the approvers, then it write back to sharepoint list under the name that I am using in the "To" dynamic content.

 

ShineTan123_0-1647419643450.png

 

Hi @KvB1,

Under the condition there are a lot of steps, but basically is to send email and request for approvals. And now the error stops the flow at the very beginning of the condition.

"To" parameter is using dynamic content. This dynamic input is actually the output from the other flow.

I built the other flow to decide which should be the approvers, then it write back to sharepoint list under the name that I am using in the "To" dynamic content.

ShineTan123_1-1647419885612.png

 

KvB1
Solution Sage
Solution Sage

Can you verify that the 'to' field is populated by the correct value?

Easiest way to do this is to create a compose action and give it the same value

Hi @ShineTan123 

Which is the "Spoc" data type field in SharePoint? Is it a a people column, or is it a text one? You should check the value of that column in SharePoint, which is probably causing the error.

Regards,

Ferran

Did I answer your question? Please consider to mark my post as a solution to help others.
Proud to be a Flownaut!

Hi @fchopo,

I have thought about this part actually. In the sharepoint, the type of that field I created is Single line of text. And the output from the other flow is email address, thus I tried manually input the email address in the sharepoint list, and the flow can run successfully.

However, when I expect the writeback from the other flow, meaning leave the field blank and wait for the other flow to update, then the current flow failed with the error of null or empty. So I am thinking whether it's the constraint of Power Automate that one flow cannot use the output from the other flow, but the weird thing is it actually got successful few times, though most of the time got failure.

Hi @KvB1,

Would you mind demo on how to verify? I added the compose and input with this dynamic content, I don't know what does it mean.

ShineTan123_1-1647421228059.png

 

ShineTan123_0-1647421178296.png

 

KvB1
Solution Sage
Solution Sage

This will tell you exactly what is used in the send email action in the 'to' field

 

It's a way of troubleshooting

 

If you 'Click to download' it will show you what is being used as an address to send the mail to, and can see where you have to correct something

Hi @KvB1,

It's blank when I click download. Both input and output are blank. So meaning it's nothing in this dynamic content?

KvB1
Solution Sage
Solution Sage

Yes that is true, I guess that means its a sharepoint field thats empty?

Hi @KvB1,

In fact not empty. I also double clicked to check, the email is there.

 

ShineTan123_0-1647422056613.png

 

KvB1
Solution Sage
Solution Sage

Very strange problem. Earlier you described an interaction with another flow. The other flow populates this email field during the delay in this flow, correct?

But this causes this flow to fail.

 

If you run it solo and manually fill in the email field, it doesn't give the error, right?

The only possibility seems that the field wasn't filled by the other flow at the time the delay passed. If the other flow doesn't give any errors (by trying to fill a text field with an array or something), I guess this flow will execute the send mail action before the other flow has finished populating the necessary fields?

Hi @KvB1,

I have also tried to test whether is about the timing.

The correlated flow and this flow has the same trigger, "when item is created".  I put 5mins delay in this flow, the correlated flow is run less than 1min with no error. but when the delay passed, the error still come. I also suspect whether the sharepoint is not refreshed, so I immediately refresh after the correlated flow completes and I can see the field populated successfully. But this flow still failed, so my hands are tied.

KvB1
Solution Sage
Solution Sage

Ah okay, that explains it then

 

The dynamic content for the email field is from the trigger in the flow that fails, correct?

The delay is irrelevant, because the information that will be used for the email field was grabbed at the trigger stage, not at the send email stage.

 

The quick and dirty way that would fix it: store the ID of the trigger item in a variable, then after the delay fetch this item again, using the ID stored in the variable. Use the email field of that output of that action to populate the 'to' field in the email

Hi @KvB1,

Could you explain how I should do that? Using the term in the power automate will be much appreciated.

KvB1
Solution Sage
Solution Sage

After the delay, add a new action: fetch sharepoint item. Use the same site and list as in the trigger. You need to add an id, use the dynamic content id of the trigger

 

Use the dynamic content mail column of the fetch sharepoint item action to populate the 'to' field, instead of using the dynamic content mail column of the trigger

Hi @KvB1,

Do you mean "Get item"? If yes, where do I put id in?

 

ShineTan123_0-1647425423601.png

 

KvB1
Solution Sage
Solution Sage

This is a different action: Get itemS

 

You need: Get item (without the s)

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (2,120)