cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
oappdev
Post Prodigy
Post Prodigy

Parse JSON Schema - Required properties are missing from object.

Hello Power Automate Community,

 

So I have the following fields:

First NameRow1,Last NameRow1
First NameRow1_2,LastName Row1_2
First NameRow1_3,LastName Row1_3
First NameRow1_4,LastName Row1_4
First NameRow1_5,LastName Row1_5

 

Still learning JSON,  What would be an sample JSON to Fill in the rest of the pending fields. 

 

INPUT Content:

 

 

[
    {
        "First NameRow1": "John",
        "Last NameRow1": "Doe",
    },
    {
        
        "First NameRow1": "John",
        "Last NameRow1": "Doe1",
        
    }
]

 

 

 

Schema:

 

 

[
    {
        "First NameRow1": "",
        "Last NameRow1": "",
    },
    {
        "First NameRow1_2": "",
        "Last NameRow1_2": "",        
    },
    {
        "First NameRow1_3": "",
        "Last NameRow1_3": "",        
    },
    {
        "First NameRow1_4": "",
        "Last NameRow1_4": "",        
    },
    {
        "First NameRow1_5": "",
        "Last NameRow1_5": ""
    },
"required": [
      "First NameRow1",
      "Last NameRow1",
      "First NameRow1_2",
      "Last NameRow1_2",
      "First NameRow1_3",
      "Last NameRow1_3",
      "First NameRow1_4",
      "Last NameRow1_4",
      "First NameRow1_4",
      "Last NameRow1_4",
      "First NameRow1_5",
      "Last NameRow1_5"

    ]
 }
]

 

 

 

OUTPUT Errors:

 

 

[
  {
    "message": "Required properties are missing from object: First NameRow1_2, Last NameRow1_2,First NameRow1_3,Last NameRow1_3,First NameRow1_4,Last NameRow1_4,First NameRow1_5,Last NameRow1_5",
    "lineNumber": 0,
    "linePosition": 0,
    "path": "[0]",
    "value": [
      "First NameRow1_2",
      "Last NameRow1_2",
      "First NameRow1_3",
      "Last NameRow1_3",
      "First NameRow1_4",
      "Last NameRow1_4",
      "First NameRow1_5",
      "Last NameRow1_5"
    ],
    "schemaId": "#/items",
    "errorType": "required",
    "childErrors": []
  }
]

 

 

 

As always, Thank you so much in advance.

 

1 ACCEPTED SOLUTION

Accepted Solutions
Pstork1
Most Valuable Professional
Most Valuable Professional

A JSON array is denoted by the use of square brackets [].  Inside the brackets are comma delimited records denoted by curly braces {}.  Each record consists of properties that have a "Name": and "value".  Multiple properties are separated by commas.  So your input is almost a valid JSON array.  The commas after the last properties should be removed.  The following is a valid JSON array.

[
    {
        "First NameRow1": "John",
        "Last NameRow1": "Doe"
    },
    {
        
        "First NameRow1": "Paul",
        "Last NameRow1": "Stork"
        
    }
]

 Note that the property names are repeated for each record.  You don't want different property names.  The schema for the JSON array above is

{
    "type": "array",
    "items": {
        "type": "object",
        "properties": {
            "First NameRow1": {
                "type": "string"
            },
            "Last NameRow1": {
                "type": "string"
            }
        },
        "required": [
            "First NameRow1",
            "Last NameRow1"
        ]
    }
}

You'll notice the section at the end called "required" this is the list of properties that each object in the array MUST have.  In your example you changed the property name for each object and listed all the variations as required.  But each object only had a few of those properties.  That's why you are getting an error.



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

View solution in original post

10 REPLIES 10
Pstork1
Most Valuable Professional
Most Valuable Professional

A JSON array is denoted by the use of square brackets [].  Inside the brackets are comma delimited records denoted by curly braces {}.  Each record consists of properties that have a "Name": and "value".  Multiple properties are separated by commas.  So your input is almost a valid JSON array.  The commas after the last properties should be removed.  The following is a valid JSON array.

[
    {
        "First NameRow1": "John",
        "Last NameRow1": "Doe"
    },
    {
        
        "First NameRow1": "Paul",
        "Last NameRow1": "Stork"
        
    }
]

 Note that the property names are repeated for each record.  You don't want different property names.  The schema for the JSON array above is

{
    "type": "array",
    "items": {
        "type": "object",
        "properties": {
            "First NameRow1": {
                "type": "string"
            },
            "Last NameRow1": {
                "type": "string"
            }
        },
        "required": [
            "First NameRow1",
            "Last NameRow1"
        ]
    }
}

