Best Of
Re: Consistently getting errors when trying to consider apps
Agreed that this has been frustrating! I first encountered this situation last year - my tip is to check the field validation (in the new portal) to see what the max character or word counts are for these fields.
In my experience, some fields created in Blueprint had limits that weren't mirrored in the new portal. For example, a short text field has a limit of 255, but the field's configuration in the new portal might have been 50. Before I knew to go back to Blueprint, I would edit the character count limit in the new portal, and it didn't matter, especially in the case of a short text field, that had a limit of 255 characters (if I changed the limit to 1000 characters, it didn't override the original field limit).
To solve the issue, I created new fields, ensuring I was using the Long Text field, OR, added a note to the description advising applicants of the limit, and turned on the counting feature. When the limit as stated in the new portal is exceeded, the applicant will receive an error.
IMO, the bigger issue is this: if there is an error that prevents the application from being considered, Blackbaud needs to push the error back to the applicant so they can fix the issue before clicking submit. Part of the frustration is that the applicant receives a message saying their application has been submitted, but really - it hasn't.
Re: Mirroring RE NXT Data for Use in Power BI
I'd be interested to hear more about your journey — we've gone through a similar experience. We always understood the Power BI connector to be limited because of which endpoints it could access, and supplimented this by doing exports and queries. Originally we did this separately for each report, meaning our reports were sometimes not alligned; the easy fix was to export everything to a common folder and all reports point there.
From there we've been using Queue. The challenge here is that (as far as we've been able to find) you can only schedule it to export to the FTP drive (you can export them locally but only if you're signed in), and we haven't found a way for Power BI to access it. We copy the exported files to a local drive and now our reports are a lot more nimble.
We're exploring Power Automate as well. The query module is pretty robust but I'm not finding it very intuitive; once you get the hang of it you should be able to export any query to a drive in the cloud, and point Power BI there as a source. The bonus is that you should also be able to do some upstream transformations before the data gets to your report, which is a good practice anyway.
Alex Wong has a good template/articel about how to do this here. I found it helpful!
Re: Mirroring RE NXT Data for Use in Power BI
Update - happy to report that I've created a custom airbyte connector that properly handles oauth and all SKY API endpoints (including incremental/append sync for queries) without any proxy — setup takes about two minutes with the custom YAML file … simple copy/paste, and I'm requesting that Airbyte add the connector to their marketplace so it's freely available for one-click deploy (basically like zapier for the SkyAPI). … 'no code' for basic endpoints (constituents, actions, funds, campaigns, gifts, etc.) and 'low code' (minimal configuration for environment-specific variables such as code table, list, and query ID's).
I'll share a walkthrough and source code when I'm satisfied things are optimized and mostly friendly for forking the connector and tweaking it to individual needs
Feature Spotlight: Blackbaud Grantmaking Branch Security Module
Blackbaud Grantmaking Branch Security is a valuable tool for organizations managing complex grantmaking operations. It centralizes grant information across multiple entities while allowing discrete management and controlled access, to maintain both privacy and efficiency. This feature is especially useful for family foundations or institutions overseeing multiple programs.
Here's a summary of its benefits, how it works, and a few practical applications:
Key Benefits
· Centralized Data, Controlled Access: It keeps all grant-related information in a single database while enabling tailored access, so users only see and interact with data relevant to their branch.
· Enhanced Privacy and Efficiency: The module restricts cross-branch visibility and editing by default, reducing data exposure risk and keeping workflows clean and focused.
· Streamlined Reporting and Searching: Users only generate reports and searches based on data tied to their designated branches, improving relevance and clarity.
· Enhanced Security: Branch Security limits data exposure through branch-specific access control.
· Operational Efficiency: Staff focus only on what matters to their department or region.
· Robust Reporting: Combines local autonomy with the power to see the big picture across programs.
· User Flexibility: The module supports a range of organizational structures by tailoring access by role or responsibility.
How it works
Branch Security enables grantmakers with multiple sites or branches and separate giving programs to capture all their information in a centralized database, while preventing users from different branches from editing (or viewing, if desired) data from other branches. Each grant request and its related records—like activities and payments—get a branch code. That code controls what each user can see or do. Access is granted per branch, and users only view data from branches they’re permitted to.
There are two main data entry models:
• The Centralized Model: A central team enters all the data, but individual branches can still view the information related to their branch.
• The Decentralized Model: Each branch operates independently and enters its own data—but everything is still housed in one cohesive system.
You can't edit or view data from other branches unless you're granted permission to do so. In addition, your reports and searches only include data for the branches for which you have “view” rights.
By stamping each grant request and related record with a branch code, the system enforces permissions automatically—no risk of cross-branch mix-ups. It’s an elegant solution for structured, scalable philanthropy.
Practical Application Scenarios
- Family foundations with multiple funds: Branch Security is ideal for entities managing multiple giving programs or funds, where confidentiality and separation of responsibilities matter.
- Large organizations with distinct programs or departments: The module ensures each department can operate independently while maintaining overall organizational security. For example, the education department can manage its grants without accessing sensitive information from the healthcare department, and vice versa.
- Banks, law offices and other wealth management organizations: If your organization manages several family foundations, you can make sure your clients only have access to the information they need to see.
- Nonprofits with multiple locations: Branch Security allows each location to operate independently. For instance, a national nonprofit with regional offices can assign users to their respective regions, ensuring each office manages its grants while maintaining overall organizational coherence.
- Collaborative initiatives among multiple partners: Each organization can manage its grants independently while sharing relevant information with partners. This makes sure sensitive information is protected while facilitating collaboration. Blackbaud Grantmaking's Branch Security module offers a smart way for organizations, especially those with multiple programs, locations, or funds, to balance centralized oversight with local autonomy. It ensures privacy, control, and streamlined workflows—all while keeping everything in one unified system. If your organization oversees multiple programs, departments, or funds, this tool is designed with you in mind.
Patrick Points, Director of IT at Ignite Philanthropy effectively manages multiple grantmaking environments for its clients using Blackbaud Grantmaking’s branch functionality. Patrick explains:
“We chose Blackbaud Grantmaking because it allows us to keep our clients’ funds and grants accurately and clearly separated. When compared to the other systems we were using, Blackbaud was the obvious choice for handling multiple funds, ensuring data integrity and client satisfaction.” For more on Ignite Philanthropy’s experience with improving the client experience with Blackbaud technology, see this story link Ignite Philanthropy - Blackbaud
Whether you’re trying to keep departments focused, protect sensitive information, or streamline reporting, Branch Security gives you the structure and flexibility to do it all.
Interested in learning more? Watch this quick video and request a demo here. Already using Branch Security? We would love to hear from you! Please comment on this blog to share with our community members.
Sharing my Power Automate flow: Get multiple query results with Query connector and SharePoint list
Description - Run Blackbaud RENXT queries based on items in a SharePoint list, retrieve results, and save results as CSV files in SharePoint with error notifications if failures occur.
Use cases -
Use this flow to quickly add and remove queries or change save locations with easy updates to a SharePoint list. With a single PA flow controlled by the SharePoint list, you may have some queries going into one SharePoint folder for a Union in Power BI, while others are saved in another location for different handling. You can turn on and off which queries are executed to run a quick, manual test on a new query output. You may want a development copy of this flow executed manually and using one SharePoint list as well as a production copy running on a schedule and using a final SharePoint list.
Required connections -
- Blackbaud RENXT or FENXT Query
- SharePoint
- Office 365 Outlook (or Gmail)
Skill level - intermediate
Instructions - See the attached ReadMe.pdf
This Power Automate flow template builds on the example from @Ashley Moose ,
Sharing my Power Automate flow: Get query results using the new Query connectors! — Blackbaud Community. This flow introduces an Apply to each action to loop through a SharePoint list controlling which queries are executed and where each result file is saved.
First, create a SharePoint list of queries as described in the ReadMe.pdf. Then import the attached flow at make.powerautomate.com to loop through the SharePoint list and save results.
Downloads -
Re: Major Gift Dashboard
@Crystal Bruce might want to move this under the SKY Developer forum for RE NXT or Power BI
What you want to achieve is doable but more complex. Blackbaud has multiple reports / query that you will need to use to then put everything together. How you go about it depends on how much time you want to put into this and how much ease to re-run,
Specifically for pledge forecasting, it is a little lackluster right now with the API. There is no "give me a list of all pledges installment schedule and pledge payment against each installment schedule" API endpoint, what Blackbaud provides is PER pledge, you can get a list of all its installments, and PER pledge, you can get a list of all its payment details (payment application, write off). Query API can get you installment schedule, but won't give you the breakdown needed with payment details. In order to "truly" do what you want to do with forecast, without "workarounds" that depends on circumstances, you will need to:
- For all unpaid (not fully paid) pledges
- call the "get installments" api save it in a data warehouse or cloud storage somewhere that Power BI can pick up
- call the "get payments" api and save it in a data warehouse or cloud storage somewhere that Power BI can pick up
- then in power bi, you will be able to link up all the gift details (for pledge) to its payment and write off gift details, thereby allowing you to do proper forecasting.
Re: Major Gift Dashboard
Hi Sa'id- this can be done but it would have to be different queries that are combined into one or shown on different pages in Power BI. You want to use the Fundraiser's specific record ID or Fundraiser Name to link it all together. You would need to roll up certain columns like you can't show all their actions with all their gifts without duplicating something. You would need to do last action with a gift total. Or have them appear on separate pages.
RE does not make it easy to pull installments due. I use a Gift export that pulls over 10 installments for each pledge. Then I Unpivot the installment columns so they appear in one column and use a date formula to get the installment date to a Fiscal Year. Then write formulas for what installment balance is in what year.
I'm sure someone could demo this at a Power BI User Group meeting if you aren't a part of that yet, many users have done this.
-Carol Grant
Re: Gift Dates for NXT Online Donation Forms
Thanks for the feedback @Ange Scott I think we would use the same approach with gift date and GL date that you note here, but from what I've seen, the gift processing in NXT is as you indicate, extremely clunky and time consuming. I'm looking forward to seeing this fall's PUB's in the hope that they will have fixed it to work more like database view which is super quick and can have defaults set to be almost data entry error free.
Re: Sharing my Adaptive Card template: Add Event
Hi @Mark Palfrey - The contents of Ben's zip file is actually the JSON you want to use to create the card, it is not the actual Power Automate flow. You would put his JSON script into a Compose action and it will render the card he is displaying.
If you wanted to start creating an Adaptive Card, there are some instructions and Tutorials on this page:
-Carol
Contribution Based Membership/Recognition Programs/Giving Circles
Looking for insights into other organizations contribution based memberships/giving circles/recognition programs. Anyone have one that works smoothly that donors are happy with? What contributions are included? Is it an annual or rolling basis? And anything else of note.
Our giving circle right now is…confusing. And especially confusing to communicate. But we're mostly wondering if any orgs are satisfied/happy with these programs? Or if everyone feels the same?








