cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Parse Data Table with JSON - Error on Null Values

 I am applying a JSON script to parse a data table - eventually to convert it to a CSV as a downloadable file. 3 of the Columns/Fields in my Data Table may not contain any data (Account_Name, Delegated_To and Task_Notes), which is causing an error in the JSON flow. I have checked similar posts - all of which suggest to add the "null" options for those Columns/Fields - but that still returns an error. Here is the Parse JSON script which throws an error:

 

{
    "type""array",
    "items": {
        "type""object",
        "properties": {
            "Account_Name": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Administered_By": {
                "type""string"
            },
            "Allocated_To": {
                "type""string"
            },
            "Delegated_To": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Due_Date": {
                "type""string"
            },
            "Frequency": {
                "type""string"
            },
            "Governed_By": {
                "type""string"
            },
            "ID": {
                "type""integer"
            },
            "Managed_By": {
                "type""string"
            },
            "Reporting_Manager": {
                "type""string"
            },
            "Status": {
                "type""string"
            },
            "Task_Description": {
                "type""string"
            },
            "Task_Notes": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Warning": {
                "type""integer"
            }
        },
        "required": [
            "Account_Name",
            "Administered_By",
            "Allocated_To",
            "Delegated_To",
            "Due_Date",
            "Frequency",
            "Governed_By",
            "ID",
            "Managed_By",
            "Reporting_Manager",
            "Status",
            "Task_Description",
            "Task_Notes",
            "Warning"
        ]
    }
}
 
Here is the JSON script - with the "error elements" removed - this works because I have removed the 3 Columns from the output:
 
{
    "type""array",
    "items": {
        "type""object",
        "properties": {
            "Account_Name": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Administered_By": {
                "type""string"
            },
            "Allocated_To": {
                "type""string"
            },
            "Delegated_To": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Due_Date": {
                "type""string"
            },
            "Frequency": {
                "type""string"
            },
            "Governed_By": {
                "type""string"
            },
            "ID": {
                "type""integer"
            },
            "Managed_By": {
                "type""string"
            },
            "Reporting_Manager": {
                "type""string"
            },
            "Status": {
                "type""string"
            },
            "Task_Description": {
                "type""string"
            },
            "Task_Notes": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Warning": {
                "type""integer"
            }
        },
        "required": [
            "Administered_By",
            "Allocated_To",
            "Due_Date",
            "Frequency",
            "Governed_By",
            "ID",
            "Managed_By",
            "Reporting_Manager",
            "Status",
            "Task_Description",
            "Warning"
        ]
    }
}
 
Do I have the correct syntax for null values to be collated from the Data Table in the first version of the JSON script? I really can't see what I might have done wrong. The error message is of no use, since it is more to do with the fact that the JSON failed- but not what failed in the JSON!
 
Thanks!
13 REPLIES 13
abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Could you post a screenshot of your error?

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

Hi - thanks for looking - very much appreciated!

 

The Power Automate error message states that the schema validation failed. In the errors for the Output I see the following against every row of data where there are no Values for the Fields highlighted:

 

    "message""Required properties are missing from object: Account_Name, Delegated_To, Task_Notes.",
    "lineNumber"0,
    "linePosition"0,
    "path""[0]",
    "value": [
      "Account_Name",
      "Delegated_To",
      "Task_Notes"
    ],
    "schemaId""#/items",
    "errorType""required",
    "childErrors"
 
This seems to indicate to me that the "type" element I have entered for the 3 Fields - where I have entered "string", "null" - is probably being ignored, somehow. Or that the element showing "required" needs to be amended in some way because those 3 Fields have no Values to pass?
 
Thanks!
abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Thanks for your reply.  So generally when we generate a JSON schema it generates with the data what you have. Then later when we do the testing the data might have some inconsistencies such as some may be null but when we originally generate the schema that data may be present. Looks like some of fields here is missing. If this is passed the JSON schema action step that means your error is getting from your next step which the other system is expecting those values. Looks to me its a data issue. Where you getting this error? In Parse JSON Step?

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

