Hey people 😁
I'm building a flow using parse json to populate a new lead row. I've used this method before in other flows and it has worked like a charm ✨
This time I've encountered something weird that I can't seem to solve! Please help me!
When using parse Json theres data in the output, but when I use the dynamic values later on, the values are empty. How come?
This is the data I receive - note that the output has lots of values, as it should have.
Naturally I initialize some variables for later use:
When testing the flow, this is the output of the set variables:
This also happen when I use the dynamic content from parse Json directly into "add a new row". There are no error messages, except from when I add them to a new record. Then I get this error:
I believe the error is just there because the dynamic content from the json are empty.
Has someone encountered something similar before?
Some tips & tricks and solutions would be much appreciated! 🙃
Hello @NoraMoller
Your schema is wrong. You are searching for firstname inside of mdmUserInfo. Here you don’t find it, that is why it is null.
Why do you use so many variables? If you don’t change them it just slows down the flow, I would suggest to get rid of those actions.
Matty is right,
your schema is looking for firstname under the mdmUserInfo branch, your schema should be
{
"type":"object",
"properties":{
"firstname":{
"type":"string"
},
etc
The best tip is take your input from the flow run and use it to generate from sample. If you did that then looks like you have multiple different schemas and need to add logic to handle them.
Hey Dave,
I'm having a similar issue. I've taking my JSON raw output data and used that to generate my schema. The parsed output shows just fine, but when I use the dynamic content fields, it's blank. Any chance you can tell me what I'm missing here?
Here's my flow:
The raw output data from the "Parsed JSON" step:
{
"body": {
"formDataList": {
"completed": "2024-02-16 07:31:12",
"email": "removed",
"role": "SIGNER",
"first": "Test",
"last": "",
"title": "",
"company": "",
"initials": "TT",
"AP Contact": "1",
"AP Email Address": "1",
"Account Numbers": "",
"Account Numbers_2": "",
"Address_3": "1",
"Address_4": "",
"Annual Sales": "1",
"Applicant Company Address": "",
"Applicant Company Name Company": "",
"Applicant Name": "1",
"Applicant Title": "1",
"ApplicantName": "",
"ApplicantTitle": "",
"Bankruptcy": "No",
"Billing Address": "removed",
"BillingCityStateZip": "removed",
"Business Type": "LLC",
"CityStateZip_3": "1",
"CityStateZip_4": "",
"CityStateZip_5": "",
"CityStateZip_6": "",
"CityStateZip_7": "",
"CompanyName": "removed",
"Contact": "",
"Contact_2": "",
"DBA": "",
"Date_2": "",
"Date_3": "",
"Date_4": "",
"Date_5": "",
"Email": "",
"EmailRow1": "1",
"EmailRow1_2": "",
"EmailRow1_3": "",
"Email_2": "",
"Email_3": "",
"Email_4": "",
"EstDate": "",
"FEID": "1",
"Fax": "",
"Fax_10": "",
"Fax_11": "",
"Fax_12": "",
"Fax_13": "",
"Fax_2": "",
"Fax_3": "",
"Fax_4": "",
"Fax_5": "",
"Fax_6": "",
"Fax_7": "",
"Fax_8": "",
"Fax_9": "",
"Home Address": "",
"Home Address_2": "",
"Home Address_3": "",
"Limit Request": "$1",
"Name_10": "",
"Name_11": "",
"Name_12": "",
"Name_13": "",
"Name_14": "",
"Name_15": "",
"Name_16": "1",
"Name_4": "1",
"Name_5": "",
"Name_6": "",
"Name_7": "",
"Name_8": "1",
"Name_9": "1",
"Owner2Address": "",
"Owner2Name": "",
"Owner2Ownership": "",
"Owner2Title": "",
"OwnerAddress": "1",
"OwnerName": "1",
"OwnerTitle": "1",
"Ownership": "1",
"Phone": "",
"Phone_10": "",
"Phone_11": "",
"Phone_12": "",
"Phone_2": "1",
"Phone_3": "",
"Phone_4": "",
"Phone_5": "",
"Phone_6": "",
"Phone_7": "",
"Phone_8": "1",
"Phone_9": "1",
"Primary Bank": "1",
"Purchase_Auth": "",
"SSN": "",
"SSN_2": "",
"SSN_3": "",
"Salesrep": "Gustavo Carmena",
"Secondary Bank": "",
"ShipCityStateZip": "1",
"Shipping Address": "1",
"Signature 1": "",
"Signature 2": "",
"Signature 3": "",
"State of EstablishmentIncorporation": "1",
"Telephone": "1",
"Title_4": "1",
"Title_5": "",
"Title_6": "",
"Title_7": "",
"Title_8": "1",
"agreementId": "removed",
"email verified": "2024-02-16 07:31:12",
"web form signed/approved": "2024-02-16 07:31:10"
}
}
}
I used that data to create the scheme automatically. I'm able to see the fields in dynamic content and select them in the last step:
But for some reason the raw input data for that step is blank:
Here's the schema if it helps:
{
"type": "object",
"properties": {
"statusCode": {
"type": "integer"
},
"headers": {
"type": "object",
"properties": {
"Cache-Control": {
"type": "string"
},
"Pragma": {
"type": "string"
},
"ETag": {
"type": "string"
},
"X-Robots-Tag": {
"type": "string"
},
"X-Request-ID": {
"type": "string"
},
"Strict-Transport-Security": {
"type": "string"
},
"X-XSS-Protection": {
"type": "string"
},
"X-Content-Type-Options": {
"type": "string"
},
"P3P": {
"type": "string"
},
"Timing-Allow-Origin": {
"type": "string"
},
"x-ms-apihub-cached-response": {
"type": "string"
},
"x-ms-apihub-obo": {
"type": "string"
},
"Date": {
"type": "string"
},
"Content-Length": {
"type": "integer"
},
"Content-Type": {
"type": "string"
},
"Expires": {
"type": "string"
}
}
},
"body": {
"type": "object",
"properties": {
"formDataList": {
"type": "object",
"properties": {
"completed": {
"type": "string"
},
"email": {
"type": "string"
},
"role": {
"type": "string"
},
"first": {
"type": "string"
},
"last": {
"type": "string"
},
"title": {
"type": "string"
},
"company": {
"type": "string"
},
"initials": {
"type": "string"
},
"AP Contact": {
"type": "string"
},
"AP Email Address": {
"type": "string"
},
"Account Numbers": {
"type": "string"
},
"Account Numbers_2": {
"type": "string"
},
"Address_3": {
"type": "string"
},
"Address_4": {
"type": "string"
},
"Annual Sales": {
"type": "string"
},
"Applicant Company Address": {
"type": "string"
},
"Applicant Company Name Company": {
"type": "string"
},
"Applicant Name": {
"type": "string"
},
"Applicant Title": {
"type": "string"
},
"ApplicantName": {
"type": "string"
},
"ApplicantTitle": {
"type": "string"
},
"Bankruptcy": {
"type": "string"
},
"Billing Address": {
"type": "string"
},
"BillingCityStateZip": {
"type": "string"
},
"Business Type": {
"type": "string"
},
"CityStateZip_3": {
"type": "string"
},
"CityStateZip_4": {
"type": "string"
},
"CityStateZip_5": {
"type": "string"
},
"CityStateZip_6": {
"type": "string"
},
"CityStateZip_7": {
"type": "string"
},
"CompanyName": {
"type": "string"
},
"Contact": {
"type": "string"
},
"Contact_2": {
"type": "string"
},
"DBA": {
"type": "string"
},
"Date_2": {
"type": "string"
},
"Date_3": {
"type": "string"
},
"Date_4": {
"type": "string"
},
"Date_5": {
"type": "string"
},
"Email": {
"type": "string"
},
"EmailRow1": {
"type": "string"
},
"EmailRow1_2": {
"type": "string"
},
"EmailRow1_3": {
"type": "string"
},
"Email_2": {
"type": "string"
},
"Email_3": {
"type": "string"
},
"Email_4": {
"type": "string"
},
"EstDate": {
"type": "string"
},
"FEID": {
"type": "string"
},
"Fax": {
"type": "string"
},
"Fax_10": {
"type": "string"
},
"Fax_11": {
"type": "string"
},
"Fax_12": {
"type": "string"
},
"Fax_13": {
"type": "string"
},
"Fax_2": {
"type": "string"
},
"Fax_3": {
"type": "string"
},
"Fax_4": {
"type": "string"
},
"Fax_5": {
"type": "string"
},
"Fax_6": {
"type": "string"
},
"Fax_7": {
"type": "string"
},
"Fax_8": {
"type": "string"
},
"Fax_9": {
"type": "string"
},
"Home Address": {
"type": "string"
},
"Home Address_2": {
"type": "string"
},
"Home Address_3": {
"type": "string"
},
"Limit Request": {
"type": "string"
},
"Name_10": {
"type": "string"
},
"Name_11": {
"type": "string"
},
"Name_12": {
"type": "string"
},
"Name_13": {
"type": "string"
},
"Name_14": {
"type": "string"
},
"Name_15": {
"type": "string"
},
"Name_16": {
"type": "string"
},
"Name_4": {
"type": "string"
},
"Name_5": {
"type": "string"
},
"Name_6": {
"type": "string"
},
"Name_7": {
"type": "string"
},
"Name_8": {
"type": "string"
},
"Name_9": {
"type": "string"
},
"Owner2Address": {
"type": "string"
},
"Owner2Name": {
"type": "string"
},
"Owner2Ownership": {
"type": "string"
},
"Owner2Title": {
"type": "string"
},
"OwnerAddress": {
"type": "string"
},
"OwnerName": {
"type": "string"
},
"OwnerTitle": {
"type": "string"
},
"Ownership": {
"type": "string"
},
"Phone": {
"type": "string"
},
"Phone_10": {
"type": "string"
},
"Phone_11": {
"type": "string"
},
"Phone_12": {
"type": "string"
},
"Phone_2": {
"type": "string"
},
"Phone_3": {
"type": "string"
},
"Phone_4": {
"type": "string"
},
"Phone_5": {
"type": "string"
},
"Phone_6": {
"type": "string"
},
"Phone_7": {
"type": "string"
},
"Phone_8": {
"type": "string"
},
"Phone_9": {
"type": "string"
},
"Primary Bank": {
"type": "string"
},
"Purchase_Auth": {
"type": "string"
},
"SSN": {
"type": "string"
},
"SSN_2": {
"type": "string"
},
"SSN_3": {
"type": "string"
},
"Salesrep": {
"type": "string"
},
"Secondary Bank": {
"type": "string"
},
"ShipCityStateZip": {
"type": "string"
},
"Shipping Address": {
"type": "string"
},
"Signature 1": {
"type": "string"
},
"Signature 2": {
"type": "string"
},
"Signature 3": {
"type": "string"
},
"State of EstablishmentIncorporation": {
"type": "string"
},
"Telephone": {
"type": "string"
},
"Title_4": {
"type": "string"
},
"Title_5": {
"type": "string"
},
"Title_6": {
"type": "string"
},
"Title_7": {
"type": "string"
},
"Title_8": {
"type": "string"
},
"agreementId": {
"type": "string"
},
"email verified": {
"type": "string"
},
"web form signed/approved": {
"type": "string"
}
}
}
}
}
}
}
Any help at all would be greatly appreciated!
Hi @aisabel ,
Your parse JSON looks right, would you be able to copy and share the companyName from the outlook action, should be something like
@{body('parseJSON')?['companyName']}
Thanks so much for answering!
Here's the code view of the message in teams:
"body/messageBody": "
<p>A credit application has been submitted.<br>
\nCompany: @{body('Parse_JSON')?['body']?['formDataList']?['CompanyName']}<br>
\nSalesperson: @{body('Parse_JSON')?['body']?['formDataList']?['Salesrep']}<br>
\nPlease allow processing by the credit department.</p>"
I tried a quick demo and it worked for me. At a guess it could be what you are passing into the parse JSON, try passing just the body and not the response.
Something like this
Outputs('Get_form_field_data_of_agreement_in_JSON_format')['body']
If that doesn't work try adding
"required": [
"CompanyName"
],
to the schema body, as this will force the action to fail if the key is missing (and that way you know it's the json input that is the issue)
I was able to figure it out!
Your suggestions didn't work, but only because the requirement was being filled. I knew it was something with the schema, so I used only the "formdataoutput" from the previous step to create the schema, and that worked. (I was previously using the raw data output.
Thank you!
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!
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
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.
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