Condition to get blank Opportunity Likelihood

@Chris Zello
you can use the Filter action on the list of opportunity that is returned by the list opportunity action. the filter “condition” should just be empty(….) is true.

however, I don't see the field you are talking about being available, which API action/endpoint are you using

@Chris Zello
Can you screenshot a run that has the “opportunity_likelihood_name” field you talking about?

I checked the schema and this property doesn't exist

@Alex Wong @Chris Zello I just tried this out (as the button says) and if there is no likelihood value the field is not returned at all so I wonder if the empty function Alex mentioned will work if the field is not even there which is what you are looking for anyway?

@Chris Zello
in graphics of what you can do:

In the parse json, you need to make sure you have this:

"opportunity_likelihood_name": {

"type": "string"

},

"opportunity_likelihood_id": {

"type": "integer"

}

The Condition is an expression:

empty(body('Parse_JSON_of_Opportunity')?['opportunity_likelihood_name'])

@Dan Snyder
When a field is “empty” the API will not produce the property in JSON response. That's normal behavior, however, the issue is the API documentation did not document the 2 fields. I'm going to assume is an oversight when it was added to the actual API endpoint and forgot to update the documentation, I will submit a support case for them to fix that.

2nd issue is with the Power Automate connector for Get an opportunity action, which is also missing these 2 fields, so will be reported to support at the same time.

@Chris Zello

{
"type": "object",
"properties": {
"id": {
"type": "string"
},
"ask_amount": {
"type": "object",
"properties": {
"value": {
"type": "number"
}
}
},
"ask_date": {
"type": "string"
},
"campaign_id": {
"type": "string"
},
"constituent_id": {
"type": "string"
},
"date_added": {
"type": "string"
},
"date_modified": {
"type": "string"
},
"deadline": {
"type": "string"
},
"expected_amount": {
"type": "object",
"properties": {
"value": {
"type": "number"
}
}
},
"expected_date": {
"type": "string"
},
"fund_id": {
"type": "string"
},
"funded_amount": {
"type": "object",
"properties": {
"value": {
"type": "number"
}
}
},
"funded_date": {
"type": "string"
},
"fundraisers": {
"type": "array",
"items": {
"type": "object",
"properties": {
"constituent_id": {
"type": "string"
},
"credit_amount": {
"type": "object",
"properties": {
"value": {
"type": "number"
}
}
}
}
}
},
"inactive": {
"type": "boolean"
},
"linked_gifts": {
"type": "array",
"items": {
"type": "string"
}
},
"name": {
"type": "string"
},
"purpose": {
"type": "string"
},
"opportunity_likelihood_name": {
"type": "string"
},
"opportunity_likelihood_id": {
"type": "integer"
}
}
}

@Chris Zello In case you ever run into a similar scenario, there is another way to get the scheme for the Parse JSON action.

1. Build the flow up to the Send an HTTP action.
2. Save and run the flow.
3. Copy the Body of the Output from the Send an HTTP action.

• Then Edit the flow and add the Parse JSON action.
• Click on the Generate from sample button on the Parse JSON action and paste the copied output into the new window.
  

The generated schema will include all fields in the output. It is possible the generated schema can be wrong (i.e. a data type may be mis-identified, fields could incorrectly be included as required, etc.) but it usually pretty accurate and a good starting point if you don't have other documentation available.

@Alex Wong I totally agree! And thank you for calling out that specific examples. I find it is useful as a good starter, especially in instances where there is not good documentation, but you definitely need to understand the schema being provided in the JSON in case other errors occur.