You'll notice the section at the end called "required" this is the list of properties that each object in the array MUST have.  In your example you changed the property name for each object and listed all the variations as required.  But each object only had a few of those properties.  That's why you are getting an error.



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

Thank you so much! @Pstork1 Will give it a try. 

@Pstork1 What l'm i missing or doing wrong?

 

Error:

 

Additional text encountered after finished reading JSON content: ,. Path '', line 4, position 1.

 

JSONError.PNG

 

Sorry, been under a lot of pressure.

Pstork1
Most Valuable Professional
Most Valuable Professional

From what I can see of the input, you've got two JSON records, but no Array.  There should be square brackets around the JSON for it to be an array.

Yours

{
 record
},
{
 record2
}

should be 

[
{
 record
},
{
 record2
}
]


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

I have a table with 3 properties out of which only two properties have data in it. I have using SQL connector to get the data and then passing it into a "Parse JSON" module. 

Following is the output of my SQL Connector:

{
  "@odata.context": "https://logic-apis-southeastasia.azure-apim.net/apim/sql/somethings/items",
  "value": [
    {
      "@odata.etag": "",
      "ItemInternalId": "Some alpha-numeric id",
      "userEmail": "somename@blabla.com",
      "someCode": "someCode"
    },
    {
      ...
    },
    ...
  ]
}


As you ( @Pstork1 ) explained in your solution,  For the above output, my JSON Schema is as follows for "Values" tag:

{
    "type": "array",
    "items": {
        "type": "object",
        "properties": {
            "@@odata.etag": {
                "type": "string"
            },
            "ItemInternalId": {
                "type": "string"
            },
            "userEmail": {
                "type": "string"
            },
            "someCode": {
                "type": "string"
            }
        },
        "required": [
            "@@odata.etag",
            "ItemInternalId",
            "userEmail",
            "someCode"
        ]
    }
}

 
 When I run my Logic App, I get the following error in the "Parse JSON" connector:

[
  {
    "message": "Required properties are missing from object: someCode.",
    "lineNumber": 0,
    "linePosition": 0,
    "path": "[318]",
    "value": [],
    "schemaId": "#/items",
    "errorType": "required",
    "childErrors": []
  }
]

Initially I had 4-5 data pointers in my table and the Parse JSON connector was working fine. I inserted few more records and now I am getting this error. I can't understand what could be the problem here.. 

Please help.

Since some of the fields are null for some records you can't list them as required properties in the schema.  You need to do two things.  Edit the schema to change the type designator for those properties to allow eiter a string or a null.

            "someCode": {
                "type": ["string", "null"]
            }

and remove them from the list of required properties.

        "required": [
            "@@odata.etag",
            "ItemInternalId",
            "userEmail",
            "someCode" <- Delete this line and the comma at the end of the previous line
        ]

 



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

if we put this condition and remove the Columns in "required 

we cannot custom select columns after parse json step. resulting with table[COLUMN1] as column header In the attachment. is there a way we can get only columns instaed of table[column names] 

Pstork1
Most Valuable Professional
Most Valuable Professional

Are you saying that you aren't seeing the columns as dynamic content? If so please post this as a new question because that should not be happening if you entered the values correctly as described.



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

I am trying to create scheduled power automate flow using Run a query against a dataset to send an email with data in csv format. I copied the dax code from Optimize--> performance analyzer(Power BI desktop) and pasted in query text of  run a query against dataset step.

I followed below scenarios 

1) I used parse json and I tried to specify the columns in schema with syntax "required":["table[column]","table[column]"]. When I tried testing the flow I got below error 

"Message": "Required properties are missing from object: " Because my data has null values for few records. 

I also tried to change the syntax "type": ["string","null"] for each column but no luck-same error. 

2) I removed columns from "required":[ ] and created a csv file and sent an email, but in email teh column headers are Table[column1],table[column2],...........

Note: I could not use Custom select of columns while create csv table or select columns to define names in select operation  

I want only column names instead of table[column1] in the file as column header  

Pstork1
Most Valuable Professional
Most Valuable Professional

Please post this as a new question.  It's really a different question than the original post. You'll get more responses and others will be able to find the answer more easily later. If you send me a link to the post I'll try to help there. The key is to start with all the columns and then use a data select to keep only the columns you want.  Simply removing them from the schema won't keep them from being included in the download. It will simply keep them from causing an error if they aren't included.



-------------------------------------------------------------------------
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!

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.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

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  

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 (4,867)