Unanswered

Cant read second property of object

(0) Share

Report

Posted on by jelittle

Hi everyone,

currently building a flow that needs to grab information from an object, but ive found that JSON PARSE isnt getting information from the second property onward, is there a problem with my JSON?

getting more specific, the Parse JSON correctly validates the object, when I change "label" too an integer it fails, but it fails in conditions and when put into compose it input and outputs an empty html page.

screenshots are simplified for testing but cause the same error.

this is the JSON Schema:

{

"type": "object",

"properties": {

"ItestName": {

"type": "object",

"properties": {

"id": {

"type": "integer"

"label": {

"type": "string"

}

Categories:

Using connectors

I have the same question (0)

All responses (2)

Answers (1)

Sundeep_Malik 6,484 on at

Like (0)

Report

Re: Cant read second property of object

Hey @jelittle

Not sure this will fix your problem or not, but in schema you can write the type of label to string and integer both.

So make this change to your schema:

{
"type": "object",
"properties": {
"ItestName": {
"type": "object",
"properties": {
"id": {
"type": "integer"
},
"label": {
"type": ["string","integer"]
}
}
}
}
}

Hopefully this works 🙂

Was this reply helpful? Yes No
Verified answer

jelittle 15 on at

Like (1)

Report

Re: Cant read second property of object

Hi @Sundeep_Malik,

error turned out to be a simple blindness, I have glasses now, The error in the original schema was an that there was an extra '.' in the "label" string, so it was calling for "label" instead of ".label".

in my test example, "ItestName" should be 'testName", very unlucky on my end that I managed to miss the typo.
I would be intrigued to know why the flow was still verifying the schema properly, but wasn't able to use the data.

Thanks for the help either way!

Was this reply helpful? Yes No