Hi All
I'm building a flow to accept some json from an external company. My flow is receiving the data but when I try to use the data (for example in a create new record or just a compose action) I get an error saying "......Property selection is not supported on values of type 'String'."
Below are the details of my flow and the results of my test.
As far as I can see from the web, what I'm doing should work - thanks for your help!
THE JSON PAYLOAD
THE FLOW DESIGN
RESULTS OF THE TEST
Schema (created with a sample payload)
Accepted Solutions
Hi @v-siky-msft
I posted quite a long reply to you on Thursday night, but I've just noticed it hasn't appeared on here!! Basically the test data comes from an external company with whom I have an account - I log in to my account on their website and can add my webhook URL and can then send test payloads to the URL direct from their website.
Anyway, I've had a play today and have found a workaround that seems to work - instead of trying to use the output of the When a HTTP request is received trigger I have added a Parse JSON action. With some trial and error I wrote a sample JSON to use to generate the schema by removing all the actual data from my test JSON and replacing with with Null - see under the message. I've also copied the schema generated from this sample.
I then used a compose action and a CDS create record action to test it and, by using the dynamic content from the Parse JSON action it all worked fine.
I also tried using my sample JSON to create the schema for the When a HTTP request is received trigger - but it still didn't work!
Anyway, thanks so much for your time and help, it was very much appreciated.
Simon
MY SAMPLE JSON
{"result":{"additionalDetails":null,"addressLine1":null,"addressLine2":null,"addressLine3":null,"addressLine4":null,"bedrooms":null,"cancelled":null,"competingCompanies":null,"county":null,"createdAt":null,"customerName":null,"email":null,"houseType":null,"phone":null,"postcode":null,"price":null,"propertyType":null,"quoteId":null,"surveyType":null,"town":null},"timestamp":null,"token":null,"signature":null}
THE RESULTING PARSE JSON SCHEMA
Additional details: Additional details go here.
123 Test St
Test Town
CF11 9HB
Beds: 3
Competing Cos: 0
County: Test County
Created at: 2020-12-09 16:30:32
Name: Test Customer
Email: test@email.com
House type: detached
Phone: 00000111111
Price: £233000
Property Type: house
Quote id: Tes-1607531432
Survey Type: Home Buyer
Timestamp: 1607531432
Token: xxxxxxxxxxxxx
Signature: xxxxxxxxxxxxxxx
Hi @sdowse ,
The JSON schema is incomplete, the JSON schema lacks the properties of result, timestamp, token and signature.
Please use the whole JSON payload in Notepad to generate the schema.
Another method is to change the customerName expression as follows, but I still suggest you generate a complete JSON schema
triggerBody()['result/customerName']Hi @v-siky-msft
Thanks so much for your advice - I've re-done the schema (see below the screenshots) but I still get an error message - see screenshots of 2 error messages, one for the original customer name expression and one using your suggested expression. Any ideas what I might be doing wrong?!
Simon
{
"type": "object",
"properties": {
"result": {
"type": "object",
"properties": {
"additionalDetails": {
"type": "string"
},
"addressLine1": {
"type": "string"
},
"addressLine2": {
"type": "string"
},
"addressLine3": {
"type": "string"
},
"addressLine4": {
"type": "string"
},
"bedrooms": {
"type": "integer"
},
"cancelled": {
"type": "string"
},
"competingCompanies": {
"type": "integer"
},
"county": {
"type": "string"
},
"createdAt": {
"type": "string"
},
"customerName": {
"type": "string"
},
"email": {
"type": "string"
},
"houseType": {
"type": "string"
},
"phone": {
"type": "string"
},
"postcode": {
"type": "string"
},
"price": {
"type": "integer"
},
"propertyType": {
"type": "string"
},
"quoteId": {
"type": "string"
},
"surveyType": {
"type": "string"
},
"town": {
"type": "string"
}
}
},
"timestamp": {
"type": "integer"
},
"token": {
"type": "string"
},
"signature": {
"type": "string"
}
}
}
Hi @v-siky-msft
I have an account with a company who send me leads - I log into my account on their website and input the HTTP Post URL that the "When a HTTP request is received" trigger generates.
Their website has a test facility so I can get it to send me a test payload of JSON (sorry, I'm not sure what the exact term is!).
The payload arrives at my Flow and I use the first Compose action to show me what is received , which is this:
{"result":{"additionalDetails":"Additional details go here.","addressLine1":"123 Test St","addressLine2":null,"addressLine3":null,"addressLine4":null,"bedrooms":3,"cancelled":null,"competingCompanies":0,"county":"Test County","createdAt":"2020-12-09 16:30:32","customerName":"Test Customer","email":"test@email.com","houseType":"detached","phone":"00000111111","postcode":"CF11 9HB","price":233000,"propertyType":"house","quoteId":"Tes-1607531432","surveyType":"Home Buyer","town":"Test Town"},"timestamp":1607531432,"token":"XXXXXXXXX","signature":"XXXXXXXX"}
But.... the first time I did it was a bit different, and this is why my original schema was wrong (as you noticed). I couldn't activate their test functionality without giving them a URL, and I couldn't generate the URL without an example payload - so when the company next sent me a lead via email they attached a file to it which was the JSON payload - except it wasn't exactly the same as that sent by their test - as you noticed!
So I then deleted my original trigger and created a new one with the "full" JSON from the test - that gave me a new URL which I updated on the other company's website. I then tried some more tests which is when I got the error messages I attached to my last post. So the data is arriving from the other company but Flow seems to be having an issue dealing with it.
I'll post some screenshots of the last failed run (which is where the JSON above came from) below.
Thanks again for your help.
Simon
Hi @v-siky-msft
I posted quite a long reply to you on Thursday night, but I've just noticed it hasn't appeared on here!! Basically the test data comes from an external company with whom I have an account - I log in to my account on their website and can add my webhook URL and can then send test payloads to the URL direct from their website.
Anyway, I've had a play today and have found a workaround that seems to work - instead of trying to use the output of the When a HTTP request is received trigger I have added a Parse JSON action. With some trial and error I wrote a sample JSON to use to generate the schema by removing all the actual data from my test JSON and replacing with with Null - see under the message. I've also copied the schema generated from this sample.
I then used a compose action and a CDS create record action to test it and, by using the dynamic content from the Parse JSON action it all worked fine.
I also tried using my sample JSON to create the schema for the When a HTTP request is received trigger - but it still didn't work!
Anyway, thanks so much for your time and help, it was very much appreciated.
Simon
MY SAMPLE JSON
{"result":{"additionalDetails":null,"addressLine1":null,"addressLine2":null,"addressLine3":null,"addressLine4":null,"bedrooms":null,"cancelled":null,"competingCompanies":null,"county":null,"createdAt":null,"customerName":null,"email":null,"houseType":null,"phone":null,"postcode":null,"price":null,"propertyType":null,"quoteId":null,"surveyType":null,"town":null},"timestamp":null,"token":null,"signature":null}
THE RESULTING PARSE JSON SCHEMA
Additional details: Additional details go here.
123 Test St
Test Town
CF11 9HB
Beds: 3
Competing Cos: 0
County: Test County
Created at: 2020-12-09 16:30:32
Name: Test Customer
Email: test@email.com
House type: detached
Phone: 00000111111
Price: £233000
Property Type: house
Quote id: Tes-1607531432
Survey Type: Home Buyer
Timestamp: 1607531432
Token: xxxxxxxxxxxxx
Signature: xxxxxxxxxxxxxxx
Helpful resources
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
