nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Condition to get blank Opportunity Likelihood

Chris Zello

Using Power Automate, I'm trying to send an Outlook email notification when a Opportunity is entered with a blank Likelihood field. (While this can be a required field in database view, it is not required in web view.)

How do I set a condition to find a blank Likelihood?

I've found the field I want in the Opportunity API. Get Opportunity has the "opportunity_likelihood_name" in the Response Content. So I know it exists, but how do I get to it for my Power Automate steps?

Thank you, Chris

Find more posts tagged with

Comments

Alex Wong

@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

@Alex Wong Here is the link to the endpoint:

Alex Wong

@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

c07c46108aee2eef654bab02a207456c-huge-im

Chris Zello

Now I think I see what you're saying @Alex Wong, in that when I look under “Application/JSON” the field I want doesn't exist. When I “Try It” and enter an Opportunity ID and hit Send, the field I want shows: "opportunity_likelihood_name".

Does this mean that this field isn't accessible because it isn't in the JSON?

Chris Zello

@Alex Wong

95ff5bd205fc4fbe6401553e60afe7e0-huge-im

Alex Wong

@Chris Zello
if you see it in the output, then it is being returned, you just have to capture that field in your Parse JSON action. (I guess Blackbaud added it but forgot to update the documentation?)

Dan Snyder

@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?

Alex Wong

@Dan Snyder
the field is only available on “get an opportunity” endpoint, it is NOT available on the list opportunity endpoint. The get an opportunity endpoint also did not document this field being available. I just tried it myself and did get the field returned in the response from the endpoint. NOTE that the Power Automate connector for action of Get an opportuntity does not “expose” this field neither in dynamic content.

e0311f3a6ce8b5f053ab02564f58bc93-huge-im

@Chris Zello

For what you want to do, you don't use Filter action like I mentioned before. Filter action intakes a list of records, and then filter on the properties. However, since Get list of opportunity API endpoint does not provide this field (opportunity_likelihood_name), then you can't filter.

To do what you want to do, you will have to make the flow use the get list of opportunity, can provide query parameter for opportunity “added” in the last day or week (depending on your interval of run). THEN you have to use Apply to Each opportunity ID and call the Get an opportunity endpoint using Blackbuad add-in Send HTTP Request action, then condition on opportunity_likelihood_name is empty.

Alex Wong

@Chris Zello
in graphics of what you can do:

8484cf45e6d91ef5d6277fbd64315f42-huge-im

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

@Alex Wong Thanks for that clarification, I was actually using the Get Opportunity endpoint to test this out. We have renamed the likelihood field to Installments in database view so if you see from the screenshot below it is blank and then below is the result when I test it. Either way, I trust your solution more cause you have more API experience than me ?!

5bd647c41ea2bb9e626c0ecc17265981-huge-im

d2c74f0d1028c8e356e5d5e4b260f91d-huge-im

Alex Wong

@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

@Alex Wong Thank you. I'm getting an error with the JSON code.

I've tried adding those lines you included, placing them below what is in the Schema but before the final curly bracket, but it won't save. Thoughts?

Alex Wong

@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

@Alex Wong That did it! Thank you very much.

Ashley Moose

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

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

67ebef5bf103a23c4c0c9d142080ad50-huge-im

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.

10ebce662f60da034516eea52e5f2733-huge-im

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

@Ashley Moose @Chris Zello
Generally use of the Generate from sample is good, but it does not do well between integer and number. So if your sample JSON data has all integer, then the generator will put data type of integer which may not be what the field “can” return (i.e. ask amount should be number). Another situation is “null”.

So it is still best to understand JSON a little more as you do Power Automate and know how to look and modify the JSON schema as needed.

In the API doc, you can click on the Schema tab and use the official FULL schema. In this situation, Blackbaud just forgot to update the schema.

Ashley Moose

@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.