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

Value could not be input via Parse JSON Object to String

I'm developing PowerApps and PowerAutomate;

PowerApps trigger => [JSON] => Parent Flow => [Add Data] => [JSON] => Child Flow => Sending Email

At the final, "Sending Email" had error;

ks4050kt_4-1596377687622.png

It simply says "To" value (=email address) to be filled. (but not only "To" also other string not be shown in sending email action)

The value was generated by Parse JSON, but not appeared in Sending Email action...

What is incorrect to set and run Parse JSON??

Parent Flow after receive JSON from PowerApps;

 

ks4050kt_0-1596378565302.png

 

 

ks4050kt_0-1596377658089.png

Child Flow to sending email;

ks4050kt_1-1596377668478.png

Detail of Parse JSON in Child Flow;

ks4050kt_2-1596377675546.png

Result of Parse JSON in Child Flow after Test Run;

ks4050kt_3-1596377681874.png

What set in Sending Email action with Parse JSON result;

ks4050kt_5-1596377697196.png

Input Content of Parse JSON;

 

{
  "body": {
    "Email": "ks4050kt@power.com",
    "Applicant": "ks4050kt",
    "Dept": "PowerAutomate",
    "DateOfApplication": "2020-08-02 23:05:41Z",
    "Cur_1": [
      {
        "CurriculumCategory": "1. Alteryx",
        "Selection": "欠席"
      },
      {
        "CurriculumCategory": "2. Power BI",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "3. Power Automate",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "4. UiPath",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "5. Data Analysis",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "6. Power Apps",
        "Selection": "出席"
      }
    ]
  }
}

 

Scheme of Parse JSON;

 

{
  "type": "object",
  "properties": {
    "Email": {
      "type": "string"
    },
    "Applicant": {
      "type": "string"
    },
    "Dept": {
      "type": "string"
    },
    "DateOfApplication": {
      "type": "string"
    },
    "Cur_1": {
      "type": "array"
    }
  }
}

 

 Output of Parse JSON;

 

{
  "body": {
    "Email": "ks4050kt@power.com",
    "Applicant": "ks4050kt",
    "Dept": "PowerAutomate",
    "DateOfApplication": "2020-08-02 23:05:41Z",
    "Cur_1": [
      {
        "CurriculumCategory": "1. Alteryx",
        "Selection": "欠席"
      },
      {
        "CurriculumCategory": "2. Power BI",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "3. Power Automate",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "4. UiPath",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "5. Data Analysis",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "6. Power Apps",
        "Selection": "出席"
      }
    ]
  }
}

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Thanks for your quick reply.

 

Try to regenerate the schema of your Parse JSON again.

 

See below how to add a compose and map. Once it failed you can check the run history and see the compose value.

 

image.png



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

View solution in original post

6 REPLIES 6
abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

I have tested using your sample data using Parse JSON. Yes it is extracting the email attribute as expected. 

 

You haven't shown the runtime failures and run history values of your child flow. The screen shot you provided is the parent flow and its difficult to analyse the error.

 

Add a compose above the send email and map the email attribute. Check the run history and see what it returned.

 

For me it looks like there are situations email is not passed to child flow hence you getting the error. Check your PowerApp and see if email is mandatory or not? Looks like there is a data quality issue here.

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

@abm Thank you for your respond.

Actually below is the result what Child Flow ran and got;

{
  "body": {
    "Email": "ks4050kt@power.com",
    "Applicant": "ks4050kt",
    "Dept": "PowerAutomate",
    "DateOfApplication": "2020-08-02 23:05:41Z",
    "Cur_1": [
      {
        "CurriculumCategory": "1. Alteryx",
        "Selection": "欠席"
      },
      {
        "CurriculumCategory": "2. Power BI",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "3. Power Automate",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "4. UiPath",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "5. Data Analysis",
        "Selection": "出席"
      },
      {
        "CurriculumCategory": "6. Power Apps",
        "Selection": "出席"
      }
    ]
  }
}

Hence variable "Email" received the value, but it could not be passed to Email Sending action.

If I need to use compose to convert it, I'm not sure how to use compose action.

Previously the same child flow was working well, but changed the parent flow JSON. Originally PowerApps gave information with string directly by each items, but now PowerApps provided Array in JSON, then information is once parsed and initialized again in parent flow.

I assume this operation caused current matter, but I'm not sure what did it.

Thank you for your further advice.

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Thanks for your quick reply.

 

Try to regenerate the schema of your Parse JSON again.

 

See below how to add a compose and map. Once it failed you can check the run history and see the compose value.

 

image.png



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

@abm 

I tried to add "compose" as per your advice;

ks4050kt_0-1596414253628.png

Originally my variable contain Array in Object, is it possible to handle this type nesting variable??

{
  "": "",
  "Cur_1": [
    {
      "": "",
      "": ""
    }
  ]
}
Anonymous
Not applicable

Finally I got the successful result;

{
  "type": "object",
  "properties": {
    "body": {
      "type": "object",
      "properties": {
        "Email": {
          "type": "string"
        },
        "Applicant": {
          "type": "string"
        },
        "Dept": {
          "type": "string"
        },
        "DateOfApplication": {
          "type": "string"
        },
        "Cur_1": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "CurriculumCategory": {
                "type": "string"
              },
              "Selection": {
                "type": "string"
              }
            },
            "required": [
              "CurriculumCategory",
              "Selection"
            ]
          }
        }
      }
    }
  }
}

Parse JSON scheme was incorrect, to be generated from sample.

Thank you so much everyone's support.

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Thanks for your message.  The schema you provided was returning the email. I did mentioned earlier to generate the schema again. If you happy with the response please mark it as solution accepted.

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

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 (1,127)