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

ValidationFailed Parse JSON

Hello,

  I received this error, "ValidationFailed. The schema validation failed.", for the Parse JSON data operation function. The app further noted, "This is a new issue. Try posting about it on our community page—somebody may have a fix. Post it now" 🙂

This error is coming after a select step at the Parse JSON function. (Plz ignore the Create CSV Table <- I was trying something which sorta worked but not really, not as twitchy-clean as I wanted 😛 )  My end goal here is to shove the values of 'Select_Data_Into_New_Array' TriggerIssue && TriggerWorkstation && TriggerThreshold into previously initialized variables (set to string).  Any ideas, help, memes or even sarcasm is greatly appreciated at this time. 

Screenshot Overview.png

 

I use a successful RUN and grabbed a sample from the RAW Output from the Select step.  

Raw Output of sample.png

 

I copy and pasted the above RAW output into the "Generate from Sample" window in the Parse JSON step. This is what it generated. 

code beautify.png

 

1 ACCEPTED SOLUTION

Accepted Solutions

@Pstork1 IT WORKS!!!!
Thank you for your replies and helping with the "brian stew" !!!
I took the raw intput contents with the square brackets, added it to the autogenerator and bam! success! Now I am in an Apply To Each loop (power automates equivalent of ForEach I guess) and I can assign the value for my previously declared variables. Thank you! 🙂 

If anyone else gets that Validation error and reads this thread, for me in this instance it was clearly related to the SCHEMA. 
Cheers, 

it works.png

 

View solution in original post

9 REPLIES 9

Here's the error output.

 

{
    "errors": [
        {
            "message""Invalid type. Expected Object but got Array.",
            "lineNumber"0,
            "linePosition"0,
            "path""",
            "schemaId""#",
            "errorType""type",
            "childErrors": []
        }
    ]
}

I suspect that when you created the schema you used the entire body, but when parsing the output you are only using array inside the body.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

@Pstork1 Thank you kindly for your reply. To answer with any accuracy I would need you to be more specific. This is 1 component of a larger flow of logic. If you look at the step "Select Data Into New Array" you can see I'm using content from a previous step labelled as "arrMessages". Using that content I remap to labels that I define. This is done in the Select step. (I have since deleted the CSV table step, it no longer served a purpose anyways) 
The RAW Output of that select step is pasted as a screenshot above. I selected the whole thing, copied it and pasted it into the Generate window as described. Can you point me to where I may have inserted the incorrect data? I feel like this should be very simple and I'm missing something obvious. So I'm a-okay triple checking everything to find the "Office Space decimal point" that's in the wrong spot 😄

 

$varTriggerIssue = $select_data_into_new_array[0].TriggerIssue <--- this is really what I want to do.. how do I do that in PowerAutomate? Maybe parse Json after the select is the wrong thing to do ? I tried set variable in various ways and kept failing.... (varTriggerIssue has been previously initialized as a string with no value)
 

When you run the Parse Json I suspect you are are parsing the JSON array called body in your ouput.  But if you copy all of that output and put it in to generate the schema it will generate a schema for an unnamed object that contains an array called body.  To generate your schema you only want the section from the opening '[' to the closing ']' not everything inside the {}.

 



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

I tried again with a custom schema and received the same error and similar error output. In my mind it is clearly the schema and it is a matter of tweaking it -OR I'm going about this incorrectly and there's 1001x easier method than this 🙂 (anyone have any online schema generators they recommend?)
#Error Below

[
  {
    "message""Invalid type. Expected Object but got Array.",
    "lineNumber"0,
    "linePosition"0,
    "path""",
    "schemaId""#",
    "errorType""type",
    "childErrors": []
  }
]

#This is the schema that generated the above error

{
    "type""object",
    "properties": {
        "TriggerIssue": {
            "type""string"
            },
        "TriggerWorkstation": {
            "type""string"
            },
        "TriggerThreshold": {
            "type""string"
            }
    },
    "required": [
        "TriggerIssue",
        "TriggerWorkstation",
        "TriggerThreshold"
        ]
}
Tried with custom schema 7APR.png

 

I see what you are saying. I used the raw output, this:

{
    "body": [
        {
            "TriggerIssue""Empty TriggerIssue",
            "TriggerWorkstation""Empty Trigger Workstation",
            "TriggerThreshold""Empty Trigger Threshold"
        }
    ]
}
 
What you are suggesting is using this with the auto-generator:
{
"TriggerIssue": "Empty TriggerIssue",
"TriggerWorkstation": "Empty Trigger Workstation",
"TriggerThreshold": "Empty Trigger Threshold"
}

Trying now..... 

@Pstork1 no dice mate; close but no cigar 😄 You can see as it comes in as RAW input, there's square brackets around the array - so it's an object with an array (unless I'm reading it wrong) - would compose be better than Parse JSON ? 

Tried with suggestion 1.png

 

@Pstork1 IT WORKS!!!!
Thank you for your replies and helping with the "brian stew" !!!
I took the raw intput contents with the square brackets, added it to the autogenerator and bam! success! Now I am in an Apply To Each loop (power automates equivalent of ForEach I guess) and I can assign the value for my previously declared variables. Thank you! 🙂 

If anyone else gets that Validation error and reads this thread, for me in this instance it was clearly related to the SCHEMA. 
Cheers, 

it works.png

 

Try this schema

{
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "TriggerIssue": {
        "type": "string"
      },
      "TriggerWorkstation": {
        "type": "string"
      },
      "TriggerThreshold": {
        "type": "string"
      }
    },
    "required": [
      "TriggerIssue",
      "TriggerWorkstation",
      "TriggerThreshold"
    ]
  }
}


-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

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,664)