Name: Inside Track to the Unified View-Query and Reimagined Export
Uploaded: 2026-03-10T16:31:14.771Z
Duration: 47 min 52 s
Description: Inside Track to the Unified View-Query and Reimagined Export

Transcript for "Inside Track to the Unified View-Query and Reimagined Export": Hello, everyone, and welcome to the Razor's Edge NXT Inside Track to the Unified View. This month we're going to be talking about query and exports, so let's dive right in. Before we get into the good stuff, let me quickly review some housekeeping. You will receive an email to this recorded session within forty eight hours. Now remember, there's no dial in number. The audio is broadcast through your computer speakers or your headphones. The chat is enabled for today's session so please submit your questions in the chat because we are gonna have some time for live Q and A. And remember if you do have any technical issues a lot of time a refresh of your browser will solve them. And the last thing before we get started, we do need to address that some of the product capabilities that we'll be discussing today are not available yet. And our future plans are subject to change based on normal product development cycles, your feedback and in response to unforeseen events. So please make any purchase decisions based on current available functionality. Okay so who are you going to be hanging out with today? You're going be hanging out with myself. I am Tanya Fitzgerald and I am in the product marketing department. But more importantly today we have Trit Mulligan and David Springer with us from our product management team. They're going to be leading you through today's session and so now I'm going to turn it over to Tripp. Thank you, Tanya, and welcome, everybody. So glad to see everybody on the call today. And I'm just gonna quickly walk through a couple of, key points that I wanna make and starting with just an update on the unified view and the timeline. I just wanna say the timeline has not changed. We are still working towards, the unified view in 2027. And this year, we are focused on the core business functions. And that is what you continually see through these inside tracks in our town halls. We're focused specifically on gift processing, data management, helping you manage, query and exporting your data, importing your data, online data review transactions. All of these are key things that are important to those core business workflows to help you make the move over into WebView. We've made a lot of progress. Those of you who have been following along in the gift processing area, we recently released the first phase of gift batch grid. And I say first phase because the the idea here is that initial phase was to get to parity with the existing web form batch, for those of you who are using our online giving solutions. And that, we are continuing to make progress, and we'll continue to release over the next quarter additional functionality. Just last week, we released some great feedback from you on just being able to apply a template to an existing batch. So keep the feedback coming in through the idea bank and, through your customer success team. We are listening and responding to that feedback. And just as a reminder, thank you again for attending. We have a large crowd here today. We want you to keep involved and engaged on these plans so that you can make a plan for the unified view. We know that it won't meet everyone's needs today, but it's important for you to understand when it will. And as it does, we want you to make sure that you're in there and making the move, to the web view. So with that, I'm gonna turn it over to David to talk to us about export and query and the single row result layout. David, Yeah. Thanks, off. to you. Hi, everybody. So I have been heading up our work on query in web view, and that has dovetailed into our work to modernize export as well. So you may be familiar from the blog post. It should be in the resources. There's more detail there and screenshots, but I'll be talking a little bit about it today as well. So first of all, if we're changing export, modernizing into query, why? So right now, today, in database view, export and query are similar tools that operate totally differently. So each has their own quirks and requirements. You have to get used to the idiosyncrasies of each in order to use them effectively. So what we wanted to do is remove some of that confusion for new users, remove some of that double work and learning of different but similar processes so that you can get used to query, start using query, and just choose what your end result layout should be. And we'll get into the specifics of what that means. Another benefit of bringing it into, query is that it allows more flexibility and consistency. So if an export becomes a query, it can then be used for things like query merges, inclusion in other processes like reports. So it just instead of working with two things that are slightly different but very similar, you're working with one one tool and learning it and using it for all of your export and query needs. So less duplication of process, less duplication of effort. So that's the why. So what is changing specifically? So as I said, export is being modernized into query. It is coming in as what is what we're calling the single row result layout. So let's break that down. Result layout is exactly what it sounds like. So it's the layout of your results. So when you choose single row, you're taking all of your many to one fields, putting everything related to a given record on one single row. And here, many to one fields means anything that a record can have more than one of. So for constituents, phone numbers, constituent codes, addresses, that kind of thing. The other option for a result layout is multi row. So this means if you're outputting constituents and you choose single row, you will see all of their addresses leading out as new columns as we see in the top of this screenshot here. And if you choose multi row, they're coming out as new rows as in the bottom. So this is identical to the way export handles things versus query handling things in database view. And as I mentioned, the other piece of what is changing is that we are bringing that export specific functionality to query. So you will have that duplicate row elimination in a single row result layout. You will have head of household processing in query. You'll have the field level filtering on the output tab, so choosing which addresses you want to put out in your output. And then those export specific fields, which are currently missing from query, we are gonna be bringing those over to query on the whole. So you have started seeing a few of those show up with, like, sort key, with the address field, and we'll see those popping in more based on usage. So that's the big picture, the sort of the philosophy behind it. Let me show you a demo, and then we can get into some questions. Oh, where is screen share? I got used to where it was on the other mode. Let me find it. There we go. Just a moment. Tanya, I'm not seeing the the screen share is grayed out for me. You are muted, Tanya. Let's Can we go to can we flip it? Can we go to some questions maybe? And then I'll go on the back end and see if I can. figure out why that's Okay. Okay. So I am seeing, I'm seeing some questions come in. Just kind of seeing the first one I noticed. When will sort key be added as something we can export with the query? That is available now. We added that, last week, I believe. So it is we brought it in for clarity of the use case. We brought it in as a sort name with import ID just to make it totally clear to users what that is. So you'll see it right after sort name in the list of fields. Susan, this is a great question. What about all the times I would make a constituent query but use it to feed a gift export? So I will actually skip ahead to my FAQs and see if we can head off a few of these. So, yep, that was the one. So can I still use an export with multiple queries or vice versa? So this is going to use the select from query, which we are which you can access today on the options tab of query. We are adding it as a step in the creation of new queries, as well. So when you create a new query, you'll see the option to select from a query so that if you know you need to do that, you can just choose it then. Part of that that is not in place yet but is planned is going to those sort of higher level queries. So selecting a constituent query as your selected query for a gift query. So you can do that today with export. We are adding that to query as well. Is there still going to be a queue option in NXT? We are working on scheduling scheduling queries as part of that, and then we'll be filling in the gaps and determining once we have scheduled queries what is needed to sort of join those and replace queue fully in WebView. Will there be options to use a query within a query? Yeah. We covered that. Can that's, David. One that continues to come up. is, will they have access to their existing exports? Yeah. Let me actually go back through these. That's a good prompt. So will my existing exports migrate automatically? They won't migrate automatically, but we are planning a migration tool. So it'll be like a one click. You'll go in there when you're ready to migrate them over. So you will be able to do any cleanup you would wanna do, delete exports that you don't want to come over, clean up like, change category names, that kind of thing just so that you're not seeing queries pop up that you're not expecting. Let me get to the other FAQs, and then we will start looking at the chat again. Will single row result layout queries appear in database view? No. They will not. These will be web view only. So once you migrate them over, any changes you make in WebView are not gonna carry back over to database view. Will I still be able to use database view export? Yes. So there are no plans to disable database view export or query ahead of database view as a whole. So this doesn't change that overall database view plan, but no plans to disable it, specifically. Will I still be able to use head of household as export specific fields, exports additional filtering, etcetera? So there are no commonly used export specific filters or features that are not planned for WebView query. There are 70,000 ish export fields, and many of those are not used by anyone. So we're not I've seen this a couple times. We're not planning on bringing every field over. We are prioritizing those that are used by the most people first, of course, and just kind of going down the list. So at the point of release, if there are fields that you're missing, you know, give us that feedback. Let us know which ones are still needed. Our goal is to get the vast majority of fields that anyone uses in their daily work. But as if we miss some and we find that out in feedback, we're happy to add later on. Okay. Let me jump down and start looking at I think that's it. Yeah. So let me jump down to the end. Outstanding pledge balances on split gift pledges, I can't get that in database view. So we know there are gaps in export fields that people would like to see. You know, it would be great to have x field and export. That's not planned. That's not scoped with this work right now. I think that's a great feedback. I would suggest adding any of those wish list items to the Idea Bank. Primary addressee and salutation are planned. Yes. Segmentation functionality coming into mail, we know that is a gap. That is not a piece of this initial export work currently, but we do continue hearing that feedback, and we're working on a plan for it. Phone import ID. Yeah. So import IDs, I know there's, like, a there's a lot of those export that don't exist in query. So that is on the short list for, like, those fields that we know people need most urgently. I'm happy to just keep going through. Tanya, have you seen any. others? I I so there's one here. Will there be the ability to change header fields? Have we discussed that? Yeah. So I wanted to show that in the demo. I promise. It's it's beautiful. I will put a screenshot in the resources. But, basically, when you add your filters, we are making that a first class field when you are choosing your filter criteria for a given field so that you don't have to right click and go in after the fact to change the header. You can change it when you're selecting your field. Okay. What about if you use single row with fields with multiple instances automatically be included as multiple columns? Can you repeat that? Yep. If you if you use single row, will fields with multiple instances automatically be included as multiple columns? Yes. Yeah. So like with database view export, you will choose how many instances of that field you want to bring in up to 99 as is the current limit. Okay. For query, will the ability to query and isolate proposals be improved or strengthened? So if it is improved and strengthened in export, that will be part of this effort. If it is if you're looking for further expansion on that, that's not planned as part of this. When will we be able to query on attachments in WebView, not just media on database view? Yeah. We there are a handful of WebView fields. I think I saw participant options come up in the chat as well that we know users need in WebView query and also WebView export. So that is one of those short list of fields. The goal right now is to focus on getting export into WebView, then we'll be expanding to, WebView fields, scheduling of queries, and kind of expanding on improving query from there. Okay. This question is about newly announced web view only fields inquiry. I know we talked about fields, but is there a guide for how the address processing fields work? He says, because I'm getting a lot of blank output when I try to use them for records that definitely have active primary addresses. I would say that sounds like a bug. It should be working like database view address processing. So if you are encountering unexpected behavior, please report it to support. Is there a plan to make participant options available in query? We use event custom fields a lot, but it sounds like they're being retired. Yeah. So participant options, that's one of those web view fields. And because we know the cusp participant custom fields are in use, we're not planning on removing those from export or query at this time. So this one's about mailing list. On web based version of query, are the plans to update it where it can create mailing list? Sounds like they have not been able to create a mailing list with it yet. So I think the heart of that issue is coming from the multi row versus single row piece. So with single row, assuming you're using this for you're using kind of an Excel file into a mail merge, single row query should handle that for you because you will no longer have 25 rows for a given constituent. You'll have that constituent with a bunch of columns for their, you know, mailing addresses or gifts or whatever you're including as your merge fields. Okay. This is this sounds like an easy question, but it's out there, so I wanna address it. Can you make query list dynamic? Query lists. Oh, yeah. Yeah. Yeah. So that is with our recent query list work or list enhancements work to better meet the needs of query lists, we did consider that. We know that is something that people would like to see. The it is not planned right now. I would not say it's off the table. I would say, please do go to the idea bank. I'm sure there's an idea for it, and continue to give us that feedback. I do see one that I've seen a couple times that I wanna go ahead and address. I use various queries with various exports throughout the month, and I want to know if I will need to recreate those outputs each time. You will not. So that's what that select from query, which I will go back to. That's what that handles. So you would set your criteria oh, that was it. You would set your criteria in query a. When you go in to create your export piece of it, you would select query a. And then you could come back into your options tab, change the query you're selecting from to run it with a different group of records. So you can make it a one to. one piece. You can still use it, kind of interconnecting those queries, as you do today. Will there be a limit to how many rows or columns we can see? Yeah. So the limit will be based on browsers so that we don't crash your browsers. That's that's unfortunately something we can't get around. So you'll still need to just based on the amount of data, you will need to export those larger datasets. Alright. How about scheduling queries? When scheduling queries, will they have the option to be emailed to specific team members? Yeah. So we're planning on using the standard reports model, and that is included in that. So, yeah, I'm I'm picturing that being part of it. Okay. I see a timeline question. So I'm sure that everyone's wondering that, and I should put that in the FAQ. So we are targeting this for release in q three to to the broader, customer base. We are at we have a small API only EAP right now, that is open to a small number of partners. If you are an API user and you would like to be involved in the early API piece of it, please reach out. Actually, I will drop the sign up in the chat here, and we should add that to the resources. Because we have way more volunteers than we can possibly include for the UI EAP, but I do still need API feedback. Sounds like there's a little confusion around templates. So can you explain query export templates or export templates? I think there's an invert like, they're interpreting it differently. Basically, the question is, so we'll have query export templates rather than export templates. Yes. Yeah. I mean, if I'm understanding the question, the answer is yes. So you will still be able to have one core export that you then plug into multiple queries if you want to. You can have just a single query and export. Like, it's all one unit, or you can interconnect them and plug that, you know, that single row query into another query. Will address processing be available in single row queries? Yes. Yeah. So it it is available in multi row query now, so we get it for free in single row query. So anything in multi row query today anything in query today will be in single row, and, we are also adding more, extra fields. Think you might have covered this, but this is about detailed exports. They have a lot already developed and built. Are they going to have to rebuild all of those over again? No. So we we will have a migration tool that you'll be able to click to bring your exports over as queries. K. Please explain how and if the front of the house processing or head of household processing and database view will be different or the exact same as in, web view. Want me to repeat that? I'd watch that one. Please explain and if head of household processing and database view will be different or the exact same. So the plan is to have head of household on the options tab of the query. So you will still have it. It will still operate on a sort of top level query level. You will just change it on the options tab if you need to. Okay. Can you export or view a sample to review before running like you can now? Yes. Yeah. So you'll click just as with query today, you'll click the results tab. It will generate results, and you can decide if you want to export from there. Okay. Exporting oh, you want you got one? Yeah. I was just gonna say Heather suggested repeating the migration tool, and I think that's a good idea. So, Go for it. I will actually pull it up here. We are planning migration of existing exports. Our goal is that you do not have to rebuild any exports because we know people have ginormous exports that you don't wanna rebuild. So we are planning a migration tool to bring those over, and that will be on your time. So you'll you'll click the button to bring them over. You'll see it pop up in your query list and be able to work them from there. This is what is interesting. Will it will it ever be possible to search for constituents using a PO Box as an address? That one got some votes, so I think. that's. So you should be able to you know, like any other field, you would be able to do, contains the phrase PO box, I would think. I haven't tested that specifically. What I would say is add that to the idea bank if it is if that's not working in some way that it seems like it should. Or if it feels more like a bug, feel free to reach out to support, and we can we can make the call. Okay. This one's about speed. How fast will export be? Will it run faster than database view or the same same speed? Do you know if we're expect faster. And like Query, it will have the ability to run it in the background so that you won't have to sit and wait for it in in any case. Will we be able to query and export on prospect insights? That's that is a great point. I think that's that falls into that web view fields category where we know people will need to. It's not planned as part of the initial release of single row result layout. Okay. This one's on gift code. When will gift code be added to InCite so we can report on that field? To oh, to to the insights. I've not been close to our reporting and insights work. I'm not I'm not sure. I don't know the answer for that one. We stumped David. Yeah. You can ask me any kinds of stuff. I don't know. Just stick to query. Can query be added to constituent search functionality with specific outputs like database view? Yeah. That's that is not planned right now. I think that that would require some changes to sort of the core way constituent search works. And we are reevaluating that. We have work in the backlog to evaluate constituent search, but that is not planned as part of it right now. Okay. Exporting from query gives us the option to export to a CSV file, open it in Excel, and pivot the data. Will this availability be lost with the upcoming changes? Shouldn't be. If you're exporting to CSV, that will still be supported. Exporting to XLSX will still be just as with WebView query today. The the further formats are not planned right now. I'll I'll say that outright. Access, you know, the any of the MDB, any of those formats because they're just not used in nearly the numbers that the spreadsheet formats are. Got it. Will you be able to specify criteria for one to many fields for each column in the single row version like you can in export? Yes. Yeah. So when you select it, when you select the field or the node, you'll get a pop up where you kind of walk through. The experience will be a little closer to summary fields in query today, so it's gonna have that same design and interface. But, yes, you'll be able to specify additional filters for each of those query field groups. Okay. Can query be added to did I just ask you that one? Well, I think I just asked you that one. I use many of the build reports to create queries then I use for my exports. Will this be an option in web view? The build it reports is what they refer to. I'm thinking maybe they're talking about standard reports with an output query. Output queries are available in standard reports today. We will need to handle that's actually a great point. Let me take note of that because we will need to handle that output query into single row. I'll have to circle back on that. We'll communicate that a little closer to release. And while we have this migration tool up there, there are questions if we'll be charging for that. So can you address that? Charging for which? This this migration tool that they would they. would be using. No. No. That that that is gonna be core part of it. We know that that makes a big difference in making it usable if you don't have to spend six hours rebuilding an export. Okay. Is exporting from query going to be a choice in a role? Not everyone should be able to do it. Correct? Yeah. So in web view today, you can restrict the rights to export a query. That export permission will carry over to single row queries. We will also have a single a a single row permission. So if you want a user to only have access to multi row, you can do that. Only to single row, you can do that as well. Okay. Will we be able to use web queries as opposed to having to use a static query to create a list for emails. That is not planned as part of the export work. I know that there is that users wanna see that email to query connection. That's not gonna be part of this export work, but I will pass that on to my colleague who runs that side of things. Okay. Can a query be added to constituent search functionality with a specific output? No. No. I well, that's we, we database view. that's not planned right now, but we do have a reevaluation of constituent search planned in the backlog. Okay. This person's exports in database view are in folders. Will they be able to search those exports by folder in WebView? Mhmm. Yeah. The search will work the same way as query category search today. So with that migration, you will see those export categories come over as query categories. So that's one of the things I mentioned was some users may wanna prepare. That might include, like, renaming those categories so that they aren't using that they're not all in the same place if you don't want them all in the same place. So we will publish documentation on that so that you know exactly what to expect before clicking that. Okay. I do see one with a lot of upvotes ahead. I'd like to address. Go for it. We still have the ability to use a query as a filter with export fields. Yes. So there are some fields that let you select a query as part of the filtering process. Summary fields do this. So we are planning that as sort of a select from query within the modal. So, yes, we are accounting for that. Okay. Will this merge of export and queries impact queue? I don't know if I'm if I'm having connection issues. I did not catch that. You did not catch that. Okay. Lara repeated. I can hear you now. this merge okay. Will this merge of export and queries impact queue? No. So existing queues in database view will still work. Later on, we will be adding query scheduling capabilities to WebView. Okay. Will we be able to query on birthday, day, month, and year? Oh, this is related to the encryption changes a while ago. So that is not that is not there are no changes planned to that field right now. I would not say it's off the table. It's just not planned right now. Okay. About dashboards, this is a question about dashboards and around speed. Is there any plan to speed up dashboards that takes quite some time now? Not as part of my work. We are always looking for ways to improve performance, to improve every part of the product. So we're running you know, we're we're sort of tracking performance. And if where we see issues and opportunities to improve them, we are making those improvements. If you are seeing specifically that a specific dashboard or, you know, for your organization dashboards in general are slow, please do open a support case, and we can look into why that might be and what we can improve. This one's around API. Much like we can currently use an API to run a query, will the same be true for export? Yeah. Great question. Yes. So I mentioned this before, but we have an API EAP that we're planning on opening up fairly soon. If you are interested in being involved in that, please reach out to me. You I would guess probably most people here know my email, but it's david.springer@blackbaud.com. This one's about columns. Can we add more column selections to list outputs such as primary addressee and salutation? think I'm pretty sure there's an idea for that. I thought there was actually some work planned around that. I do not have that answer right in front of me, but I know that's a very common ask. I will follow-up with the proper person. Okay. Let's see. Will there be a spot where we can see all of our exports in one place and access them also, or is it kind of a stuck in the background kind of query? Not sure. question. This is one of those things that would have been super obvious if I'd been able to demo, but we will have a filter on the query list. So you can filter by result layout. You can see all of your single row right there. I also see a question about control reports. We are actually working on the design right now for what those will look like for exports. So, yes, we are planning those and should be readable to help with sharing queries and saving them and all of that. Let's stick with simple question. Will all my existing queries be defaulted to multi row? So that'll be a sticky setting. If you tend to use multi row more frequently, that is what it will default to. If the last one you created and saved was single row, that will be the default. Oh my goodness. I see screen sharing. Good news, everyone. Okay. Let me share my screen. And I'm happy to circle back, but I think having some visuals the demo. Let's do it. comes. You heard tales of the mythical demo. Okay. Alright. So, here, we are looking at the query list. So as you can see, this is that column I was talking about where you can see clearly multi row or single row. This is optional. You can move it around. You can include it. You can also filter by multi row or single row. So should make it easy for users who you know what you're working with. You don't remember the name. Whatever. Another piece worth talking about is the new query model. So I mentioned select from query. When you create a new query, this is where you will choose if you want that to start from another query. So if I'm using that sort of traditional export workflow that you have in database view right now, this is where I select the query I wanna use. So I would I'll just come in here, find the query I want, select it, and now that is my criteria. That's the group I'm starting from, and then I'll go from there. We also have result layout here on the create screen. We you can't flip it back and forth because the output fields work totally differently between the two types. So we wanna make sure that users are considering this and making this choice when they create a query. So you'll choose this when you create a query. You'll say okay. And then this is a pretty familiar query at this point. Right? So you've got a criteria tab. You can add additional criteria here if you want to, but like I said, we are using that select from query. So it's already restricted to however many records are in that query. When I go to the output tab, you'll see this is a little bit different. We've got icons to help you distinguish between a one to one node and a one to many node. This is what determines whether those, multi row records would be duplicated or something like that. The filtering piece, the UI filtering piece, is not in place yet, so I can't actually show you that live. But in, in the prototype, I can. So, for example, this is solicit code. When I click on that field to include a solicit code, I this is where I choose how many solicit codes I want to include. This is where I can rename that node from the outset so I can have whatever column name I want for that column. I can then on the filters, tab, I can choose whether I want to show inactive solicit codes or not. I can restrict it by solicit code if I want to. So here, I'm selecting my solicit codes that I want. I see them listed here. Okay. Okay. And I can see, you know, what I've included here down below the node. If we think about a slightly more complex field, such as a summary field, you can see this is where, Carlene asked about, the query as a filter. So this is sort of the pattern we'll be using. You can select from a query here as well, renaming the node, the soft credit, and matching gift options. And then the filter tab in this case would basically show all of the gift filters that you currently have access to in summary fields. Let me jump back to a real query with more data in it. Oh, and, actually, I'll show you one more fun brand new thing that is there for you right now, which is people have asked about resizing the query panes, and we just released this about an hour ago. So you can now resize these to see the tree better as you open up and dig down into it. If you wanna see your, you know, a full list of email addresses or whatever listed out, you can resize that. So I have a bunch of fields here. Many of these are many to one. On the options tab, this is where we see the result layout after the fact. I'm currently in sync in multi row mode, so so you have basis of comparison. So when I go to my results, we will see a bunch of duplicated records. So here, Joseph Deresta has multiple emails, multiple, gifts, so we're seeing his name many times here. If I go here and this is just an internal tool. You this is, not gonna be there for users when we release. But if this is a single row query, what I will see is instead the one row per record. So we can see here Derek Baker has one row. Joseph Deresta has one row. And as we go out here, we can see three constituency codes. We have changed the names to make them a little more readable, but they're still distinguished by number so you know which we can see three different phone numbers and phone types. And we can see the gift information that we've output. So this is a very familiar export format. Right? It's just now we're showing it all in the browser view, so you can get more than that 20 rows when previewing, or you can export for the for the whole shebang. So that is the basic demo. I'm happy to do a few more questions. I think I touched on everything I wanted to show. We do have two more good questions, then we can wrap it up because we will be doing a recap log with the majority of the questions just like we did, for Anthony's session back in January. This has been asked a few times. Will we still have the ability to use a query as a filter with export fields? Example, using a fund query. for certain funds to limit the gifts being exported within a specific export field. Yeah. So we we covered that before. That's that select from query that I showed within the summary field. So that will be there. And back to the migration tool, can they use it more than once if they need to? Yeah. I've been thinking through that because on the one hand, we obviously need to avoid duplication of data. But if there's an update to that export, if the first time through, we have to have some way to allow that. I'm still thinking through if that, by default, will be usable more than once or if it will be a contact support in case of emergencies thing. I suspect we'll be planning to allow its use more than once while also controlling for, you know, creating a bunch of duplicates. Okay. Well, we do wanna be mindful of everyone's time. We do try to keep these at forty five minutes because of that, but we did go a little bit over. But we wanna thank you for coming to today's session. Registration for next month is up. The links are in the doc. It will be on import. And there are other great resources in the documents, so please make sure that you look at those. And we'll see you next month. But, Trick, do you have anything you wanna say? I know you popped back in. Yes. Yes. Yes. I do. Just a couple quick things. One recap of all the questions will be updated in our blog post with a link to a demo. So I apologize that it wasn't there. I will make sure it gets there. Thank you for all your questions. Keep them coming. We want to make sure that we're responding to the feedback and getting the questions and answers, more importantly, that you need in order to make your plans for the move to the WebView. So continue to stay tuned. Product update briefing is coming soon in May, and there will be a lot more for us to share with you there as well. Thanks, Yep. everyone. Have a good day, guys. Thanks.