Power BI Accelerator workshop update for attendees: Query API values align with web view

Rebecca Sundquist

Hello, Power BI Accelerator 2024 attendees! I have an update for you.

As developers, we appreciate the rapid evolution of technology. Make sure to keep an eye out for 'What's New' notifications from Blackbaud, especially over the next 15 months.

Check out the update 9/16/2024 at: https://developer.blackbaud.com/skyapi/support/changelog/renxt

A blog post highlighted this today: Changes to Query API - Blackbaud Community

I am thrilled with the enhancement to Query API to return web view values for Gift Type, where database view values had appeared before. Previously we had this reference: Glossary of database to web view terms and translations. Now more values coming out of Query API align with what your end users are accustomed to seeing in web view.

How does this impact our workshop templates?

The Power BI Accelerator files you received as part of the workshop included bi_dimensions.xlsx, a translation table that matched Gift Type values to flags used in reporting. With new values exported from Query API, you'll need to update that table. I am attaching the update for you.

Credit where credit is due: This attachment originated in @Ellen Smith's template: Power BI Template for use with Exports - Blackbaud Community and has been updated to include new Gift Type values as they appear in web view for Blackbaud's Raiser's Edge NXT: One-Time Gift, Recurring Gift Pledge Payment, Pledge Payment, Matching gift, Matching gift payment.

bi_dimensions.xlsx

Alex Wong

@Rebecca Sundquist
Was just looking at the change log, and notice a new constituent endpoint for deleting constituent. I'm pretty sure we had this endpoint before, as I created a custom sky add-in button to delete constituent. But maybe this is due to permission and endpoint was in nxt-integration, so now it is in constituent.

I honestly hate the abrupt change of the Query API export that changes the gift type to webview terminology, As mentioned in my other post, there is much better way to do this on a production use API endpoint.

Now, I can ONLY PLEAD that BB does not sudden decide to “align” all gift type terminology and change the gift type being returned by Get a Gift and Get Gift List API endpoint, there are WAY TOO MANY automation and reporting that already align to the terminology used (Donation instead One-time Gift NOR Cash)