Best Of
Create Event Participant WITHOUT Creating a Constituent First
We are working with CVENT to integrate the event registrants with RENXT. For Event participants that match a constituent record, the integration is working to create an event participant. But for those that don't match a current constituent record, we keep experiencing an error when trying to create an event participant without creating a constituent first. Most of the event participants do match but there will be some that don't match that we only want as a participant record.
Has anyone found a solution to make this work in the API? Any suggestions or ideas would be helpful.
We have been working with BBaud Support and they are no help!
We are working off of the API documentation here: https://developer.sky.blackbaud.com/api#api=event&operation=CreateParticipant
Also included is the Payload here:
{
"raw": {
"rsvp_status": "Attending",
"invitation_status": "Invited",
"attended": false,
"rsvp_date": {
"d": 28,
"m": 5,
"y": 2025
}
}
}
***** The error we receive is the following:
HTTP response
HTTP/1.1 400 Bad Request
cache-control: no-store, must-revalidate, no-cache
content-length: 189
content-type: application/json; charset=utf-8
[{
"message": "The contact ID is required.",
"error_name": "CreateParticipantContactIdNotSupplied",
"error_code": 1017,
"raw_message": "The contact ID is required."
}]
Re: Constituent List - exclude/include
@Dariel Dixon
I'm not sure it was intentional. Originally it seemed as though Lists was supposed to be the “better version of Query” in webview, completely redesigned from the ground up, just as webview batching was redesigned from the ground up. At a certain point BB realized that the old functions were much more robust than Lists and webview batching, and so they launched the plan to pull DB Query and Batch into webview instead - which is what they've been doing since last year. I think that is the reason that webview email links to Lists and not Query. My hope is that they add that connection down the road. But they have their hands full right now trying to meet their “complete webview functionality” by 2026 so as to deactivate DB view. So I don't imagine that other details like this will have much room in their priority list for awhile.
Re: Constituent List - exclude/include
@Karen Diener We send segmented emails by donor giving history. To send an email, you have to use a constituent lists, and to build a constituent list off a query, it has to be static. The need for the capability to create dynamic email lists that consider giving history logic seems like a given for advancement shops.
Re: Location for BBCOM 2025
@Payal Sen The conference FAQ says: “The in-person event will be hosted at the Pennsylvania Convention Center, 1101 Arch Street, Philadelphia, PA 19107. "
Re: Constituent List - exclude/include
@Karen Diener, she can't use queries because she is using the email feature in NXT. The email only allows you to create an audience from a list, not a query. @Amy Bridges can only create a list from a static query. Maybe when the Constant Contact functionality comes along this will change.
Re: Any best practices recommendations?
@Wade Barren Yes, as @Dariel Dixon said - widely debated subject.
While some donation forms allow you to have the field and make it required, it doesn't seem to be a popular item on many crowdfunding platforms.
I would love to say that we have it on all records so can use if formal add/sal is needed but we don't. Not having the title does require special attention when you have a default format for primary that uses titles.
So, we don't require it but do include it on all our alumni records as we get that info from university grad files. For a lot of crowdfunding donors, we don't have it and there are so many names that are gender-neutral - more all the time.
Re: Constituent List - exclude/include
I think you're right @Amy Bridges. Lists were not designed to have that level of logic. It does seem a bit like a misstep to limit email campaigns to lists and not allow it to use queries where that functionality already exists. It does seem intentional though. I'd suggest searching through the idea bank or creating a new idea and letting us know, as that does seem like an oversight that would be worth fixing.
Re: Any best practices recommendations?
Welcome to the community @Wade Barren. Let me tell you this is a highly contentious subject. I think it really depends on your audience. I've worked at organizations that are very formal, and some that were extremely casual. You better know your audience before making a decision. And if you decide to make it required, consider having some gender neutral options available.
Re: Allocation Management - Adjusting Date in FE-NXT webview
@Nikki Baldwin Thank you for the information. Looking forward to it being fully functional.
What are System Adjustments in Bank Reconciliations
Trying to resolve longstanding bank reconciliation issue. What are System Adjustments and how best to use them?