Parsing JSON Response error - "message": "Invalid type. Expected Integer but got Number."

[Anonymous]

Hi Team,

Trying to get client secure scores by running a flow, but hitting an issue with parsing the response.

I'm getting this on my "Parse secure scores" action.

[
{
"message": "Invalid type. Expected Integer but got Number.",
"lineNumber": 0,
"linePosition": 0,
"path": "value[0].currentScore",
"value": 76,
"schemaId": "#/properties/value/items/properties/currentScore",
"errorType": "type",
"childErrors": []
},

I used the sample payload returned from the "Return secure scores" action to generate the schema(below). Any ideas would be helpful.

Parse secure scores schema

{

"type": "object",

"properties": {

"@@odata.context": {

"type": "string"

},

"@@odata.nextLink": {

"type": "string"

},

"value": {

"type": "array",

"items": {

"type": "object",

"properties": {

"id": {

"type": "string"

},

"azureTenantId": {

"type": "string"

},

"activeUserCount": {

"type": "integer"

},

"createdDateTime": {

"type": "string"

},

"currentScore": {

"type": "integer"

},

"enabledServices": {

"type": "array",

"items": {

"type": "string"

}

},

"licensedUserCount": {

"type": "integer"

},

"maxScore": {

"type": "integer"

},

"vendorInformation": {

"type": "object",

"properties": {

"provider": {

"type": "string"

},

"providerVersion": {},

"subProvider": {},

"vendor": {

"type": "string"

}

}

},

"averageComparativeScores": {

"type": "array",

"items": {

"type": "object",

"properties": {

"basis": {

"type": "string"

},

"averageScore": {

"type": "integer"

},

"deviceScore": {

"type": "string"

},

"dataScore": {

"type": "string"

},

"identityScore": {

"type": "string"

},

"appsScore": {

"type": "string"

},

"seatSizeRangeUpperValue": {

"type": "string"

},

"categoryValue": {

"type": "string"

},

"seatSizeRangeLowerValue": {

"type": "string"

},

"infrastructureScore": {

"type": "string"

}

},

"required": [

"basis",

"averageScore",

"deviceScore",

"dataScore",

"identityScore",

"appsScore"

]

}

},

"controlScores": {

"type": "array",

"items": {

"type": "object",

"properties": {

"controlCategory": {

"type": "string"

},

"controlName": {

"type": "string"

},

"description": {

"type": "string"

},

"score": {

"type": "integer"

},

"total": {

"type": "string"

},

"count": {

"type": "string"

},

"on": {

"type": "string"

},

"expiry": {

"type": "string"

},

"adopted": {

"type": "string"

},

"Reviewed": {

"type": "string"

},

"AgentCnt": {

"type": "string"

},

"UserCnt": {

"type": "string"

},

"UserCnt3DES": {

"type": "string"

},

"AgentCnt3DES": {

"type": "string"

},

"NotScored": {

"type": "string"

}

},

"required": [

"controlCategory",

"controlName",

"description",

"score"

]

}

}

},

"required": [

"id",

"azureTenantId",

"activeUserCount",

"createdDateTime",

"currentScore",

"enabledServices",

"licensedUserCount",

"maxScore",

"vendorInformation",

"averageComparativeScores",

"controlScores"

]

}

}

}

}

[v-bacao-msft]

Hi @Anonymous ,

Please try to modify schema and check if it helps:

Best Regards,

[Anonymous]

Hi @v-bacao-msft ,

I made the suggested change.

Now I get the following.

For reference, this is the "Return secure scores" action.

[v-bacao-msft · Accepted solution]

Hi @Anonymous ,

Please try to change Number to number.

Best Regards,

[Anonymous]

@v-bacao-msft ,

That fixed it, thanks mate.

Regards,

Dan

[DejanTrajkovic]

HI, I was using pars JSON action and got error msg

: Parsing JSON Response error - "message": "Invalid type. Expected Integer but got Number."

I have used the solution that was mentioned here 

"temp_c": {                     "type": "integer"                 },

solution has been

"temp_c": {                

    "type": [  

                      "integer",

                        "number"  

                  ]        

        },

However, now even that flow is running successfully fields that are having this fix are not showing in dynamic content.  When I change back to one data type it will show so the problem is definitely with this fix but I can't find a solution.

Do you have any ideas on how this can be fixed?