Prospect Status Histories from API- flow is SLOW

Carol Grant

I was excited to see that they have the Prospect Status History available in the API but I'm struggling with pulling the information. I want to pull it like an export but it's taking a long time to return anything so I wanted to see if any of you have tried.

The Prospect Status History endpoint is by ID so I started my flow using a query for the prospects I want. I am looping around the returned results from the query. Then I look to see if they have a prospect status with a condition if it's empty or not, then use GET http request.

Then I have a Parse Json after that splits the fields out and I'm appending those to an array that I was hoping to use in a Power BI report.

For 180 people, it was still going after 40 minutes, I decided to cancel it.

Any ideas on how to make this faster? I looked into possibly doing it in python but I would be learning python along the way.

Thanks,

Carol

Alex Wong

@Carol Grant
I don't think it should take a long time.

• Query API (30 seconds to 1 minute)
• Apply to each record (180)
  • get constituent prospect status (5s max)
  • condition (no time needed)
    • send http request (5s max)

So max 10s per loop, 180 will be 1800s, meaning 30 minutes max. Unless Blackbaud has performance issue.

first thing you can do to make this faster, don't do “Get constituent prospect statuus” action. In your Query API, you can criteria on Prospect Status not blank so the System Record ID returned is already those that have prospect status, thereby reducing the need to make one more call per constituent/loop. Your flow can look like this:

• init array variable for prospect status history
• execute query job, get JSON format
• do while job not complete
  • check job status
• HTTP download JSON
• Apply to each System Record ID
  • Blackbaud HTTP to get prospect status history
  • append array to a variable
• action(s) to save it to sharepoint

Carol Grant

@Alex Wong

Thanks Alex, that did make it faster by removing the check on Prospect Status. I did get it returned in 2 minutes without the loop for append array to variable so that helped!

Now I'm going to test doing assigned prospects (1,400) and see how long that will take and add the append to array and save to Sharepoint.

Jessica Kalista

@Carol Grant is this a flow you would be willing to share with the community?