Power Platform Community Forum Thread Details

I have a Power Apps sending data to Power Apps...this is the "body" from Monitor...

I'm sending this to Power Automate...where SelectedCollection is the collection and I'm only sending the first record.
FlightOpsComplianceTriggerApproval.Run(JSON(First(SelectedCollection)));

When I look at this in Power Automate I see...

{

"ParseJSON_Content": "{\"AcceptJetRide\":\"Y\",\"Company\":\"CONSULTANT\",\"Email\":\"jamesastorer@comcast.net\",\"GovBoard\":\"N\",\"GovOfficial\":\"N\",\"GovOwned\":\"N\",\"ID\":302,\"Nationality\":\"US\",\"PaxID\":\"118\",\"PaxName\":\"Storer, James\",\"Routing\":\"RDU-KGGG-RDU\",\"Start\":\"2020-10-13\",\"TripId\":\"38\",\"TripPurpose\":null}"

}

When I Parse this using the Action Item Parse Json I paste in the json above (how Power Automate sees it) and it says invalid JSON, so I paste in how Power Apps sends it using the body example and it accepts it if I add a leading and trailing {} but the output is a string. I'm not sure if having a value of null is throwing this off.

I've been playing with this for hours now and it's infuriating... I have validated the schema in JSON Lint so I know it's valid.

It just doesn't like the JSON.

When I paste the string that Power Automate sees in the trigger the extra \ and " throw it off.

Any tips/tricks to better solve this would be appreciated.

My current schema is ...

{

"type": "object",

"properties": {

"body": {

"type": "object",

"properties": {

"ParseJSON_Content": {

"type": "object",

"properties": {

"AcceptJetRide": {

"type": "string"

"Company": {

"type": "string"

"Email": {

"type": "string"

"GovBoard": {

"type": "string"

"GovOfficial": {

"type": "string"

"GovOwned": {

"type": "string"

"ID": {

"type": "integer"

"Nationality": {

"type": "string"

"PaxID": {

"type": "integer"

"PaxName": {

"type": "string"

"Routing": {

"type": "string"

"Start": {

"type": "string"

"TripId": {

"type": "integer"

"TripPurpose": {

"type": "string"

}

Categories:

General topics

@sasrsc

Hey Mate,

You JSON does not complain, although I had to use Parse JSON twice.

The First schema was generated using

{
 "ParseJSON_Content": "{\"AcceptJetRide\":\"Y\",\"Company\":\"CONSULTANT\",\"Email\":\"jamesastorer@comcast.net\",\"GovBoard\":\"N\",\"GovOfficial\":\"N\",\"GovOwned\":\"N\",\"ID\":302,\"Nationality\":\"US\",\"PaxID\":\"118\",\"PaxName\":\"Storer, James\",\"Routing\":\"RDU-KGGG-RDU\",\"Start\":\"2020-10-13\",\"TripId\":\"38\",\"TripPurpose\":null}"
}

The Second one was created using the Output of the First Parse JSON action:

{
 "type": "object",
 "properties": {
 "AcceptJetRide": {
 "type": "string"
 },
 "Company": {
 "type": "string"
 },
 "Email": {
 "type": "string"
 },
 "GovBoard": {
 "type": "string"
 },
 "GovOfficial": {
 "type": "string"
 },
 "GovOwned": {
 "type": "string"
 },
 "ID": {
 "type": "integer"
 },
 "Nationality": {
 "type": "string"
 },
 "PaxID": {
 "type": "string"
 },
 "PaxName": {
 "type": "string"
 },
 "Routing": {
 "type": "string"
 },
 "Start": {
 "type": "string"
 },
 "TripId": {
 "type": "string"
 },
 "TripPurpose": {}
 }
}

Final Output:

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!