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

Parse Json

I'm trying to parse json and am getting an error.

 

My current schema is:

 

 

{
  "type": "object",
  "properties": {
    "diagnostic:topic": {
      "type": "object",
      "properties": {
        "nextBuffer": {
          "type": "object",
          "properties": {
            "url": {
              "type": "string"
            },
            "moreData": {
              "type": "string"
            }
          }
        },
        "message": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "header": {
                "type": "object",
                "properties": {
                  "messageId": {
                    "type": "string"
                  },
                  "masterMsgId": {
                    "type": "string"
                  },
                  "equipment": {
                    "type": "object",
                    "properties": {
                      "serialNumber": {
                        "type": "string"
                      },
                      "make": {
                        "type": "string"
                      },
                      "model": {
                        "type": "string"
                      },
                      "nickname": {
                        "type": "string"
                      }
                    }
                  },
                  "moduleCode": {
                    "type": "string"
                  },
                  "moduleTime": {
                    "type": "string"
                  },
                  "receivedTime": {
                    "type": "string"
                  }
                }
              },
              "numberOfDiagnostics": {
                "type": "string"
              },
              "diagnosticBlock": {
                "type": "object",
                "properties": {
                  "diagnostic": {
                    "type": "object",
                    "properties": {
                      "level": {
                        "type": "string"
                      },
                      "mid": {
                        "type": "string"
                      },
                      "spn": {
                        "type": "string"
                      },
                      "fmi": {
                        "type": "string"
                      },
                      "occurances": {
                        "type": "string"
                      },
                      "timestamp": {
                        "type": "string"
                      }
                    }
                  }
                }
              }
            },
            "required": [
              "header",
              "numberOfDiagnostics",
              "diagnosticBlock"
            ]
          }
        },
        "@xmlns:diagnostic": {
          "type": "string"
        },
        "@xmlns:feed": {
          "type": "string"
        },
        "@xmlns:xsi": {
          "type": "string"
        },
        "@xsi:schemaLocation": {
          "type": "string"
        }
      }
    }
  }
}

 

The error I'm getting is :

 

[
  {
    "message": "Invalid type. Expected Object but got Array.",
    "lineNumber": 0,
    "linePosition": 0,
    "path": "diagnostic:topic.message[318].diagnosticBlock.diagnostic",
    "schemaId": "#/properties/diagnostic:topic/properties/message/items/properties/diagnosticBlock/properties/diagnostic",
    "errorType": "type",
    "childErrors": []
  },
  {
    "message": "Invalid type. Expected Object but got Array.",
    "lineNumber": 0,
    "linePosition": 0,
    "path": "diagnostic:topic.message[319].diagnosticBlock.diagnostic",
    "schemaId": "#/properties/diagnostic:topic/properties/message/items/properties/diagnosticBlock/properties/diagnostic",
    "errorType": "type",
    "childErrors": []
  },
  {
    "message": "Invalid type. Expected Object but got Array.",
    "lineNumber": 0,
    "linePosition": 0,
    "path": "diagnostic:topic.message[321].diagnosticBlock.diagnostic",
    "schemaId": "#/properties/diagnostic:topic/properties/message/items/properties/diagnosticBlock/properties/diagnostic",
    "errorType": "type",
    "childErrors": []
  },
  {
    "message": "Invalid type. Expected Object but got Array.",
    "lineNumber": 0,
    "linePosition": 0,
    "path": "diagnostic:topic.message[333].diagnosticBlock.diagnostic",
    "schemaId": "#/properties/diagnostic:topic/properties/message/items/properties/diagnosticBlock/properties/diagnostic",
    "errorType": "type",
    "childErrors": []
  }
]

 

The data content is:

 

