Name: Beyond the Blackbaud Raiser’s Edge NXT Product Update Briefing: Your Questions, Answered
Uploaded: 2026-05-08T16:30:51.877Z
Duration: 1 h 20 s
Description: Beyond the Blackbaud Raiser’s Edge NXT Product Update Briefing: Your Questions, Answered

Transcript for "Beyond the Blackbaud Raiser’s Edge NXT Product Update Briefing: Your Questions, Answered": Hello, everyone. Thanks for being here today. Let's jump right in. My name is Bill Connors, and I'm a thirty year Razor's Edge user. And I've been a Razor's Edge consultant for almost the same period of time. Blackbaud's asked me to prepare and moderate this Blackbaud razor's edge NXT product manager session today as a follow-up to the razor's edge product update briefing that happened earlier this week. My colleague and collaborator, and I promise you all around great person, LJ Ren, is also an independent consultant and contractor on the Razor's Edge. She is gonna be working in the background this morning, as is her preference, to work on the live questions you raised today. Last November, Blackbaud had another consulting firm do this. I'm sure this fall, they'll have someone else do it, but I think it's a great idea and generous of them to do this as the product update briefing is jam packed with information, so so they don't have time to take questions live. Some folks have expressed in the online communities that they think the questions that do get answered are filtered to the easy ones, and the hard ones are left unasked. So we independent consultants being involved in choosing the questions is meant to allay that concern, I assume. Thanks to Blackbaud for hosting this and making this available to us all and compliments to Blackbaud and to the five people and others behind the scenes that you see on the screen for the crisp, fast paced, information packed product update briefing, that you had this week and for all the exciting new things that are coming. Folks, there were 1,117 questions. Yes. That's over 1,101,100 plus questions submitted during Tuesday's product update briefing, and I've since received dozens, easily more than 50, more on social media and in the email. So here's how this is going to work. I'm going to assume you all attended at least Tuesday's product update briefing, and so you know how all this webinar software works and you know who these great people on the on the webinar with me today are. So we're gonna skip all that except to note that it is being recorded and you will get a link. We're gonna spend about forty five minutes asking the product managers the questions I've selected from all that those you've submitted, and then we have fifteen minutes allotted at the end today for your questions that you raised today. Now as you've noticed, we left the chat on so you can talk amongst yourselves as you wish. But LJ will be monitoring only the q and a window for further questions to ask today. So put your questions in the q and a part of the screen if you want us to consider them to ask today. Blackbaud will not be answering questions there. LJ will only be using that window to review them, and then she will pass on to me behind the scenes the questions that she decides that you all want to ask later in the session. And Blackbaud says they'll answer the top questions and themes in a blog post next week or shortly thereafter. Today, there are no slides. It's all about q and a. So we're calling in as our fireside, and thank you, Anthony, for providing the fire. You'll notice there in the background, this little fire is burning, very appropriately so, a little electronic fire. Thank you, Anthony. So no slides. It's just gonna be us talking and answering me asking and the rest of the team answering questions. A quick note about terminology based on certainly the way questions were submitted. The web view is the web version that we have today. The unified view is the consolidated version that we will have in the future. Today, we have the web view and the database view. In the future, the end of next year, when the database view goes away, that's what we refer to as the unified view. Razor's edge, the term razor's edge is not a reference to the database view. NXT is not a reference to the web view. We're going to use the terms database view and web view this morning. A final comment before we get started. I plan to ask some questions that some people might consider hard questions. And our intent today is not to put blackboard folks on the spot. This is not a beauty pageant or a political debate where we're trying to see how quickly and spontaneously they can answer questions. The point of today is to get good answers to our questions. And so I provided the questions to the product managers yesterday to give them a little bit of time to think about what they want to say. I do I did reserve the right to ask follow-up questions, and they will not have received those. But I'm not gonna ask a lot of follow-up questions because you wanna hear a lot a lot of things. And so if you have follow-up questions, again, put them in the q and a chat, and then LJ will send them our way. Okay? So that's the plan. Let's get started. So, Tripp, again, thanks for being here today, and thanks for doing this. So there were a lot of questions, and let's start with you. I wanna turn what I was gonna do as an introductory statement into a question for you since you're the team manager. Users asked and sent good, often great, reasonable questions. Some were extremely detailed. For example, Chris sent a question about the length of the business title and that 50 characters just isn't enough. With so many questions submitted, everyone which I read and seriously considered, again, there were just too many to ask today. Lots of us were excited, but also a lot of us are skeptical and nervous. Some people are aggravated and scared. So here's the question. How do users get their questions answered when they have so many? And you and your colleagues need to be building software, not answering questions? What resources do we have available to get all of these questions answered? That is a great question, Bill. And first of all, Bill and I have worked. together for the last thirty years. I'm a thirty year veteran of Blackbaud. So. we go way back. Way back. So thank you for hosting today, Bill. We really appreciate it. Thank you. So as far as questions, I mean, honestly, we wanna make sure that you're equipped to be able to move when you're ready to the web view. So, this year, we started, a new monthly series called the inside track to help get a little bit deeper into an area of the road map. And I mentioned that in the product update briefing this this week to say we did some in in, January, February, and March on import and gift processing, so that you can see from a road map perspective what what we're what we just released for gift what we're getting ready to release, and what's coming soon and get your questions answered. So that's one forum. Second forum, we also host town halls, and those are literally just a town hall for q and a for that particular area. In, in quarter one of this year, we did three town halls on gift processing, which was you know, we had a at capacity, at least a thousand of you attending each one of those to make sure we get your questions answered. We also follow the community. If you're posting in the community, not only us, but we have a whole team behind us across customer success, who is looking at those questions and making answers. And we're also starting to put tools in your toolkit for to help you get there. So as a, at the product update briefing this week, we released the feature map, which is a new tool for you to see what's in web view, what's in database view, and what's not currently planned to come over to help you equip your team to know when you're ready to make that transition and move over the web view. We're also exploring, a way in which to provide you, like, a a gift management workflow road map. And for each piece of the workflow, have we completed that per that area? So for example, campaigns, funds, and appeals is part of your gift management workflow. Can you now create a new fund in WebView? Yes. Can you do the campaign? Yes. Can you create an appeal? Yes. Can I thank you? Can I create thank you acknowledgments? Not quite yet. You can do it for one offs, but not multiple. So we're gonna track each of those parts of the workflow. That's a tool that's gonna come to you, very soon. Then finally, we're looking at ways in which we can actually leverage AI to help. Can we have an AI agent that can actually have all of the questions that you've asked and the answers that we've given you, available twenty four seven so that it's always on for you when you're looking to do your planning. Alright. Thanks, Trid. There has been a lot of positive feedback both you can see in the emojis coming up on the screen as well as in the feedback that I got about the feature grid. So thank you to you and the team for doing that and for the other ideas that you're gonna be expanding on. The second question is along the same lines. Even when users are excited about when capabilities are released and coming, they are confused about how to actually prepare, what they need to do on a daily tactical basis to to prepare and implement these changes. What what is Blackbaud doing or going to do to address this? For example, Michelle asked, quote, with everything in WebView now seeming to happen so fast, it's hard to keep up and keep doing everything in your job, end quote. Carol asked, it would be nice to know what enhancements are planned for what quarter. I have specific goals for my work built around the NXT deployment. For example, updating and approving our acknowledgment and recognition program. How can I establish those goals and deadlines without understanding when the updates communications are coming out? End quote. And even just this morning, like, a half hour before this time together, Christy asked and sent me the same question. So how can we take the changes in the pub and make them real in our organizations? Yeah. So, one way is that we, are working closely with our education team to build training for Unified View. And they're building a whole course catalog for a lot of the training so that you can step back and look at the full area of of of the of the capability within WebView that you're interested in learning more about. We've also equipped with a sample database. So maybe you don't wanna do some of the testing within your production environment. You can actually log into a sample database, play around with it there, get comfortable before you actually implement it in your own production environment. And then we're also creating micro learnings right now. So with some of the new what's new, what's new. I don't know if you guys have all seen that what's new is getting longer and longer each week. We're creating micro trainings, and soon we will have embedded video trainings within the product. So we're trying to do more and more in the product where you are so that you know and can see, but also provide a resource center that's available now that has lots of additional information for you. And we're gonna continue to do that. We, we, as Blackbaud are completely focused on making sure that you're successful in this process. And we recognize that this is a lot of change, and we wanna be here for you and walk through that change together. And thanks, Trud. I would also add that the blog posts, which are coming faster as well that you all and your colleagues do, especially on the marketing and comm side of your team, are really helpful. I that's my primary or at least first source of information to learn more as well. And folks, if you're not subscribed to the r e n x t blog post, which is different than the community where we all talk to each other, I'd recommend you go to the community and there's a link to it in the doc section of the webinar today and that you subscribe to the blog. I have it for instant notifications, so I get them as soon as they come out, and I love that. Thanks, Tripp. Yeah. David, let's turn to you. You've got the award for probably having the topic that got the most excitement. People are loving the fact that the interface for the constituent record is about to change. So a series of questions for you. I got a lot of questions on this one. First of all, Ellen oh, look at all the emojis coming up. Ellen and Candice asked if the red check marks are coming back. So that's not in the initial design. The hope. is that, you know, we're open to adjusting all of this with feedback. That's not in the design right now. Okay. But you're open to the idea that we want some indicator that a tab has information on it? Yeah. Like, that's that's not in the design right now, but the hope is that by having sort of the sticky tabs and and going you know, retaining your place when you go from one record to another and just that sort of, like, continuity of process that you don't need them as much in WebView. But as with. anything, we'll what we learn in EUP sorry. Okay. Early adoption. I need to minimize my, acronyms. Oh, good. Okay. The same eagle eyed Ellen noticed that the header or summary area of the constituent record in your slide and demo didn't display constituent codes or membership. Will that still be there? Yeah. So we are streamlining that as well because we're making the overview personal information tile customizable. So that. will be the place where you put your most important information, and that's and so that's kind of taking the place of the header that's been getting busier as we try to add more to it. Okay. Shani asked if the giving summary in the web view will look more like that in the database view, and especially, will it stop rounding and give us the exact amounts? A lot of us don't like the rounding. So as part of this change, we're not planning any changes to sort of how it processes. I I think if we're seeing those numbers appearing wrong, I would say report that to support. If that's a design thing, maybe I'll chat with Anthony about that offline and see if, if that's something that's in the works to change. But the general processing is not gonna change. Just the presentation to make the editing and accessing the data is going to be speeding up because you're getting right to the list of gifts initially. Okay. Katie, as when it's coming, can you be more specific as to when we can expect to see the change? Yeah. So we're looking to start early adoption potentially late q two, and then wider release in q three. And so for folks. like q two would be June and q. three would be July, August, September? Yes. Yeah. Yes. Okay. And then, you know, I mentioned this in the in the product update briefing, but, we're looking at early adoption for a small group of customers. We'll get feedback and and adjust from there. Then we'll have an opt in period where you'll see sort of an ability to opt in if you want to or you can wait, and then we'll roll into the wider release once we've seen people opting in and continued positive feedback. Okay. Thanks. To Robin and Alan asked two related but different questions here. First of all, will we still be able to move the tiles around on the tabs? Yes. And then will we be able to change the tab order? Again, that's not planned right now. If feedback is that we need to do that, we're open to adjusting that. Okay. And then what will happen if a user doesn't have rights to get to data of that type? For example, someone who can't see gifts. Yeah. So if you don't have access to specific data on the tab, as today, it just won't be on there. If you have access to nothing on the tab, the tab will not show up for you. Great. Will we be able to change the default tab? I told you told you there was a lot of excitement and interest interest in this. But will we be able to change the default tab? That is not planned right now. Again, part of the goal in making the overview tab customizable is that you can put your most important information there and that that's kind of a home base for everyone even if their most important information is not the same as other people. But you said the tabs are sticky. So does that mean that if I if I leave a record on the gifts tab and come but log back in tomorrow, that the gifts tab will be the default tab in essence? It's per session. So the intent is that you might be working on on gifts today and you're working on events tomorrow, for example. The this. was really to meet the use case of you're working through query results or list results, opening. many records in sequence, and making changes on in the same area. Okay. Another big question was one of the reasons for excitement, of course, of the record change is faster data maintenance. Will there be further options to eliminate more white space and tighten the data displayed so that us data entry folks and data focused folks can see more at once. Yeah. The we are always looking for ways to help people move faster and do their jobs more efficiently. So this is the sort of v one, our first in iteration of a tabbed view, and we'll be looking for ways to improve it further. Alright. And final question on this those later versions are, I'm not sure yet because we haven't gotten for those improvements. Okay. Okay. Thanks. This looks like your audio is a little different than your video, so sorry to cut you off there. Final question on this. For fundraisers especially, will we be able to keep the existing long tile screen if they want that? Almost certainly not. I think what is more likely is that we will look at what why why do you want to? Like, what is beneficial about the tile view and see if there's a way we can kind of meet both needs. Because if we're trying to maintain two totally separate views of a record, that makes the experience worse for everyone and may makes maintenance harder. So we'll try to sort of find the middle ground so that it's most useful for everyone. Okay. So thanks for answering all those questions, and folks, thanks for sending in all your great questions about that. So, Anthony, let's turn to you. As you can imagine, there's also lots of interest in batch. I sent you a very long question with lots of people asking for lots of more lots more specificity on the timing of the changes to batch. You know, Carrie and Roxanne about linking events and tributes, and Michelle about linking events, Katie about the batch commit control report, Diana about the drop downs and Canadian stack receipts, Rosie also asked about the receipt stack, Steven about constituent IDs, Kevin and Rosie about manual pair, etcetera. Lots of interest, specifically about timing. Can you be more specific with. us about when each of these options is gonna be coming. in just broad quarters? Yep. I can. So I broke up my response. I was I was just looking through all the questions that are in there, so I broke up my response to order them based on timing. So, the current quarter, quarter two going till June, we are working on the control report, the validation report. Those are the two top of the list. Right behind them, I would say gift code. Nobody asked about gift code in your list, but I just saw it pop into the chat. So easily the top requested things would be the reports and gift code for sure. And that's five at the end of. Tributes right now. Hi, June. As a reminder, about eight two. yeah, gift processing is our number one priority right now. It falls ahead of any other things that we're working on to. make sure that we can so it's all coming. Right. Yeah. So, yeah, right now, it's we're working on and we're working on some back end functionality to support, the advanced gift linking. So, to be able to support linking to an event, linking to a membership, linking to benefits, linking to matching gifts, we don't wanna store all of the stuff in our gift code. We want the different, teams to basically own their own, you know, their own path forward for their experience with those pieces of linking. And, eventually, we're gonna support third party in there as well. So the back end work we're doing is gonna support that. But this quarter, opportunities and tributes would be the advanced linking things that will come this quarter along with the reports, along with gift code, gift constituency. Once we do that back end work in the next quarter, now we're talking about events, memberships, benefits, matching gifts, being able to do those linkage because we'll have the back end work done. From a feedback standpoint, I saw I saw the drop downs for campaigns, funds, and appeals. We just got that work ready this week. So when someone frees up, I have a couple different buckets of work that are kinda like, hey. If you're looking for something to do, go grab these, and it's campaign funds and appeals. It's not gonna be a drop down. It's gonna be in a in a list format where you'll be able to do your search as it is today, but you'll also be able to do show all and get your full list that you'll be able to pick from. We have that experience in various areas. And that's that's what, And? then it's that is TBD. It's not gonna be any further than quarter three. We may be able to pull that into this quarter if things go well. That's work again, that I'm kind of getting ready to say. just and just for everyone's clarity again, this quarter is ending June 30. So Ending month or. Yeah. so, and the next quarter is July 1 to September 30. Right? Correct. Right. Yeah. I'll say quarter I'll say I'll say the September the one that ends in September on that one because we don't have it planned into this quarter. But if things go well, that's that's one we're gonna pull forward along. with constituent search updates. Right now, the search doesn't return, inactive records. It doesn't return spouse records. We wanna button that up, and have that work as well. As far as IDs go, in that campaign fund and appeal update work that I was just talking about, showing IDs in the search when you're not searching off ID, we have that as part of that work as well. Something I'm still working on is showing IDs, showing that constituent ID when you've selected the constituent ID constituent, showing the ID when you've selected the campaign fund and appeal because those columns are getting a little especially the campaign fund and appeal column, we're getting a little crazy with our showing all of the splits and now we're gonna show splits with all the IDs in there. I don't want it to be a mess. So we're still evaluating the how are we gonna show the IDs once it's selected. Right. So that one's still kind of in discovery a little bit. And other feedback you mentioned, the custom fields and columns, easily the number one feedback that I've gotten would be the I miss my columns for custom fields. And, Bill, you. called that one before we even shipped. So, credit to you for knowing Ari and the the customer base. That one's a little further out. I'm still doing discovery on that one. I would like to get all of the missing pieces in the batch before we circle back on things that aren't in batch yet. So that's, like I said, that's bringing all that advanced linking, bringing import in a batch, bringing global change in the batch. That's gonna include the payroll deduction batches, the automatic applications, your manual batch your manual automatic batches where you're running your generate transactions now and your EFT, that's all planned for quarter three. for quarter three. So by September 30. Correct. Okay. And that included that included the separate columns for custom fields. Correct. It does not. I'm saying I wanna get all that missing stuff that's not in there yet, and then we're. gonna see where that one slots. That that one's potentially I wouldn't put that ahead of anything else that we have because those other items are just completely missing. I don't wanna have missing stuff, before I go back and revisit the columns. it. Yes. Okay. Okay. Alright. So lots coming by June 30 and then another whole set coming somewhere in the period of July to September. Yes. Okay. Anything else you wanna say? No. I'm aiming for complete parity by the September. Complete parity with database view batch. Yes. Database. Yes. Alright. I'm gonna repeat that. Complete parity with database view batch by September 30 of this year. Yes. Correct. Okay. Can anyone else see all the emojis popping up? So we wish you well. Clearly, that's what we want as well. I, I have to check on Anthony. every day just to make sure that Alright. Alright. Well, thank you. Yep. Thanks for that, Anthony. Daisy, let's let's turn to you now. So, we're all very happy to have online review available for events and event registrations in the web view. Thank you. There have been, so since it's been released, some concerns expressed about it, how that it's integrated with the online donation form and gift review as well using shared the same shared screen, shared permissions, etcetera. Have you heard that feedback, and what are you all thinking about that feedback? That's been pretty strongly expressed in the online communities and was echoed by the emails that I got this week. We can't go. hear you, Daisy. There we go. Can you hear me now? we go. Okay. I I put it up, and. I forgot to bring it back down. Yeah. No. Well, we definitely have heard that feedback about just having better separation of of permissions or even the accessing the page. Our goal with online data review this past quarter so at the January, we wanted to get that registry in there first, because we want you to start matching and linking your constituents to the correct records, early on. And then later, we can start splitting up, If we need to put up permissions, we need to I have also heard feedback about, well, why does it accessible through the management page? Right? Like, and why and it's because it's it's part of this evolution of where we start off with online data only for deletion forms, and that's where it that's on that gift management overview page, and the needs attention link, ODR settings. I believe that page came out at the same time as ODR first came out. Oh, sorry. Online data review, came out. So it is tied to that page, but it doesn't mean that it has to live on that page forever. So I can share that, Okay. this quarter. So starting from April until June, we are currently working on moving it out of there. It'll not moving it. Giving it a true home under a new left nav item in your menu. And. then gift management, you can still access it from there. We don't wanna take away your access points to online data review. If your donation person is already working on that gift management page and they go to online data review and they go to batch and that's where they like it, they can still access it. So. we are going to move it. We are going to also move the permissions away from, I think is it under fundraising right now? Because it's not just fundraising. It's not just gift management anymore. Right? It's also constituent form, matching. It is event reg form matching, and we'll see membership also come in there, down the road. So I think we have heard a lot of it. I've heard the feedback about the shared permissions, the shared screens. Don't like where it's. at, but it's all feed I think it's all stuff we can definitely keep our backlog, keep voting on the idea bank, and we'll keep getting that feedback and and iterating because that's as somebody who was on a different team before, this is the fun part about working with Razer's at Genexx is that we can shipping things and keep working quickly as needed. It's not, you know, tied down to a a long period of time and waiting for my my release window to happen maybe once or twice a year. So that's the fun part is that we can keep getting that feedback and looking at it together. So I didn't know this. It sounds like the urgency was just to get it built for events, and now you've got some time. to refine about how where where it is, how it. works. Exactly. Because we. wanted to make sure that you came into your events. We just I think we're on the downswing of the busy event season. But you guys are gonna pick up with your event season come September. October is a big event month. So, giving you the ability to re registrations and start matching and linking the correct records was critical for a lot of our customers and what we were hearing. So that was our first goal, and now we can, keep. it, you know, you know, move online data review away from gifts because it it its future can be a lot of different things coming through it. So, Daisy, there are also some questions from Mary, Stephanie, Jessica, others about additional functionality, like adding more fields to be filled out, like named formats, add cells, default using default nets, the matching criteria. Thoughts on further improvements to the online data review? Yeah. I I love those ideas, so please do put them in the idea bank because that's where if it starts bubbling up to the top, we start noticing it too, and start planning for it. Like I said, this is the fun part for me, being on Razer's iGen XT now is that we are, more of a modern software cyclical deployment. So I've been enjoying that. So put that in the idea bank because we can look at it later. So then in the radar now, in the radar right now. open. Right now, we're working on getting those permissions out of gift management and then giving it a true data home. okay. Alright. Thanks, Daisy. And, Daniel, thanks for your patience. So a lot of users, including Ellen, asked about whether the improved import tool you discussed will replace third party tools like Importomatic, ImportTacular, SmartImport, etcetera. Can you share more details on that and, you know, to the extent that you can, what how your import or the the you are calling it your import. The new standard razor's edge import will compare and contrast to those kinds of tools. Yeah. I'm sure. So first, just to be clear, WebView import is not being built to replace partner solutions. Our partners are still going to continue to add value there, especially for organizations that need more advanced workflows and more automation outside of what we're building in WebView for import. What we're focused on is building that native import experience in WebView so that you can more easily import every day in WebView either through what's going to be the new import UI or the import API. But like I said, partners are still gonna be needed if there's more advanced capabilities that you need beyond that. In terms of comparing and contrasting a little bit, I can give, like, a high level of what our import and web view is going to include. So at a very high level, we'll have insert and update you'll be able to insert and update records using a single file, so you'll no longer have to select your import type at the start of your import process. Import fields are going to be auto mapped based on file headers. You will have exception handling as part of your import work flow. So if there are errors that come up during your import, this will call them out. You can remediate them as part of this process. Another thing that's coming is that imports are going to run asynchronously for, processing in WebView, which is great. Yeah. Yeah. No more Yes. work. stoppages to run your imports. And then, other things, you'll have insight into the status of your imports. You'll be able to see if it's queued, processing, when it's complete, and then we'll also have the duplicate management functionality. baked in as part of this process as well. Jessica asked about that. So real quickly on that. Right now, import can use its own defined criteria to see if someone looks like a duplicate, and the best they can do is kick it out as a possible exception. Will you will the new import you're working on allow duplicate matching and updating? So the duplicate management functionality, at least initially, is gonna be pretty similar to what you're used to today with database view. So. if there's a system record ID provided, we'll update the existing record. If there's an import ID or another lookup ID provided, we're going to look for a match. And if we find a match, we'll update the record there. But if there isn't a match found, that's when our fuzzy matching comes into play, which looks at a combination of name and contact details, so address, phone number, email, to find potential matches. And from there, if a match is found, we'll append that information as a child record to the constituent, but we won't update that constituent record. If no match is found with the new functionality, that's where we will then create a new record for that incoming information. Okay. As far as the part around being able to, like, manually make changes, right now, there is no manual review step to confirm or reject the fuzzy matching, but I know that's something that there's definitely a need for. So we're already looking at more ways that we can incorporate transparency and more control in the matching process. We're even, having conversations about potentially leveraging ODR in the future, so we know there's a need there. As we build out this import functionality, just right now, it's not part of the initial work that. we have planned. K. Alright. Well, thanks for your work on that. Thanks, Danielle. A reminder, folks, we're about ten minutes away from q and a for the questions you've raised today. So, again, put them in the q and a window for LJ to review and get ready for us. We're not monitoring chat for that purpose. So, Tripp, back to you. A really interesting question came in from Catherine that I hadn't thought about before, which is what is the period going to be like before the database view is turned off? The idea was it's gonna be hard, he suggested, and I would tend to agree, to be moving making sure everything is moved over from the database view to the web view while the web view is continuing to change at least at the pace that it is right now. It's gonna be hard to hit that moving target and stay on top of changes at the same time we're trying to move things over. So do you have thoughts yet as to what the 2027 might look like prior to that final cutoff of the database view? Yeah. That's a great question. And one we're thinking about a lot, to make sure that, again, we're we're enabling you to plan and prepare, effectively. So, the way that we've kind of, prioritized the roadmap, again, gift processing first. So once we get gift processing in a great place, we won't we will probably press pause there to give you the opportunity to come on over and then listen to the feedback and start making adjustments and updates at that point, and then rinse and repeat along the way. So I know that early on, we may have kinda jumped the gun a little bit and said things like, come on over. We're ready for you. Especially maybe in the gift processing area. I I will take all, all of that, to say, yeah, we weren't ready for you. Not for all of you, but for maybe some of you, if you don't, if you've heard seen that in the what's new before. But, you know, moving forward, we're gonna make it much easier for you to understand when we are ready for you. And then we're also gonna make it much easier to say, we're gonna we're gonna hold here, and we love all the feedback, but we want to enable you. Okay. Thanks. Real quick while I've got you, Trent. Patty and many others on the online communities have been concerned about the CVV requirement for back office credit card charging. I've heard there's been a change in that direction. Can you update us quickly on that? There has. This is a little bit of a whiplash. I think, a lot of folks may have been surprised that there was a requirement put in, for CVV. That was something that was a little bit out of our control underneath the platform, that we were able to negotiate and say, you know what? This is not gonna meet the needs of our razor's edge customers. And. so we're pulling that back. It's not gonna be February anymore. We're not gonna make that a required. field now moving. forward for some time. You know, eventually in the future of the way in which we modernize years for now, maybe folks won't be still writing their credit card number down on an appeal card. But we know who we have ways we have a long way to get there. So, that's the update. on CVV. Terrific. Yeah. That's a good update and can take down some anxiety of having to recreate appeal cards before your end of year. Yeah. Terrific. Terrific. I was part of that feedback on the online community. I know a lot of people were, so thank you for yes. Again, to us and back to we are listening. We are listening, and we are making changes based on that feedback. Thanks. David, final question, as part of the canned questions. Let's talk about query and export merging because I know there's both a lot of excitement and angst about that. So let me ask you some questions about that if I could. Gabe is asking if we'll be able to toggle the same query between the two data formats. Not a toggle as such, but you'll be able to save as the other format. So you will be able. to go back and forth. It'll just lead to some changes to the output tab, obviously. Okay. Like, Okay. you would need to reselect different. Okay. Alright. That that makes sense. So we can use the same base and just do a copy to get it in the other format if we want it in the other format. Diana asked where she can see a demo of it. I know you have one. So can you tell us real quick if people wanna see it or they can see it again? Yeah. The inside track has has a good demo as well as a lot of these questions answered there as well. We can share a link to that. Okay. So, folks, you can go you can just frankly Google Blackbaud Insight track webinars, and you'll find the page and you can you can see the demo. David did a good job of that. That's an inside track. David, Jill asked if the single row format will work like export does now, and we can have different columns of the same field with different filters like phone or solicitor type. So there's a column for home, a column for sale, or what have you. Yes. Yeah. That is supported, and that is also in the demo I just mentioned. Okay. And then I think the biggest question of all, and everyone I know the answer, but I want you to be public with it and have another opportunity here. People are still nervous wondering if a single row query, what used to be an export, can be used interchangeably with a variety of multi row queries or what we know now as a query. So in summary, will we still be able to have an export like query that works with multiple queries? Yes. You'll still be able to plug a query into an export. You'll still be able I say export, of course, because that's how you think of it today. You'll still be able to plug one into another. You can still easily change that to change your initial grouping, change your output fields. That entire workflow will still work. You just don't have to use that workflow if you don't Okay. Alright. Great. Thanks, David. want to. Danielle, excuse me. We do have time for another question for you. You talked briefly about global change. I think you called it bulk update, but you did it in connection with import. So Vanessa and others were asking if you're planning to merge import and what we know of this global change today, or is it gonna be two different things? And can you tell us more about what the future of global changes looks like? Yeah. So the plan is actually to have global change run through the import UI. So instead of having separate tools like we do now for importing global change, you'll make your bulk updates by uploading a file through the same experience that you use for import. While we are with the term bulk update, like, we're considering, potentially a more intuitive change to bulk update instead of global change. But in terms of functionally, the global change functionality is going to be what you're already used to as global change today. So even though it will be run through the import UI in web view, you're still gonna be able to add, update, and delete data across multiple record types using this functionality in WebView. That's not going away. Just the name might change. Okay. Great. Thank you. Alright. Now let's switch to some of the questions that were have been submitted live. And, LJ, thanks for pulling these together for us. I'm gonna read the question. I these are new to me because they are live. And then team, just whoever feels most, appropriate to respond, please just jump in and do so. So the first question comes from Jessica, and it's about dashboards. And the question is, will RE NXT dashboards expand to include other criteria? Custom fields, for example, can't be used in the fundraising dashboards. I'll take that one. So reporting in general, we are working on hopefully, you're starting to see some of those updated reportings and dashboards showing through the home page. Next week, we're actually releasing a whole new, dashboard for the campaign funds and appeals, a new view that's gonna have some really great insights. And we're looking at the dashboards, that are in Insight Designer and looking to reimagine those. We didn't get to spend a lot of time on that in the product update briefing. So we're actually gonna do an inside track on that. I don't remember which month it is, but stay tuned. I think it's maybe October, where we're gonna go deep into reporting. So you'll get a whole sphere of what we're doing around reporting in in the ecosystem of moving reports. Some of the standard reports that you've released, some that we are planning to release, and then the dashboards and eventually the the full vision of reporting. So stay tuned for that. More to come. Okay. Thank you. I have follow ups, but I wanna ask other questions. And if you're gonna do a whole inside track on that, I'll just wait for the inside track. The next question comes from Amy, and it's about consent and email. And when will we be able to provide constituents with granular email preferences? Are there really no plans to do this global unsubscribe as an ongoing problem? Now I'm gonna elaborate here because I can just read what Amy wrote. I'm assuming we know about the new constituent forms that were just released, but my understanding is they're not tied to a specific email address. So I'm the world's worst with my bill conners dot com plus a Hotmail address. I can't remember who I gave to what. Will there I may be I hopefully, I'm asking Amy's question correctly, but will we be able to do preferences per email address rather than constituent level email preferences? So, yeah, we have a lot of, additional work we plan to do around consent. Likely, it won't happen until early next year because of the focus and what's on our road map now. But we do have a full backlog of of of a lot of the requirements. And I think if this is the Amy who actually emailed me about this, thank you for doing so. And I learned something new. So, there's some new regulations coming through on soft opt ins and other things that we need to also take into account and consider. K. So that is on your radar. Absolutely. Okay. I think I mentioned this in the past. Like, today's we have solicit codes and consent. Eventually eventually, we would want to get all of our consent solicit codes into consent. We're not there yet. We're not removing solicit codes so nobody nobody panic. But eventually that's kind of the strategy and vision, that we move away from the solicit codes to fully consent. If I if I can real quick on that, Trent, a lot of this this event after November was about the conversation around consent and solicit code. And our takeaway that there was a lot coming that we needed to get ready for, and then it to be honest with you, it kinda felt like nothing. So has that been delayed? Is that where we stand on that consent and solicit from the November part? Yeah. We shifted that work out a bit. so that we could pull in and make sure we get all the gift processing. Again, we we. we don't wanna we wanna stop incrementally releasing across a full year of a specific capability. So that's why we shifted that workout so that we could pull in more of the gift processing work, which is why Anthony's working twenty four seven right now. But besides. that. Alright. Thanks. Tracy, I think you are the person who addressed events, so perhaps this question is for you. Sue Ann asks, would love to know if being able to create a multifaceted, Not multi event like a reunion weekend is in the queue to create. And if you're not the right person, then someone else can. jump in. I can answer that. It is a really good question, and it is something that I think is super cool to have, but it's not at the top of our backlog as we're focusing on all the great things Troy has been talking about. So, but I've seen the idea in the idea bank. So it's something to keep building up, and we'll revisit when we have. Am I cutting out? Sorry. You guys are cutting out for me a little bit. We heard the answer, Yeah. Okay. so I think we're good. Okay. a little bit. Yeah. Alright. Was it for me? So Okay. yeah. You are, but we got the point, which is it's not on the radar right away. Go to the idea bank if you want that, and you'll consider you'll continue to consider it. Right? Exactly. Yep. Good. Okay. Thanks. Not sure who this is for. Maybe you, David. It's an admin question. Will there be a change log? That would be so helpful. I assume they're talking about without having to get the third party product that exists to do that. Will there be more on that directly natively in Raizer's Edge itself? Sarah, add that. Oh, boy. Lots. of responses to that as well. is a there we we talk about that. That comes up from time to time. Right? Because it's always something that people, would like to see. There's there's a lot sort of that that would require. It is not planned in the road map right now, but it's one of those pieces that, we would definitely like to get in soon. We know it's a needed feature, but it's not directly related to the unified view work, which is why we haven't been including it in the road map pieces recently. Okay. Alright then. So I'm not sure, David or Trid, if this one is for you, but Manny well, no. Actually, if you think it says Manny, not Manny because there were lots of people who did email about this. And the question is simply, what's going on with queue? So the module queue and that name will not come forward in web view. The functionality that is in queue will. So you will be able to do scheduling and automation like you can with queue. Just the name. And I think you can also yeah. I mean, you can also put plug ins in that same bucket. Yes. Right? Exactly. Yeah. A lot of the things that are in plugins are gonna be reimagined as just part of the the solution within WebView for, like, unposting gifts, for example. That's a that's a plugin today. Deleting phone tables is another plug in. A lot of a lot of the plug ins that were created over the years were stop gaps when we didn't have a cloud solution. And the way that we shipped the product was shipping fixes for data changes. So all of those types of things, we're just gonna make part of the product moving forward. What about the plugins that are things like deleting phone numbers and some of the almost, like, global deletes that aren't global deletes. Danielle's gonna solve this. Yeah. going Danielle's gonna solve those problems. okay. Alright. Thanks, Daniel. We look forward to that. So the plugins will totally go away. Some of them, like the import packulars, import o matic, those are being built as new products by those companies. And then we already know on those gifts is already in an from Anthony's work under gifts. And then some of the data maintenance ones that we just don't have in global change, global delete will be moving to those kinds of tools. So in some because this was a popular question that we didn't get to yet. All of that in essence will be replicated just in other parts and in other ways. Is that a fair summary? is a fair summary, and we're working closely with our partners to make sure that they that the the APIs, the public APIs that they need in order to modernize their solutions are available. We spent a lot of time, in the last quarter really focusing on making sure that that we prioritize those so that they can work to build their updated modern solutions like the omatics of the world. And and because when database view is no longer with us, those plug ins will no longer be there. K. Thanks. So Vered is asking a question about accessibility. It says, when the UI fundamentally changes in a structural way, like tiles to tabs, this kind of change is much harder for users who need screen readers, have optimized their screens for low vision, etcetera. Can you confirm that you're you've tested the new UI, use AI for folks as user interface, the way the screen looks to those of us who use the software? That's what UI means. Can you confirm that that you've tested the new UI for common accessibility tools? Yeah. So accessibility is definitely top of mind with all of these changes because especially, like, keyboard navigation and accessibility of just sort of screen readers and all of that is something that has long been a problem for database view. So so we wanna make sure that it's definitely more readable, more usable for all users. So, yes, we're not at that testing stage now, but it's definitely top of mind. And just to add there, So you're just concerned? we just we're working with a a third party auditor right now, to update our. VPATs. And we just gotten the results, and we've actually prioritized that work for this quarter to update. So you might see some slight changes, and and they're subtle changes. They're like color changes or button size changes or some things in order to enhance those screen readers, shipping over the course of this quarter. They're very subtle, but they actually make a major difference from an accessibility standpoint. Okay. Terrific. Thank you both for that. David, will established exports set up in the database you migrate to over? Gwen is asking. Yes. We're building a migration tool, so you'll be able to kick it off when you're ready, get used to sort of how it's going to work, and then, click the migration to kick that off and get your exports in WebView. K. Great. Thank you. Daisy, can you tell us more about recognition? I think folks under from the question, I think folks understand the so Robin's asking this for clarity. Understand the concept, of course, of recognition. But how is that gonna affect us as users on a day to day basis? Are they queryable? Are they gonna be displayed in a constituent's record? I know you that you've had to race through all of you had to race through all your topics. But tell us a little bit more about how recognition is gonna benefit us kind of on a day to day practical basis. Yeah. Yeah. So the value of the new recognition programs that we started building out, is that it's going to give you a consistent and dedicated place in your razors edge NXT environment to track and manage your recognition or giving societies. So it's not something we so we did a lot of his research initially for this, and we found that people were tracking giving societies in a multitude of ways inside of razor's edge and outside of razor's edge. But it was something that everybody was doing at their organization. Most of our users are trying to acknowledge and recognize our donors based off of their land gifts, their giving history, their continued giving, recurring giving. So that is why recognition programs is its own hub, page, location in Razer's Identity. It doesn't have to be between constituent codes or custom fields. I've heard of actions and opportunities and memberships. I I heard them all from different places people were tracking them, and it was inconsistent, right, and not built. for that. So we started with legacy programs, because every not every, but most organizations have some type of legacy society to, kind of acknowledge and honor those people who have left, committed or fulfilled a planned gift or request. So we're working on, that's releasing right now, actually. So it's not going out. It's not out fully, but, the idea is that you we'll be able we'll be able, for example, to query to say give me a list of everyone who's a member of the founder's society. yeah. You'll be you don't even need to. You can go straight to the recognition list and see that list today. Query integration is on the road map for it. So that's also on the backlog, and it's fairly high because it's the first thing everybody is asking for. But. I really I I was actually talking about it this morning. I'm like, there is value to working within a list of records where you can quickly and easily see their constituent record, add actions, manage fundraisers, and kind of do that more naturally in your day to day while staying within Raisers at Gen XT and not having to go to a report and spit out a list. Right? Or go to a query and then spit out a list and then work with that outside of Razor's Edge and then going back. Okay. Now I've highlighted these are the ones I need to add actions to. Come back in. It's. all within one place, all within one page. You can see your list, and you can see how it keeps growing. Right? Like, you it's doing the automated it's looking for those records that qualifies for you. So you don't have to build the query every time. You don't have to build the report every time. It is set up with a, you know, a robust rules engine that we're gonna keep building, as we get to the next lifetime loyalty and annual program types. But that robust rules engine is going to be checking your database for you every day, Great. and telling. you, hey. This person qualified. And, again, you're never leaving Razer's Identity and view the record, Thanks. live within it. Alright. Yeah. Thanks, Daisy. Thank you all. We really appreciate this. Thank you all for attending. Thank you all. this was helpful. Thank. you. Thank you all for the questions. Appreciate it. Have a great day. Thanks, everyone.