Name: Ask The Expert about Compound Queries
Uploaded: 2025-04-09T18:30:47.074Z
Duration: 58 min 44 s
Description: Ask The Expert about Compound Queries

Transcript for "Ask The Expert about Compound Queries": Hello, everyone. Welcome to today's session, the Ask the Expert for, a big topic, a a huge topic that we had a lot of questions on last week, which was, compound queries. Of course, I am Geoff Arbuckle, all around eTapestry guy as I put my, title there at the bottom. I am so happy to see people checking in from all across the, continent. And I was going to bring this up because, you know, for a lot of us here in North America, you know, I'm in the Eastern time zone here in Indianapolis. You know, we have people checking in from, the central and from the mountain and from the Pacific time zone. Seattle, I saw I saw a couple of were well represented in Saskatoon, it looks like. So I I feel like, you know, ETap Street must be big in Saskatoon, which is great. Makes me wonder if I go there, if I'm gonna have to ever pay for a lunch or, you know, or a drink at the pub. But, I also wanna call out because a couple of times and again today, we have somebody who is calling in from overseas, from The United Kingdom. So we have, we have Joanna over in Scotland where it's apparently sunny today. We've had people in these sessions come from Scotland, from England, from Wales, from Ireland. And I really wanna call that out because, Joanna, you could be eating dinner right now, but instead, you have to see my face and hear me drone on and on and on about eTapestry. I don't know I I don't know where your priorities are, but, oh, and, Louise, there you are in Wales. I don't know why you you folks aren't aren't at dinner, but I digress. Thank you for attending. It's always greatly appreciated. It's always, wonderfully, it it brings a smile to my face to see so many people saying hello, letting everybody know where they're calling in from. That is fantastic. Now, like I said, I expect to have quite a few questions over the next hour as we, spend some time here talking about, compound queries in particular. And, while I wait for some of those questions to start coming in, a couple of things I do wanna say is, one, as I had posted in the chat, about, ten, fifteen minutes ago before we kick things off, be sure to utilize the chat because one of two things. One, everybody can see the question at that point so that they can kinda know what I'm responding to or what I'm answering, just in case I don't read back the question. But, also, that gives our, our more advanced folks who might be listening in an opportunity to either answer the question or talk about something that they do, maybe provide some, tips and tricks of their own, if there are any. I so that's one of the things I definitely like whenever I do one of these webinars, whether it's the ask the expert or if it's the main topic itself. I I always like that participation because one of the great things that we can do is we can kind of treat this almost like a live discussion, board on our community where people can chime in, ask questions, find out from each other how they're using eTapestry, depending on whatever the topic is. So, please, make sure that you're using the chat so we can make sure that all of those questions can be seen and gives everybody an opportunity to kind of interact with one another. But what I want to do here is I'm gonna get into my database. So while I wait for any questions that may come in, I did wanna at least kind of show you in motion how these, you know, how do you get to do a compound query, Where are some things that you can, you know, where what are the steps that take you there? Some of the things that the the actual, like, more of the process of doing a compound query. And then based on the questions that come in, I should be able to, you know, also kind of follow along and kind of demo a little bit of what that answer would look like. One thing I definitely want you to do is this is, right here already on screen. It's probably going to, I think, actually, now with my cursor over, it will stay. Make sure that you're going to the, product update briefings that are coming in the May. The reason for that is is that there is something that I just learned that is in the works for compound queries. That was a question that came up last week about, you know, what queries can be used there, how many queries can be used within a compound query. We're doing some work around that to enhance compound queries in general. It's still in early development, so there's only going to be kind of a sneak preview of that, I believe, at the product update briefing. But this is also a great place where you can go and kind of see the things that we are working on with eTapestry. So, definitely wanna make sure I call that out. You will see this top banner that runs across the top of the screen. This is where you see any other kind of call outs that may come up like here, which are, you know, where's your North American sessions, where your you know, where and when are the European sessions that you can sign up for and listen to online and the Pacific sessions as well. But also, I usually will always have this represent you know, our webinars that I do, represented up here as well. So always good to kinda keep an eye on the banner that runs across the top. Alright. So to get into a compound query, of course, you go into queries. You can either click on one of your queries here. You can click on see all or manage queries to see them all. And when you get to here, you have to choose whether you want to create a new category or you wanna select one of the existing categories. One of the sessions that I, I have a session coming up next week where I am going to be talking about some cleanup tips. While I don't necessarily directly call it out, one thing that will probably come up in that conversation and certainly may come up in the conversation with the ask the expert that will follow-up with that on the twenty second of this month is the idea that it's always a good idea to try to keep things as tidy as possible. So one thing I do wanna call out while I'm on the screen is, unless a query is tied to maybe something else that you're working on or it may be just a loan query that you're, you know, wanting to find certain groups of people with certain attributes and you won't really have a bunch of other queries that will tie into the same concept. I mean, if you have something like that base or one of the other existing categories, but do consider building new categories to kind of help you say, okay. These are specifically my mailing queries. These are specifically my, year over year donation giving or or, queries, or this is my queries about board members or whatever. I will say that it is probably bad form to me for me to suggest that to you, because I clearly don't do that when you see 52 queries under base. But it is something that I do recommend for a lot of people, especially if they don't use eTapestry on a everyday basis because queries, reports, communications, those types of things are easy to lose if you aren't properly, categorizing them or keeping things kinda tidy in those sections. So if you do create a new category, all you have to do is name the category. When you save it, it will show up down here at the bottom here. But as you'll see here, I have a compound queries category already that I use for examples the previous time that I, did this session, last year. So I'll go in there just to kind of talk about, like, you know, here are some ways that you can build a compound query, and here are the examples that, that we can talk about. And, Jolene, I am definitely going to be talking about, what you're asking here in just a moment. So if you get into a category, you can create a new compound query by going under tasks and then selecting new compound query. It is the second query that, the second query type that's listed when you're within a category under tasks. So when you click on this, that brings you to what I was showing in the slides last week, in these various sections. You name it, you select whether or not you want it to be a favorite query so that it appears on the home tile for favorite queries, reports, and communications. You can label this to be private if, you don't want it to be messed with, or read only if we, if you want that to be, if you, you know, want that to not be able to be edited by anybody else. You can select your, results here, your data return type. And then this is where you get into, do you want it to be intersect? Do you want it to add or do you want to subtract? And then underneath it, that's where you can I normally tell people to click search by category so that you can open it up this way? Although if you search by name, if you know the name of the names of the queries that you're looking for, you can just search on that and it will find it within the category. But if you don't know which category it's in or you don't remember the name of the or if I'm sorry. If you don't remember the name of the query, then search by category that allows for you to open this up and select your queries. Now to answer Jolyn's question about, this about the compound queries, you can use any query that's inside the database. It doesn't matter if it's one of the standard queries that comes with the database, like base all constituents. It doesn't matter if it's a, if it's any query that you've created in the past. Especially if you're an admin, they will all be made available to you. The ones that may not be available to you are the ones marked as private if you're not an admin, but, a custom account query are available and compound queries are available. So conceivably, I could select as query number one my, do not mail or my, I'm sorry, my clean mailing list, which itself is a compound query. And when I click to edit the query, you can see this is a compound query where I'm subtracting all of the people marked do not mail from my all constituents. So I could use that here as the, as my query number one. And from that, I could subtract out maybe, let's see if there's a really easy, yeah, I can subtract out all of this year's donors to find the people who I can mail to who have not yet donated, this year. So you can use a compound query in these. You every query is made available to you and made, possible to be used in a, compound query and, so and you're not limited by how you intersect them. Again, the limitations in how they interact with one another, if they intersect, if they're subtracted in particular, only comes from how the data return types will interact with one another. So for example, if this year's donors was, a journal entry return type query like this last year's donors, that may not actually work in a subtraction because unless unless somebody in the clean mailing list has all of their transactions given last year, there's no transactions given from the year before, there are no transactions from this year, they can be removed at that point. If all of their transactions are represented in this journal entry return type query, they will be removed from an account return type query. But if somebody who gave last year also gave this year or also gave the year before, they're not going to be removed because not all of their entries are, found within this last year's donations j e query, this journal entry return type query. That is the number one place where people end up, having a little bit of issues with compound queries is that they have a journal entry return type query trying to subtract from an account return type query, and therefore, it's not removing the entirety of the account because the journal entry return type query is capturing is not capturing enough information to have all of their journal entries from their account to be removed to make the account removable in the query number one. The other thing that can happen is if you have last year's donations and you're trying to subtract out, let's see here. Let's say you're looking for everybody who gave this year but didn't give last year and you're trying to subtract out journal the journal entries from last year from the journal entries from this year, they don't match. So they end up having a, they end up creating a a, an unsolvable problem. The this year's journal entries versus oh, I'm sorry. This was supposed to be this year, not last year. Sorry. Sorry. Sorry. This year's journal entries list is not the same as last year's journal entry list. And when you're looking at the journal entries, they can't match, so they won't be able to be subtracted. Now if this was if last year's donations was an account return type query, now we've got something else that we can work with because that's going to remove the accounts that might have shown up within the journal entry. So subtracting accounts from journal entries, perfect. Every time will work. But subtracting a specific set of journal entries from a different specific set of journal entries where there are no matching journal entries to be able to remove, that's when a compound query will, end up not provide either not subtracting or not intersecting. Adding adding is not a problem. They can be added together. No problem there. Now Wilma asked if we can get the recording from last week. We sure can. Let me go over to the, let's see here, my eTapestry resources. If you come to this link, I'm gonna put it in the chat, This will have a bunch of on demand versions of past webinars or, a couple of these may actually be shortened, just recordings that I made. I think all of them are past webinars, though. But you can come here in this very first one under latest adoption settings or sessions. Gosh. I can't read today. That will be the one that we had from last week. So you can click on that. When you go here, you will be asked to, register. So if you put in your information and click submit, it should take you right into that recording at that point. So use that link there and, that will definitely be something that can help you get to that session. And you'll also see here that I've had a past, ask the expert about compound queries as well. This is from last fall. So that will definitely be something to, to take a look at as well. And this one actually too may also be the one from last fall. It may not, but it was pretty much the same. It was I didn't make any changes to the slide deck that I presented. So should pretty much be the same content as what I did last week. But this is always a good, link to to bookmark and to have. K? So, again, one of the things to be mindful of is if you're adding two two queries together, no problem. Doesn't matter what the data return type of those two queries are. They will add the results together, and it will also display the information based on whatever data return type you've chosen. Okay? But where you need to be mindful and where you need to be careful and where you do need to double check your results is when you do subtract and intersect. For example, here, because I like I said, was subtract and intersect. It really does matter what your two queries contents are because in this case here with this example, those two lists do not match. So if you were to intersect these two, it will show you no results. And if you subtract these two, the results will just be the this year's entries because it could not subtract out anything from last year. Couldn't subtract out the accounts, it couldn't subtract out the matching information because there was none. So that's one thing that I always say be mindful of what your data return types of the two queries are, what those two queries designs are, what it is that you are trying to do with those two queries. K? Something else I want to also, almost everybody will have in their, base category. I think we've even I let's put it this way. Most everybody who ends up doing any kind of mailings, especially if they have the user defined field. Let me get into my account here. Most everybody will have the user defined field in their accounts, in their constituent accounts for mailing status. We began to I mean, we we used to recommend that all the time. Back in my days of support, we didn't use to automatically include this user defined field into accounts, neither did we include account type, which is also very beneficial, very important. But we then, later on, because we recommended these two fields so often, we began to just include them inside of databases. And, mailing status is a very, very important thing for people who do a lot of mailings. And that's because sometimes people don't wanna be mailed anything, sometimes they just don't wanna receive a solicitation, solicitation or they don't wanna receive a newsletter. They don't mind receiving solicitations, but don't print out a newsletter for them. Sometimes you get something returned to you, so it's a bad address. Sometimes you have, folks who pass away and, you know, they're marked now as deceased. Well, you don't want to include people with one of these statuses in your mailings. So one of the most common compound queries that we recommend people do is what we call a clean mailing list. It's so common we actually have a often used KB article, knowledge based article. And the others, as well is to, or the, the one thing about those is is that it's so common. Like I said, we have a KB article. We used to have an entire step by step in the help section, which the help section doesn't normally get into the to the minute details, but that is something that is, oftentimes, very, very, very much asked for. So it's yeah. And because it was so asked for, we did put it into the, into the help section, but then we we moved it over to knowledge base. And, yes. I will, get that knowledge base article and link it over here as well. But, essentially, what it is is if we go into my base category, you'll see that I created a query that's just finding the people that we don't want to mail to. And what this was was just an account return type query using all constituents as our starting query, match at least one of these criteria. I could have included any other ones too. I mean, I could also say field has any value and it would just capture everybody. But because I specifically said, no, I don't want do not solicit bad address, deceased, and do not mail. I wanted to make sure that I had this match at least one criteria. So any account with any one of these, marked on it will show up. And then what I did after that was I created a compound query that says, okay. Now I want the accounts to subtract. Query number one is my base all constituents. Query number two is base do not mail, and that subtracts out. And that's an easy peasy way to find people that are up, that are allowed for, you know, for you to mail to or that, you know, that there are no restrictions on what they are receiving. Oh, Mordecai, yes, asked, can I repeat why we should double check the subtract and intersect queries? So the reason why I recommend that you double that you double check the results of that, and you should do that, I mean, even for this, you wanna double check. If you know somebody who let's say you're subtracting out do not mail people and you know that John Smith says 'I don't want to receive mail from you'. It's always a good idea when you are doing your compound query that you preview your query so that you can go through your list and say 'Ah, John Smith does not show up. This should work. And you can double check a few of the other people in your query by going into their account and double checking them to make sure that they don't have a, like a do not mail or something like that. But it's important because you wanna make sure of two things. One, did you build the compound query correctly? Are the two queries interacting with one another correctly? And number two, was the data entered originally correctly? So for example, this can happen even when you have, when you're entering in a gift. By default, whenever you enter in a gift, it's going to be today's date. Well, maybe you meant for that to be last month or maybe you meant for that to be last year, and you didn't change the date. So what ends up happening is that it ends up creating a situation where the data was entered wrong, so it's not gonna do what you want it. If it's something that's going to play into a compound query, it's not gonna play incorrectly depending on how you, say, intersect or subtract. It's just a good way to double check those two things. One, did the query work the way you expected it to, and two, is the data entered properly? That's why I say it's a good idea to double check that. Wilma asked also, is it possible to use, for the queries like the opt out? Yeah. So, I mean, you can, there's a couple of different ways you can use opt out. If there is, if there are accounts that are opted out, of, like, emailing, that can be added by going into, changing the commonly used fields to account and it should there you go. And you can say, yes, they have opted out and still, it's saying match at least one criteria. They've either opted out of mailings of emailings in particular, or they've opted out of one of the mailing statuses. If you want to, you can also add something like opted out to your user defined field of mailing status. So you can go in here, go into, under management, you go into user defined fields, you go to base, you go to mailing status, and then you can add that here as well. And to follow-up that question, Wilma, is this just for email or, or as well or is this for email or as well with mailing? That's up to you. Most of the time, if somebody is marked as opted out for emailing, they will already be taken into consideration when you're doing your next emailing. Most of the time, if people sign up for, email, and as long as they don't opt out, you don't have to worry about building a compound query around that. It's usually just for physical mail that you need to be concerned with that. So that's something else to take into consideration. Most of the time, people treat physical mail and, the, email as two different features. And, yeah, that opted out field that I showed you is specifically for, usually specifically for emailing. And that specific field that I showed you actually shows up if I was to receive an email and I said, nope. I'm gonna opt out. In my account under personas, it would say this person is opted out of mass emails. Right now, I've I've not opted out, so it says not opted out. So that opted out field is specifically for emails. Some people do track something like that in their mailing status, to take into consideration, but typically, opted out when you see that somewhere in the database that is specifically for mass mailings or mass emailings rather. Yeah. No problem. As far as the knowledge base article, let me go ahead and get that for you here. Just go to kb.blackball.com. And, actually, let me link that as well. When you go to that kb.blackbaud.com slash knowledge base, it will pull up this first, screen where it will go ahead and ask you what what it is that you're looking for, and you select, in this case, eTapestry. How do I create a mailing list that does not include do not mail bad address, etcetera accounts? That's our help doc or that's our, knowledge base article here, and I will link that over into the chat as well. And this will go through first the create the accounts that should not receive the email. That's that do not mail that I had. And then it's the remove those do not mail, and that's the compound query, and that's what is ultimately your clean mailing list. And then here it says, this clean mailing. This is also important to understand. This clean mailing list can be used as the starting query for another query if you need to further define your mailing list. So what it means by that is, okay, we've got our clean mailing list. You know, maybe sometime down the line, I'm going to send another mailing, but I'm only going to send it to people who gave something last month or something like that. So if I come in here and I'm gonna create a new query, I can come over here and say, I want the, clean mailing list to be my starting query, my common denominator for everybody that I'm now going to look into that had a, who gave to a specific fund this year or something like that. And then that will that will not look at anybody who is marked as do not mail even if this year they gave to the unrestricted fund. So keep that in mind too that compound queries are absolutely available for you to use in the starting query section as well. So that's kind of like, much like with the compound queries. Obviously, compound queries are going to be available for communications, for reports, things like that. But not only are compound queries available in other compound queries, but they are also available in your standard regular queries as your starting query option. Let me take a sip of my drink here while I wait for any other questions that might come up. Rebecca says I'm not showing the do not mail option under my defined fields. If you go into management and go into user defined fields under database configuration, Rebecca, click on the base category. Do you see mailing status? Because typically that's what it will be that's that's what we generally call that field. And that's where you will find your options as the values where it will say do not mail, do not solicit. No newsletter or bad normally, it will be do not mail, do not solicit, bad address, deceased, and not head of household. Usually, not head of household is not really used anymore if you have household relationships set up, between accounts. You wouldn't need to mark anybody as that. But do you see mailing status by chance, Rebecca? No. Okay. Then what I would recommend in that case is to create that user find field. And this goes for anybody who maybe doesn't have mailing status as a a field inside their database. I thought that there was at least there was a period of time there where we were including that user defined field already being created. But what I would recommend is go under management, click on user defined fields, we'll go into base, and here we can create a new defined field, and you can name this whatever you want. You can name it do not mail, you can name it mailing status, you can name it whatever you would like. But the key thing to do here, there's a few steps here that are going to have key features for you to, take into consideration. First, you want the data type on step one to be text. On step number two, you want the, field application to be set to constituents, and I would not check any other box. The reason for that is is that you want there to be one clearly defined place that you want this field to appear on. There are consent options here that are available. For those of you who are in, The UK, that might be something to take into consideration. I doubt it would for this field, and it certainly does not apply to every single field, but that is something to take into consideration. There's a little question mark icon that talks a little bit more about that. Field attributes, I would leave all of these unchecked. You certainly don't want it to be required because you don't wanna have to have it filled in for every single account, especially if once we get to the values, you're only selecting the negative values, the people who don't want to be mailed, or for whatever reason shouldn't be mailed. So I would leave all of the field attributes blank. The next important thing is under display type. I would recommend either selecting the first option, the selection from a set of values, which is the checkbox type of field, or allow assignment of only one item. I would lean sometime depending on what values you wanna have there, I would potentially lean toward the selection from a set of values because there could be multiple different mailings that you might send out. You might send out a solicitation. You might send out a newsletter. You might send out a, a volunteer email or something or a volunteer letter or something. Whatever the case is, if you have multiple mailing or types of mailings that you send out, you might want some people to only receive certain ones and therefore be marked off not receiving all of them. So selection from a set of values gives you the option opportunity to select multiple items within that field. Nicole asked a good question here. Is there a difference between do not mail and the remove from list, yes, option, function in user defined fields? It is possible that your database may have it listed as removed from list, and you have it marked yes for those people who you want to have removed from that, that could be how your database has that set up. So it is possible you already have something that's taking into consideration that you don't want somebody to be mailed to a list. Yes. And, Judith, good, good follow-up there, Judith, on that. That it it'll remove from list may imply that a decision was made by the donor or the administration, maybe not necessarily tied to mailing, but it would be something to to at least explore and look and see who's marked with that, through a query and then try to figure out, oh, okay. This is why these people are marked this way. They are for, not to be mailed to or they are somebody who may be, may be getting removed for a very specific reason. Mordecai is, asked, is there a live person to speak with if I have a specific question and can't find the answer besides that chatbot? You should be able to ask the chatbot to be connected with a live person. I don't fully know exactly how that, how that process works through, you know, signing up to speak to somebody from, support from the chat. But you should there should be an option, and I'm just kind of the way it was described to me is very similar to how my cable, support is signed up or the way it works out is that, you know, I sign in to chat. They try to help me through the chatbot first, but then I can say, no. This didn't really help me or this wasn't what I was looking for. I would like to speak with a, with a, with a member of the team or something like that. And it can get me into the live chat with a live person. It sounded very similar to that, but I don't know exactly what steps it takes to get there. But you should be able to to request speak, you know, to speak to a, a live, support person as well. Yeah. As Joanna, yeah, as Joanna mentioned there, yeah, you it it and it is dependent on the time because if it's closed, then, of course, it wouldn't be available at that point. Bella asked, do you have to create a new category to sort on base? What do you mean by that? Because base itself is a category. So if you have something created within base, you there isn't a way to create a subcategory, but you may not necessarily have to create a different category. So, Bella, if you can, perhaps, expand on that a little bit. Okay. So after you select the selectable type, normally, you can bypass security in this case because security really is not going to be something that's going to be, really kind of effectively working on this field. But then in values, this is where you can add your do not mail, bad address, deceased, and whatever other values you want. And once you fill in your value values, you click save and finish, and then it will show up in the, define fields page of those accounts so that you can then mark people as do not mail, create the query for do not mail, and then subtract them out of your all constituents to get your clean mailing list. Oh, great question, Sharon. We have a grandfathered 02/2013 database that needs calling. What compound queries might I use to discover who needs to be deleted? Great question. So you're working with potentially data that may be more than a decade old, and there may be data from before 2013 where, you know, it's just historical data from accounts that may no longer be part of the database. So one thing first thing I would recommend is determine a basic idea of who needs to be called. Are they accounts that were added within a specific date, or in a specific time frame from years past, like, maybe any any account that was added before, 2018 that does not have any journal entries or does not have any gifts in them. So there you would say find all of the accounts with let me go into if this was our query to find all of our accounts that gave, or that was entered in be you know, before a certain date, we would change the drop down menu to dates, and we would find account created date. And we can say, okay. Find everybody who was created before 2018, let's say. Maybe you want that to be more like 2020 or 2019, but you would say, okay. These are all of the accounts that were added to the database before this date. You save this query and that will say, okay, here are all the accounts that were created, then. Then what I would do is I would create a second account return type query that just simply says that they've given something. So here, we can say individual transaction received greater greater than or equal to a penny or or whatever. You can put in one for a dollar or pound or whatever. This will then find all of the accounts who have ever made a donation, and then your compound query would be the people created before that date minus the people who gave. That would be one list of people that you would say, okay. These people, we should be looking to get rid of from the system because they were created, you know, seven, eight years ago and they haven't done anything. The next group of people that I would consider is the people who are lapsed for many, many years. So what you would do is you would find all of the people who gave, basically, the query would be, okay, find everybody who have who has given a donation since, oops, since 2018. And this would be a query of accounts that would say, okay. Everybody who gave since 2018 accounts, and then you would say, okay. Now I'm going to subtract out from that, or I'm gonna subtract these people from all constituents. And that would leave you with people who have not given since that time frame, who are probably considered lapsed. Whenever you're dealing with somebody who maybe have given something in the past, but they are now lapsed, I would consider running a report just so that you have that data someplace just in case they come back or just in case they, you know, they they contact you for some reason to get information about something that they maybe have, you know, donated. So it would first take consideration over what are the what are the, determining factors over whether or not they need to be removed from the database or not. Then number two, then figuring out, okay. Well, if we're talking about people who've been added but haven't donated anything, that would control what the two queries would be used in the compound query for. Or if it's a situation that they've just lapsed for several years now, then that would con that would be a similar idea subtracting those accounts from the others, but it would be changing what query number one and query number two may be looking like. So those are those are some ideas, to to take into consideration there. It really then it really would then come down to what exactly are going to be the determining factors over what needs to be removed is really what it comes down to. And then we can figure out the compound queries from there. So Bella included the additional information. So I go to management then to queries and then to user defined fields, but I, can't see base like like I have on your screen. Ah, okay. So yeah. So you go to yeah. So management, user defined fields. Usually, there's a base. Now it is possible that you renamed your category to something else, and you no longer have base. Base is what we typically include in databases as kind of like the miscellaneous, category. There's a base in queries. There's a base in in in the user defined fields. If you don't see base, it is possible that that category was renamed or the, fields removed to different categories and base was deleted. Yes. And Michael is absolutely correct there, Joanna. Yeah. Mass update would be, the way to go. So, like, let's say, you found all the people you don't wanna contact. How do you update all of their fields in one go rather than individually? Yeah. So if you have the query of the people that you know you don't want, to be mailed to, you go into management, you click on mass update, and you'll update existing accounts. That will be something that I will be touching upon next week when I talk about, cleaning the database, and keeping a a clean and tidy eTapestry. So that is something to, possibly look into, signing up for, and I'm sure will be covered, on the on Tuesday, the twenty second, and they ask the expert there as well. Alright. So any other questions that I can help with here? We're kinda getting down to the last ten minutes or so, so I wanna make sure that I cover any other questions. Now I know the, I know this topic is a very large one. You're not I did not expect either last week or this week for anybody walking away and saying, oh, I'm an expert now in in compound queries. It's it's a complicated topic, and there's a lot of things that can come in and out of that, come in and out of play when it comes to doing these kinda compound queries. But, I'm hoping that you are at least getting some idea of, okay. Well, if I can at least do this in compound query, if it works, great. I kind of have an idea of what I did right there. If it doesn't work, I have some idea possibly what could be wrong, but I also know, you know, that support can assist with that as well. But, Christy, yes. So does the system give a report of those who donate a thousand dollars in total through the years? So, yeah, that is what would be called a cumulative query. I would scroll up to that KB link that I sent, and, there is definitely some some articles that talk about how to create a query like that so that you can find that. Mordecai. Yes. See. Bella, how do I find it and put it back? You're probably not going to find it if it's not listed when you go into management and then user defined fields. My like I said, my guess is is that the base category has been renamed or all of the query all of the user defined fields that were in there were moved into different categories, and then it was deleted. But you can create a new category and call it base if you want. What I would do before doing that is just if you have other if you have other categories listed there, then take a look around and see what might be, you know, what fields are in those categories. You can expand each category by clicking on the little plus sign. So if you see other categories but you don't see base, open up the categories, look and see what might already be in there because that's very possible that all the fields you need are there. They're just not under something called base. Yeah. And you can also like here, like Michael says here, under find, you can say mailing status, and you can search, and it will show you the category it's in and then the field itself. So that's something else you can do. Good good catch there, Michael. Yes. As far as, like, where you can find the link for, upcoming, normally, if you just log into eTapestry, first and foremost, there is a, this section up here where you can see sign up for new eTapestry webinars. You can click here on the eTapestry Blackbaud eTapestry insider tips and tricks, and that will take you to this link that I will put in the chat. And this is where you can sign up for what's coming up here. And you'll see that I have sessions planned out through mid May. Explain which one, Sandra? The searching for the field? Oh, how to find the tips? Yeah. So when you log in to eTapestry, we have this running, bar that scrolls across the top. There will usually be something like this listed here. So, like, sign up for new eTapestry webinars, and here is where you have that link. Now the link that I just sent a couple of minutes ago, is that link that it takes you to. So if you, see right before you asked, if I can explain that one more time, that's, that's the link that you can use to to sign up for upcoming sessions. Alright. So just a couple of things that I want to cover before we, wrap up here today. Let me get back here to my slides. I definitely recommend, taking advantage of these resources, especially when you get into, like, slightly more complicated ideas like, you know, like the the one situation where it's like, well, we have some you know, we have a lot of data. We need to get rid of some of it. One of the things that I would recommend doing is making sure that you take advantage of the community, because that's a great way to, ask, you know, you know, put something in the community and ask the folks who are in there, you know, what are some of the the tips and tricks that they may have for certain, concepts or ideas or things that they may be working on. Of course, we also have knowledge base and support, that can help, with some step by step information. But I would also recommend everybody take advantage of the Blackbaud University. If you go to blackbaud.com, you sign in with your Blackbaud ID, there is a section there for training and support. The training in there does have the option to provide, or to give you the, eTapestry curriculum and there are several resources in there. If you have a learn more, subscription, you are able to sign up for, live instructor led courses, but everybody should at least be able to, access any of the on demand, sessions that have the word basics of eTapestry in the title. And some of those will touch upon, concepts of, like, queries, reports, communications, and a few other features as well. Nicole, as far as getting a learn more subscription, I can put you in contact with your, with your account executive to look into, you know, what what that, would be like, as far as, like, cost and whatnot. So let me just write down your information there. Okay. Now something else that I also want to call to your attention as well is we do have these other programs where you can engage with both Blackbaud and your peers. None of these do you have to be a Blackbaud expert, but, like, with Blackbaud champions, I like to kind of consider that more like, you know, more like community plus, if you would. Community, where you can interact with not only Blackbaud users, but also members of the Blackbaud staff, might get in there and and help answer some questions as well. But, with the Blackbaud champions, that not only helps us spread the word about Blackbaud products and services, you can also provide feedback to Blackbaud teams and, participate in professional development opportunities. We even also have, like, a gamified rewards program in there as well. We also have the reference program where that's a little bit more detailed where a a perspective, customer might be looking to talk to somebody about some of the things that they've done inside of of the Blackbaud product that they're using. In case in this case, it would be eTapestry. It would give you the opportunity to, say, yeah. Yeah. I'll take a call and talk to somebody about what they're working with and maybe see a little bit of what I do with my eTapestry database. You have total control over how often you take a call from, from a prospect. If you want to do it once a week, you can do that. If you wanna do it once a quarter, whatever it is, totally up to you. We also have the spotlight your success where we can, either invite you to speak at a webinar or, maybe potentially have you write a blog for the community. And, anything else that you might be, you know, willing to share with your success and, maybe even create a success story around your use of eTapestry. So these are all things that I would like for people to take in consideration. If you, are interested in, doing a little bit more, and signing up for one of these, programs, let me know. I will get you in contact with that team, and they can, they can take it from there and and help you out there. Oh, yes. Mordecai. Yes. You're very welcome. Look forward to the, to seeing you next week. And, Bella, I am taking down your information for champions. Okay. Monique, JustGiving is not gone. JustGiving is actually what's replacing the old eTapestry, fundraiser, piece that we used to have inside the database. Just Giving come it integrates with eTapestry. We just, it's a it's a lot more modern. It's a lot more it's a lot newer. So we replaced, the eTapestry fundraising with that, with that JustGiving. So alright, I think we are pretty much at the end. Alright, Marilyn. I will write you down to alright. Thank you everybody for, for coming today. I hope this at least helps kind of demystify a little bit on the on the, compound queries. I think this is something where it's it's a lot more of a bigger topic because there's so many different things that you might want to compound that you might want to, subtract or intersect with with other lists and so forth. But, I hope that this at least is a start, and I think this is something that I will probably revisit down the way. Like I said, there is some development going on around compound queries. I don't have a time frame when that's going to happen, but I will say it's really cool looking. If you do end up going to, the, product update briefings in early May, you'll see some of that, advertised. Of course, that's going to be advertised on the home page and those banners that run across this top. So if you do wanna sign up for that, I definitely recommend that you do. But I hope everybody has a great rest of your day, a great rest of your week, and I look forward to talking to you again soon. And, for those of you who are going to be attending next week when I start talking about some cleanup tips, I look forward to talking to you then and, hope you have a great, rest of your day. And I hope that spring is starting to to to take, take hold in some of the areas where I know it's been cold for way too long. So thank you so much. Have a great rest of your day.