{
	"diagnostic:topic": {
		"@xmlns:diagnostic": "http://www.xxxxx.com/feed/v4/Diagnostic",
		"@xmlns:feed": "http://www.xxxxx.com/feed/v4/CommonFeed",
		"@xmlns:xsi": "http://www.w3.org/2001/XMLSchema-instance",
		"@xsi:schemaLocation": "http://www.xxxxx.com/feed/v4/Diagnostic http://www.xxxxx.com/feed/v4/Diagnostic/Diagnostic.xsd",
		"nextBuffer": {
			"url": "https://www.xxxxx.com/APIService/CATDataTopics/v4/feed/CLEAR/Diagnostic/196510356",
			"moreData": "false"
		},
		"message": [
			{
				"header": {
					"messageId": "195329530",
					"masterMsgId": "195329530",
					"equipment": {
						"serialNumber": "WTS0xxx",
						"make": "CAT",
						"model": "637K",
						"nickname": "2143"
					},
					"moduleCode": "1377F052TR",
					"moduleTime": "2020-03-17 19:45:10",
					"receivedTime": "2020-03-17 19:45:48"
				},
				"numberOfDiagnostics": "1",
				"diagnosticBlock": {
					"diagnostic": {
						"level": "1",
						"mid": "-1",
						"spn": "521761",
						"fmi": "31",
						"occurances": "127",
						"timestamp": "2020-03-17 19:45:10"
					}
				}
			},
			{
				"header": {
					"messageId": "3854675206",
					"masterMsgId": "1086743735",
					"equipment": {
						"serialNumber": "WTC00130",
						"make": "CAT",
						"model": "627K"
					},
					"moduleCode": "DQCAT0138523Q1",
					"moduleTime": "2020-03-30 19:10:50",
					"receivedTime": "2020-03-30 19:56:44"
				},
				"numberOfDiagnostics": "1",
				"diagnosticBlock": {
					"diagnostic": {
						"level": "1",
						"mid": "36",
						"spn": "3385",
						"fmi": "21",
						"occurances": "1",
						"timestamp": "2020-03-30 19:10:50"
					}
				}
			},
			{
				"header": {
					"messageId": "3854860249",
					"masterMsgId": "1086789397",
					"equipment": {
						"serialNumber": "WTB00126",
						"make": "CAT",
						"model": "623K",
						"nickname": "2139"
					},
					"moduleCode": "DQCAT0174108Q1",
					"moduleTime": "2020-03-30 12:17:33",
					"receivedTime": "2020-03-31 03:53:26"
				},
				"numberOfDiagnostics": "1",
				"diagnosticBlock": {
					"diagnostic": {
						"level": "1",
						"mid": "27",
						"spn": "672",
						"fmi": "8",
						"occurances": "44",
						"timestamp": "2020-03-30 12:17:33"
					}
				}
			},
			{
				"header": {
					"messageId": "3855343479",
					"masterMsgId": "1086919487",
					"equipment": {
						"serialNumber": "WTB00xxx",
						"make": "CAT",
						"model": "623K",
						"nickname": "2139"
					},
					"moduleCode": "DQCAT0174108Q1",
					"moduleTime": "2020-03-31 12:10:11",
					"receivedTime": "2020-04-01 03:56:05"
				},
				"numberOfDiagnostics": "2",
				"diagnosticBlock": {
					"diagnostic": [
						{
							"level": "1",
							"mid": "27",
							"spn": "3534",
							"fmi": "8",
							"occurances": "9",
							"timestamp": "2020-03-31 12:10:11"
						},
						{
							"level": "1",
							"mid": "27",
							"spn": "672",
							"fmi": "8",
							"occurances": "45",
							"timestamp": "2020-03-31 12:08:47"
						}
					]
				}
			},
			{
				"header": {
					"messageId": "3855504697",
					"masterMsgId": "1086962803",
					"equipment": {
						"serialNumber": "DLS01xxx",
						"make": "CAT",
						"model": "775F",
						"nickname": "8028"
					},
					"moduleCode": "DQCAT0048777Q1",
					"moduleTime": "2020-03-31 12:17:55",
					"receivedTime": "2020-04-01 12:41:46"
				},
				"numberOfDiagnostics": "1",
				"diagnosticBlock": {
					"diagnostic": {
						"level": "1",
						"mid": "116",
						"spn": "719",
						"fmi": "5",
						"occurances": "42",
						"timestamp": "2020-03-31 12:17:55"
					}
				}
			}
		]
	}
}

 

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
v-alzhan-msft
Community Support
Community Support

