You are doing your parse at the wrong level. You are trying to get orderID, but in the JSON you just posted OrderID is a property of Order which is a property of Orders. The sample you gave me was for the Order object. But you are doing a Parse Json on the whole thing. If it worked and you had the right schema Order ID would be
@body('Parse_JSON')?['Orders']?['Order']?['Order_ID']
The problem is the JSON you are using. All the keys are set to type. That's why they are all named that. You need to change the key names to individual values in the JSON text before you Parse it. Can you post an example of some of the JSON you are parsing?
@Pstork1 firstly , thanks for responding, that has been a big hurdle getting help.
I have taught myself some thins but is taking days !
1. I have XML files coming into Dropbox.
2. Once I get content I am Replacing '<![CDATA[ & ending ]]>' from that XML.
3. Compose to get the clean XML
4. I then use json(xml(outputs('Compose'))) to get the attached output.
message removed as irrelevant
How are you getting your Schema? Are you using a sample of the output from a run to generate the schema? or hand coding it? The schema doesn't look correct to me. The only references to arrays are in the required section. There should be a couple arrays of objects from the way you describe the data.
@Pstork1 If i use the payload fron the xml to json out put get errors as some orders have more than 1 Item. so if i use json from order that only has 1 items i get a fail for the items that have more than one. and vice versa.
@Pstork1 not sure of location as i havent heard back from you in hours? i am using json payload to create schema but the Parse json is return this schema every time? i cant clear the type
'
@Pstork1 the schema above is he schema that keeps getting set by the parse process? when I change it to the previous step output (Below) it just keeps coming back the same as above.
The Sample JSON you sent is invalid. It includes some extra braces and brackets at the end. But after I clean it up I get the following for a schema.
{
"type": "object",
"properties": {
"Order_ID": {
"type": "string"
},
"Order_Status": {
"type": "string"
},
"Order_Date": {
"type": "string"
},
"Customer_Email": {
"type": "string"
},
"Customer_Phone": {
"type": "string"
},
"Total_Quantity": {
"type": "string"
},
"Total_Shipped": {
"type": "string"
},
"Date_Shipped": {
"type": "string"
},
"Order_Notes": {
"type": "string"
},
"Customer_Message": {
"type": "string"
},
"Billing_First_Name": {
"type": "string"
},
"Billing_Last_Name": {
"type": "string"
},
"Billing_Street_1": {
"type": "string"
},
"Billing_Street_2": {
"type": "string"
},
"Billing_Suburb__State__Zip": {
"type": "string"
},
"Product_Details": {
"type": "object",
"properties": {
"item": {
"type": "array",
"items": {
"type": "object",
"properties": {
"Product_Qty": {
"type": "string"
},
"Product_SKU": {
"type": "string"
},
"Product_Name": {
"type": "string"
},
"Product_Variation_Details": {
"type": "string"
},
"Product_Unit_Price": {
"type": "string"
}
},
"required": [
"Product_Qty",
"Product_SKU",
"Product_Name",
"Product_Variation_Details",
"Product_Unit_Price"
]
}
}
}
}
}
}
The Parse JSON action then shows the following results.
Something about the JSON you are using to create the schema is invalid. Try using the schema I generated.
@Pstork1 data parses but get error for everything?
ExpressionEvaluationFailed. The execution of template action 'Apply_to_each_2' failed: the result of the evaluation of 'foreach' expression '@body('Parse_JSON')?['Order_ID']' is of type 'Null'. The result must be a valid array.
outputs from parse
{
"?xml": {
"@version": "1.0",
"@encoding": "UTF-8"
},
"orders": {
"order": {
"Order_ID": {
"#cdata-section": "343"
},
"Order_Status": {
"#cdata-section": "Awaiting Payment"
},
"Order_Date": {
"#cdata-section": "26/11/2021"
},
"Customer_Email": {
"#cdata-section": "admin@griffosautomotive.com.au"
},
"Customer_Phone": {
"#cdata-section": "02 6552 3874"
},
"Total_Quantity": {
"#cdata-section": "6"
},
"Total_Shipped": {
"#cdata-section": "0"
},
"Date_Shipped": {
"#cdata-section": ""
},
"Order_Notes": {
"#cdata-section": ""
},
"Customer_Message": {
"#cdata-section": "Can we please include these as part of the New RAS Member welcome pack?"
},
"Billing_First_Name": {
"#cdata-section": "Griffo's Automotive"
},
"Billing_Last_Name": {
"#cdata-section": "1692"
},
"Billing_Street_1": {
"#cdata-section": "3 Beeton Parade"
},
"Billing_Street_2": {
"#cdata-section": ""
},
"Billing_Suburb__State__Zip": {
"#cdata-section": "Taree NSW 2430"
},
"Product_Details": {
"item": [
{
"Product_Qty": {
"#cdata-section": "3"
},
"Product_SKU": {
"#cdata-section": "RPOLO-2XL"
},
"Product_Name": {
"#cdata-section": "Poly Cotton Polo Shirt"
},
"Product_Variation_Details": {
"#cdata-section": "Size: 2XLarge, Extra Decoration: Business Logo Only"
},
"Product_Unit_Price": {
"#cdata-section": "36.90"
}
},
{
"Product_Qty": {
"#cdata-section": "1"
},
"Product_SKU": {
"#cdata-section": "R2146-CHILI-10"
},
"Product_Name": {
"#cdata-section": "Ladies Ezylin Blouse"
},
"Product_Variation_Details": {
"#cdata-section": "Colour: Red, Style: Short Sleeve, Size: 10, Embroidery: Business Name only"
},
"Product_Unit_Price": {
"#cdata-section": "74.75"
}
},
{
"Product_Qty": {
"#cdata-section": "1"
},
"Product_SKU": {
"#cdata-section": "R2145-CHILI-10"
},
"Product_Name": {
"#cdata-section": "Ladies Ezylin Blouse"
},
"Product_Variation_Details": {
"#cdata-section": "Colour: Red, Style: 3/4 Sleeve, Size: 10, Embroidery: Business Name only"
},
"Product_Unit_Price": {
"#cdata-section": "74.75"
}
},
{
"Product_Qty": {
"#cdata-section": "1"
},
"Product_SKU": {
"#cdata-section": "R6V1CNBX10"
},
"Product_Name": {
"#cdata-section": "Ladies Crew Neck Vest"
},
"Product_Variation_Details": {
"#cdata-section": "Color: Black, Size: 10, Embroidery: Business Name only"
},
"Product_Unit_Price": {
"#cdata-section": "45.00"
}
}
]
}
}
}
}
You are doing your parse at the wrong level. You are trying to get orderID, but in the JSON you just posted OrderID is a property of Order which is a property of Orders. The sample you gave me was for the Order object. But you are doing a Parse Json on the whole thing. If it worked and you had the right schema Order ID would be
@body('Parse_JSON')?['Orders']?['Order']?['Order_ID']
@Pstork1 hank you again for your response and My apologies for that, learning as I go that accurate data posting is a benefit here. I did pick that up and I Practiced on it and was able to did adjust my schema to include the Orders. Order scenario to my schema, and it is parsing Ok But It does roll into another situation with dealing with Objects and Arrays in the inputs causing the parse to fail again. (have raised another discussion on this, parse-Json-Failing-due-to-Objects-and-Array-in-same-XML-call so do you think it best close this discussion as the answer about the disappearing Outputs?
{
"type": "object",
"properties": {
"orders": {
"type": "object",
"properties": {
"order": {
"type": "array",
"items": {
"type": "object",
"properties": {
"Order_ID": {
"type": "string"
},
"Order_Status": {
"type": "string"
},
"Order_Date": {
"type": "string"
},
"Customer_Email": {
"type": "string"
},
"Customer_Phone": {
"type": "string"
},
"Total_Quantity": {
"type": "string"
},
"Total_Shipped": {
"type": "string"
},
"Date_Shipped": {
"type": "string"
},
"Order_Notes": {
"type": "string"
},
"Customer_Message": {
"type": "string"
},
"Billing_Last_Name": {
"type": "string"
},
"Billing_Street_1": {
"type": "string"
},
"Billing_Street_2": {
"type": "string"
},
"Billing_Suburb__State__Zip": {
"type": "string"
},
"Product_Details": {
"type": "object",
"properties": {
"item": {
"type": "object",
"properties": {
"Product_Qty": {
"type": "string"
},
"Product_SKU": {
"type": "string"
},
"Product_Name": {
"type": "string"
},
"Product_Variation_Details": {
"type": "string"
},
"Product_Unit_Price": {
"type": "string"
}
}
}
}
}
},
"required": [
"Order_ID",
"Order_Status",
"Order_Date",
"Customer_Email",
"Customer_Phone",
"Total_Quantity",
"Total_Shipped",
"Date_Shipped",
"Order_Notes",
"Customer_Message",
"Billing_Last_Name",
"Billing_Street_1",
"Billing_Street_2",
"Billing_Suburb__State__Zip",
"Product_Details"
]
}
}
}
}
}
}
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