Yes the error is being shown in the Power Flow Parse JSON Step. The Flow is being called by a PowerApp button, which contains the same JSON parameter list:

 

JSON(
ShowColumns(
SQLDATATABLENAME),
"Account_Name",
"Administered_By",
"Allocated_To",
"Delegated_To",
"Due_Date",
"Frequency",
"Governed_By",
"ID",
"Managed_By",
"Reporting_Manager",
"Status",
"Task_Description",
"Task_Notes",
"Warning"
),
JSONFormat.IndentFour
)
);

 

I still think the fact that there are no Values for the 3 error Fields within the originating Data Table is the issue.

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

If the error is in Parse JSON step add the null option in all the values. Let me know how it goes.

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

OK - all values within the JSON script contain the "null" value option - the output error remains the same - specific to the 3 Fields with null Values:

 

  {
    "message""Required properties are missing from object: Account_Name, Delegated_To, Task_Notes.",
    "lineNumber"0,
    "linePosition"0,
    "path""[0]",
    "value": [
      "Account_Name",
      "Delegated_To",
      "Task_Notes"
    ],
    "schemaId""#/items",
    "errorType""required",
    "childErrors": []
  },
Anonymous
Not applicable

I think it might be because the JSON in the PowerApp may not be including items from the Data Table where there are no Values - and is therefore not passing any data for those Fields - and is therefore not passing those Fields(?)

 

Perhaps there is something I can do in this section within the PowerApp JSON to enforce the inclusion of null data values for the 3 Fields where the error appears to be?

 

JSON(
ShowColumns(
SQLDATASOURCETABLE,
"Account_Name",
"Administered_By",
"Allocated_To",
"Delegated_To",
"Due_Date",
"Frequency",
"Governed_By",
"ID",
"Managed_By",
"Reporting_Manager",
"Status",
"Task_Description",
"Task_Notes",
"Warning"
),
JSONFormat.IndentFour

 

I am thinking perhaps to add some sort of WHERE clause to ensure the Field is included, even if there are no Values in the Row data?

abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

Thanks for your reply. Are the below properties defined under the required?

 

Account_Name, Delegated_To, Task_Note

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
Anonymous
Not applicable

In the JSON in my Flow, the "properties" for each Field are complete. These precede the "required" elements, which do not contain any properties. For clarity -  the latest version of the full script is as follows:

 

{
    "type""array",
    "items": {
        "type""object",
        "properties": {
            "Account_Name": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Administered_By": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Allocated_To": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Delegated_To": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Due_Date": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Frequency": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Governed_By": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "ID": {
                "type": [
                    "integer",
                    "null"
                ]
            },
            "Managed_By": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Reporting_Manager": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Status": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Task_Description": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Task_Notes": {
                "type": [
                    "string",
                    "null"
                ]
            },
            "Warning": {
                "type": [
                    "integer",
                    "null"
                ]
            }
        },
        "required": [
            "Administered_By",
            "Allocated_To",
            "Due_Date",
            "Frequency",
            "Governed_By",
            "ID",
            "Managed_By",
            "Reporting_Manager",
            "Status",
            "Task_Description",
            "Warning"
        ]
    }
}
abm
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous 

 

You could temporarily remove all the required parameter 

 

 "required": [
            "Administered_By",
            "Allocated_To",
            "Due_Date",
            "Frequency",
            "Governed_By",
            "ID",
            "Managed_By",
            "Reporting_Manager",
            "Status",
            "Task_Description",
            "Warning"
        ]
 
Also add all the properties can accept string or null. That might works.

 

Thanks 



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

@Anonymous in the action after the Parse JSON set the Configure run after checkboxes to checked for if the Parse JSON action has succeeded or has failed.

 

Rob
Los Gallardos
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.

Anonymous
Not applicable

I tried this - it made no difference to the output - which still has the 3 x null Value Fields missing.

Anonymous
Not applicable

It does not fail. But it also does not include Columns for the 3 Fields which have null Values across all Rows.

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 (485)