Hi @SPOFLOW ,

 

Where is the content come from?

Please take a try to streamline your content with a correct type since we couldn't format your provided content in the Parse JSON action.

 

Best regards,

Alice       

 

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

View solution in original post

I got it to work. Thank you for your help.

View solution in original post

13 REPLIES 13
ChristianAbata
Most Valuable Professional
Most Valuable Professional

hi @SPOFLOW  you have 2 options to change your schema.

{
  "type": "object",
  "properties": {
    "diagnostic:topic": {
      "type": "object",
      "properties": {

 

First delete the type

{
  "type": "object",
  "properties": {
    "diagnostic:topic": {
    
      "properties": {

  

Second change the type

 

{
  "type": "object",
  "properties": {
    "diagnostic:topic": {
     "type": "Array",
      "properties": {

 

 



Did I answer your question? Please consider to Mark
my post as a solution! to guide others :winking_face:

Proud to be a Flownaut!


If you want you can follow me:
Youtube: Christian Abata
Facebook: Power Automate LA
Power Automate examples: Power Automate examples

Ive tried both and they failed. 😐

 

First, I changed that second type to an array"

Capture55.PNG

Second, I got this:

Capture66.PNG

 

 

 

I just noticed that it won't accept Array .. but will array.  still failed. Capture77.PNG

mmmm another thing you can do is this.

 "diagnostic:topic": {
                    "type": ["object","array"],
                    "properties": {
                        "type": {
                            "type": "string"
                        }

please try.

 



Did I answer your question? Please consider to Mark
my post as a solution! to guide others :winking_face:

Proud to be a Flownaut!


If you want you can follow me:
Youtube: Christian Abata
Facebook: Power Automate LA
Power Automate examples: Power Automate examples

Still no good.

Capture88.PNG

Is there a way I can send you the actual file containing the json?

hi @SPOFLOW  you can use this link https://ecsoftpc-my.sharepoint.com/:f:/g/personal/christian_abata_cloud360_com_ec/EnlNJYgHR0BKqVwB34...



Did I answer your question? Please consider to Mark
my post as a solution! to guide others :winking_face:

Proud to be a Flownaut!


If you want you can follow me:
Youtube: Christian Abata
Facebook: Power Automate LA
Power Automate examples: Power Automate examples
v-alzhan-msft
Community Support
Community Support

Hi @SPOFLOW ,

 

Where is the content come from?

Please take a try to streamline your content with a correct type since we couldn't format your provided content in the Parse JSON action.

 

Best regards,

Alice       

 

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

JohnAageAnderse
Memorable Member
Memorable Member

Hello @SPOFLOW 

Please try and paste your data into a Request trigger "When a HTTP request is received" as the sample payload.

I tried and got a completely different schema than the one you use. See if the new schema will work for you.

Kind regards, John

I'm performing it in steps.  The first 2 have worked out fine.  The Data is coming in as XML .  I need to convert it to JSON inorder to eventually insert it into sql.

Step1

Capture98.PNG

Step 2

Capture99.PNG

Hi @SPOFLOW ,

 

What is the Body output of the HTTP action? Could you please share the content?

Does the Body output is the content that you want to parse to JSON?

 

Best regards,

Alice       

 

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Best regards,

Alice       

 

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

 

I got it to work. Thank you for your help.

@SPOFLOW 

Don't mean to necro this post (only a month!), but it would be beneficial to those that having this same issue if you explained how you solved it.

Hi @SPOFLOW can you please tell me how you fixed this? I have the exact same issue, getting "Expected Object but got Array" so changed the schema to array and got "Expected Array but got Object" from the same data. Banging my head against the wall right now!!

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