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

6 REPLIES 6
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.
shreyans-s-jain
New Member

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.

Pstork1
Most Valuable Professional
Most Valuable Professional

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.

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (2,489)