Name: Combining and Comparing Query Results with Compound Queries in Blackbaud eTapestry®
Uploaded: 2025-04-02T18:30:47.575Z
Duration: 57 min
Description: Combining and Comparing Query Results with Compound Queries in Blackbaud eTapestry®

Transcript for "Combining and Comparing Query Results with Compound Queries in Blackbaud eTapestry®": Hello, everyone. Welcome to this week's webinar. This week, I'm going to be, talking about, compound queries and what those are, what are some tips and tricks in using them. I, this is something I did, previously, at an earlier, in an earlier webinar last year, but I know this is a topic that gets a lot of people, confused or, they've never really kinda messed with stuff like this before. So I thought, well, this would be a good idea to, to go ahead and rerun this one. So, as people are getting settled in, I'm seeing, quite a few people joining, which is fantastic. A couple of things I do wanna do before I get into, introductions here. One of the questions that gets asked a lot in these sessions, I'm sure will get asked by somebody who will come in slightly after I make this announcement, but, this is recorded. This is something that you are able to, come back to. Use usually, you can just use the same link that you had previously to access the webinar. You'll be able to, use that to get into the recording, usually, by later in the day, but you will receive an email about twenty four hours after this completes, with a reminder and a link to say, hey. You can go check out the recording. If you want anybody else at the organization to take a listen to this, they will have to register separately. But, when it gets to the recording side of it, once they register, it will allow them into that recording. So just wanted to make sure that everybody was aware of that. Now one of the other things that I also want to, make sure that I make clear before I, get into the introduction of myself here. I am, recovering from a pretty nasty head cold. For those of you who are in the Midwest, you know this time of year, not only is there allergy season, but there's also a, a spike and a immediate follow-up with a dip of temperatures that has thrown me for a loop over the last few weeks. I am mostly recovered, but if I do need to cough or something like that, I'll make sure to take myself, onto mute. And, I may, you may see me take a sip from my drink a little bit more often, but feeling pretty good today. I think we are mostly beyond that. So with that, now that, several people have joined, I will do a quick introduction. I am Geoff Arbuckle. Many of you probably already know who I am because you've attended these sessions or I've worked with you in the past. I'm a customer success manager. I'm actually on the arts and cultural team. However, my expertise has always been in eTapestry. I am coming up on nineteen and a half years of service here at eTapestry and Blackbaud. I actually joined eTapestry before they became part of the Blackbaud, family. I am located in a small burg inside of Indian Indianapolis called Beech Grove. I'm a big time comic book collector. I'm a big movie fan. I love animals, particularly cats. I have two of them, Kirby and Sadie. They keep my life, pretty busy most of the time, chasing after them and sometimes cleaning up after them. Real quick, one thing I do wanna say about my comic book collection, I actually just recently completed an entire run from 1963 to present of Avengers comics. So that's a new little, trivia question about me. I actually have every single comic book that has the Avengers in the title since 1963. So something I'm very proud of ultimately means nothing to what we're going to be talking about today. But, so let's dive into what we're going to talk about here. And, at any point, you are more than welcome to utilize the chat, to ask questions as they come up. I will try to keep on top of those and answer as many questions as I can in this hour that we have together. Next to chat, you will see a little, link for docs. There is a copy a a PDF copy of these slides that you can also, download and and, utilize if you want to, save those for notes or for anything else that you might be, taking down while we go through this session. Mhmm. Alright. So what are compound queries and why do we need them in eTapestry? Well, simply put, compound queries takes two queries of any kind. They can be a, just a plain old typical query or a standard query, and, you could also include another compound query. But what it does what a compound query does as you set it up is it reviews the results of each and based on what you want to do with the results, whether it's add, subtract, or intersect, it will then combine, compare, or remove the results. We'll talk a little bit more about what each one of those add, subtract, and intersect means technically as we go through the or as we go through the session, but that is really what a compound query is. But why Why can't we just do this in one query? Well, sometimes criteria for queries are not able to exclude or create a matrix that would say include someone who did this, but not those who did that. Standard queries or just your typical queries can really only match all or any of the selected criteria that you choose within, that queries setup. So, you know, for example, you can say, well, I wanna find everybody who gave a gift to a particular fund in a particular year. Well, that would be a regular query. But if you wanted to say, I wanna find everyone who gave a gift in 2024, but I want to exclude everyone who gave a gift to a specific fund or anybody who gave a gift in 2025, that you can't do in one query. You have to create a compound query to be able to look at those two results and then, single out the exact accounts or the exact entries that you want. Now let's talk a little bit more about building a compound query. So building a compound query is no different than building a regular query. So when you are, logging into Tapestry, if you go under queries, you can either click one of the categories that's listed, they show the first ten categories inside your query section. You can click on one of those or as you see the second green arrow at the bottom of that menu you can click on manage queries. Now just like with any other query you have the first thing that you will see if you click manage queries will be the list of your query categories. Now the main section of this page will show you all of your existing categories that you can create a query within. Although you do also under tasks have the ability to create a new category. So this allows for you to create a brand new category to create specific queries that you wanna work with within that new category. Alright. So oh, and I'm just catching up on a couple of, people who who sent in through, q and a. Rayma Hutchison mentions that she had used eTapestry for twenty years. And, yes, Rayma, I think I used to talk to you and support quite a bit and, of course, in these webinars. And, Bella, hello, coming to us from Saskatoon, Canada. Nice to have you here. Thank you. I just wanna make sure I caught up on that before. Moving on there. Okay. So if you were to either click on a category that already existed so going back to this slide here, one of these that are in like the main section there where it says existing categories available, or if you created a new category, saved it, and then clicked on it, this will take you inside the category where you will see something similar to what you see when you see your listing of categories, but there'll be two major differences. The first thing is in the main section of the page on the right hand side, you will see your existing queries that have already been created and saved. You can go in, as long as they're not one of the, one of the pre created preset queries that eTapestry provides you with, you are able to edit those queries. However, you can also create a new query and on the left hand side under tasks, you will see new query, new compound query, new custom account query. For the purposes of what we're talking about here, today, you would, in this case, create a new compound query. Now generally speaking, if you were creating a regular query, you would see the query basics, the starting query, the results, and the criteria options. So these are like the query basics. That's how you name thing the name the query. The starting query is like the the the lowest common denominator that you're starting with. The results are whether you want accounts or data return or the, accounts or journal entries for your data return type. And then your criteria is how in a regular query, just a plain old basic query, that's how you would say, I wanna find everybody who gave something in this date range. However, in a compound query, most of the stuff is going to be lost. The two main things that will remain are your query basics so that how you name the query and whether or not you wanna make it a favorite, if you wanna make it something that only admins have access to, whatever. And then you have your results, your data return type, whether you wanna see accounts or journal entries. You do not need to worry about the starting query. You do not need to worry about creating query, criteria. So after you name it and you set your data return type, the next thing you will see is a portion of the screen that will basically say, how would you like the results of each query to interact? And you'll have three choices. And each one comes with, like, a visual, like, Venn diagram guide as well. But it was, your first choice is intersect, second choice is to add, and the third choice is to subtract. And then underneath that, you will see where you can select your two queries. Now one of the things that will be coming up here very shortly as we, you know, kind of explore what compound queries can do. There is sometimes a definitive, a a a definitive query that needs to be query number two or query number one. It depends on whether or not you are doing subtraction or something else. I'll talk a little bit more about that. But, query number one is, you know, oftentimes, like, if you're doing a subtraction, query number one would be like if you were doing a a regular number. For those of you who are still, old like me and still like to keep a checkbook, it's the number that you start with, and then query number two would be the number you're subtracting from. So there are instances in which query number one and query number two need to be placed there very specifically, but, for the most part, this is what you would see on this screen. So let's get a little bit more into what each of these various options are. So if we were looking at ad, this is the simplest one. So this is why I like to start with this one. It just simply takes the two queries selected in the query number one, query number two section and then just adds them into one result. So, like, let's say you already have a list of everybody who gave, to a specific fund this year and you want to add them to a list of everybody who gave to a different fund last year. So you have accounts who gave, to that you know, to fund a in 2025 and you have everybody who gave to fund b in 2024 and you want them to just all be in the same list, well, if you already have those two queries, you can do a compound query and just add them together. And my example there, very similar to what I just said, the you're adding an existing query of donors with a particular attribute to a list of donors who gave in a time frame. So this is just taking two lists and putting them together. Now if somebody is in both lists, they will still only be listed once. So you may see query number one has 50 results, query number two has 25 results. But when you preview the the, new list with both of them put together, you may only see 65 results. That means that 10 people appeared in both lists, so they're not gonna be listed twice in that regard. Subtract, this takes two queries selected in the query number one and query number two and it removes the results from query number two from the list represented in query number one. So the the most common example of this is what we call a clean mailing list. So basically, what you would have is you would typically set up a query that will find anybody who has some sort of a mailing status. They're deceased. They are, they're listed as do not mail or do not solicit or you list them as bad address, most of you will likely have a, a user defined field for mailing status that will allow for you to enter somebody in as deceased or enter them in as do not mail or something like that. If you've never used that before, you will find that by going into a constituent's account, clicking on the the define fields page for them, and it should be listed under base. So you may have to click on base to expand it, and you should find mailing list there. But if you wanted to make sure that those people who are deceased or it's marked as do not mail don't get the mailing that you are preparing, you would typically create a compound query that's called a clean mailing list. And query number one will usually be all constituents. Query number two will typically be your, do not mail list. And when you do the subtraction, it's gonna take those folks who are marked as do not mail out of your constituent list, that, you know, take them out of the results of query number one. Subtraction is there are some things to be careful of that I will talk about a little bit, coming up here in just a moment. But for the most part, much like add, it is a pretty straightforward concept. I want to remove a a group of people from an existing list that I have a query for, and that's what the compound query for subtract would do. Intersect, basically compares the two queries, for query number one and query number two. And what it will do is it will find anybody who matches from both lists. Now let's say you have 50 people who, well, we'll use that example that that I had before. Right? You have 50 people who gave to a particular fund in 2025. You have 25 people who gave to a different fund in 2024. You do an intersection to find the people who did both, and what you would you know, you might find that there's 15 people that were that appeared in both lists or there was 10 people, I think, was my previous, when I used the that same idea in the ad. So what it will do is it will compare the two lists that says, okay, and says, let's find anybody who, gave or or who appear in both of the results and then that will become our new list. So, when you are doing, the, you know, an intersection, it is plucking out the people who meet both sides of, you know, both query number one and query number two, and it provides you with that list of people, that do appear in both. And the example here is, you know, you have one list of people just generally who gave in one time frame, another list of people who gave in a different time frame. You do the intersection and what you'll find are the people who gave in both time frames. So that is something, that is, you know, very helpful for you. And, Betty, I think I answered your question about whether or not that, takes out the, yeah. Okay. I see. Yep. I did answer the question about it taking out the duplicates. So yeah. So, you know, the only time that you may not see duplicates removed so this is one thing that the data return type becomes very very important when you're working with a compound query. So let's say you have list of journal entries, the journal entries who gave in one time frame, journal entries who gave in a different time frame, if you added those together, because it's journal entries, you would see those people marked multiple times, if your result is going to be journal entries. But if you do the data return type of accounts, it will just show the person one time. It won't show the duplicates. Unless for whatever reason, there are there is a duplicate account for that person. That's always a possibility, but I'm I'm going to assume that a lot of you are already kind of taking care of, you know, are taking care of your duplicates. Molly asked a really good question in the q and a here as well. If you need to make a compound query on three factors, how do you do one? How do you, would you do one compound query on two factors and then use that compound query as one of the two queries in a second compound query with the third factor. Yes. So let's say to, you know, to kind of simplify what Molly was asking me there in the q and a, Let's say we wanna find people who gave in 2025, who also gave in 2024, and who gave in who also gave in 2023. So what you would do is you would take the first two and you would say, okay. Give me, you know, the accounts who gave in 2024 and 2025 intersect to find the people who did both. And then I want to take that compound query, put that in a new a second compound query is query number one and intersect it with my third query which is the people who gave in 2023 and then the result will be everybody who gave in the in all three of the time frames. So you can use compound queries in new compound queries as well. It's just it's doing the exact same thing. It is comparing, contrasting, adding, subtracting, intersecting from one query to the, to the next. And just so that everybody I do see, Monique, you asked about the, you know, you're not able to see, you're not able to see q and a or chats. So the questions that I'm getting are coming in through the, q and a side. Those are not publicly available. Chats are the ones that are. So that's why you may not be, seeing those those q and a questions come in. Yes, sir. So you can compare more than two queries. The thing is you have to do it in multiple compound queries. So each compound can only compare two queries of any kind, but you can take that compound and use it in a second compound to compare it or, use it to add or subtract or whatever a third query at that point. So you can while compounds limited to only two, you can take that compound into another compound and and utilize the same features there. Alright. So let's talk about some things to keep in mind when it comes to, working with compound queries. So I I wanna say and what I have there in the left is I always try to advise people to not overthink compound queries. Yes. These can be difficult depending on what you're trying to do, and they can sometimes become almost strung out in the sense that, okay. Well, I've gotta do all of these. Yeah. I'm doing multiple compounds. I'm taking compounds upon compounds upon compounds. However, overthinking the process can complicate things much much more, and underthinking compound queries can also, be harmful. I like to say that when it comes to compound queries, they are a difficult concept. However, there is a method to the madness of a compound query. So think about what you're looking for. Are you simply trying to add two lists together? Are you trying to exclude some folks? Or do you need to find the similarities between two lists? Those are the first question that you'll need to ask because that's gonna determine if you're choosing add, intersect, or subtract. Compounding can be used as a shortcut. So if you already have two lists, like people who gave last year and people, and people with a particular attribute, If you already have those two lists, using a compound query to add them together instead of building a new query can be a shortcut. Adding is almost always a shortcut. Now the compounds, like I was saying, can also be compounded, so any query is available to use in compound queries. Most commonly, it's the regular types of queries, but custom account queries and compound queries can be used in those two. So, you know, like I was just saying, you know, while most of the time you're gonna take two regular queries, the the the most, typical types of queries, yeah, you can also say, well, I've already got a compound query that does x, now I want it to be used in this compound with another query so that it can give me y. That's absolutely doable. You can also do the same thing with custom account queries. For those of you who've never used a custom account query, custom account queries you build one by one yourself. So, like, if you were to, wanna have a list of 20 people that have no, similarities that you can really query on yourself, You can put them into a custom account query where you individually search their name, add them to the custom query. Those can also be used in compounds. But the number one thing is that the matching data is going to be key. This is very important for subtracting and intersecting. The system must find exact entries or accounts in order to be able to subtract or intersect queries and that's gonna be something that I'm gonna be going into much more detail here in just a moment. And I think, Diana, this is gonna help, answer your question as far as can compound queries use different data return types, because that is something that can very quickly derail the results from working out the way that you want. So it is important to understand if you're intersecting or subtracting, there are some things that you need to keep in mind, as you are selecting your queries for query number one and query number two. Sometimes the data return type of those individual queries is going to be very important. So with that, let's get into a little bit more of examples where the data return type can work for you perfectly or it can create a little bit of of, caution or it can create havoc. So when subtracting and intersecting, like I had mentioned before, the compound query will need to compare data in each query. So to be able to actually get results, what the compound query is looking for are exact matches. So, accounts minus or intersecting with other accounts tend to work best. In this example, I have accounts query number one is my base all constituents query. Query number two is my list of accounts that are marked as do not mail. There will be one to one matches if Geoff Arbuckle is a constituent and Geoff Arbuckle is matched or is selected as do not mail, then Geoff Arbuckle will not show up in this subtraction result. If the do not mail was a, journal entry return type, then the one thing that to to make sure the Geoff Arbuckle is removed, all of my journal entries have to be in the journal entry return type query. Otherwise, if there's just a single journal entry type of any kind in my account, it will not be a complete match to remove the account as a whole. So when you're subtracting, I tend to, I I tend to caution people that you want to make sure that you are subtracting accounts from accounts. Especially with subtraction, that is going to be the number one thing when people have, you know, reached out to support my in my days of support or they reached out to me and said, you know, Geoff, I tried this compound query. For whatever reason, this person keeps showing up. They shouldn't be showing up in the results because they have the thing that I wanted to subtract. And if we were to look at the queries, query number two might be selected as a journal entry return type, and that's why it's not subtracting. It doesn't capture that the entirety of that person's journal entries. And so therefore, Bob Smith still shows up even though he was marked as do not mail. So, so that is one thing to be, especially mindful of and especially, keen on is accounts minus accounts are always going to work the best, especially in subtraction. Now the next, the the next one is a little bit of a different one. So here, we are intersecting accounts. Oh, and I'm sorry. I the the the third is the third example that's a little bit different. But here, we are intersecting accounts. Accounts and accounts, it's gonna match up. It's gonna say, hey. I see Geoff Arbuckle in the major donors for 2024 and do not mail. He's gonna be pulled into the results because they do intersect. His exact account matches. So again, accounts, comparing to accounts, there should be similarities found. So there shouldn't be any issue with being able to find those in a intersect compound query as well. Now when we get into the topic of mixing data return types, this is there are ways that this can work perfectly, and there are ways that you might need to use caution. I'm gonna take a break here to take a sip. So if we were working with two different data return types for our compound query There we go. Alright. Moved. So here we have all of the journal entries from last year, and it's a journal entry return type query. And from that, I wanna remove all of the accounts that are marked as do not mail. This will work because the accounts are going to remove every single journal entry from the account that it was marked do not mail. So this is a scenario where query number one is journal entries, query number two is accounts, that's gonna work perfectly. So when you are subtracting, keep in mind that if journal entries is query number one, if query number two is accounts, that should work. That should remove any account that, you know, that was in query number two that has a matching account in query number one. Even if they gave multiple times, it's removing the entire account from the results. Now in a compound query like this, query number one being journal entries, query number two being accounts, you can set this compound query to be either journal entries, so we'll give you the leftover journal entries from the people who are not marked as do not mail, or you can set this data return type for the compound query to accounts. And instead of showing you the journal entries from last year minus the people that are marked do not mail, it will just show you the accounts that are that had a journal entry from last year minus those that are do not mail. So great question here that I received. How does one determine whether the compound crew results are journal entries or accounts? Before you get to this section there where you choose your your option to either intersect, add, or subtract, and then put in your two queries, just above that, there will be a data return type just like any other query. So you can choose from there if the ultimate results of the compound query are going to be accounts or journal entries regardless of what the two queries are that you use for the compound itself. So you still have control over that. Now the next, the the next thing I wanted to say here is that I put this as yellow and that it should work. I don't see any reason why this shouldn't work. But if you're intersecting accounts with journal entries, it should still work. So in this case, we're finding everybody who was marked or who gave last year or had a journal entry from last year, but are also marked as do not mail. Maybe we, you know, maybe we do something slightly different for those people, as opposed to sending them a a mailing of some sort. This should work. I don't see any reason why you couldn't find regardless if you're going to return journal entries or accounts in the end result, you should be able to intersect, those do not mail accounts with the last year journal entry. Where that becomes a problem, particularly with subtract and with intersect, is when you cannot match the the person. So this example will not work. So remember again, the subtractions and intersections and in especially subtractions require matching information. And in this example, I am trying to find the people who gave last year but didn't yet give this year, maybe to specific funds or to a specific approach or something like that. But what I have is I have journal entries from last year, and I'm trying to compare it and subtract journal entries from this year. Now, there's a real easy explanation as to why this doesn't work. The two queries being used in query number one and query number two are set to journal entries, meaning they are being extremely specific with what those queries return. Journal entries that have a last year date, last year information versus this year's date and this year's information. Because those dates don't match, nothing will be subtracted from this query. If we tried to subtract the journal entries from last year from the journal entries or the journal entries from this year from the journal entries from last year, there's just nothing to match. The system wouldn't be able to remove anything, and what the end result will ultimately be would just be all of the gifts from last year. If you were trying to intersect these the same thing, it would, it would show nothing in in with an intersection. The subtract would only show the last year's because that's query number one. Intersect would show nothing because nothing matches in between. So this is where you need to be careful about your data return types, and this is where compound queries can get very complicated for some folks, and I completely and totally understand why because it's also hard to explain too. So it would be like saying, well, if I, you know, like, think about this from a different perspective. Maybe this analogy will help. Maybe it makes it more confusing, but maybe it hopefully it'll help. Think about this. Let's say you were preparing a dish, and you're preparing a dish that was going to include vegetables and fruits, and you wanted to find the people who want to have some sort of a vegetable. Doesn't matter if it's a carrot. Doesn't matter if it's a, squash. It doesn't matter whatever. And you also want to not include anybody who would also like to have fruit on their plate. Doesn't matter if it's an orange, an apple, a pineapple, whatever. That would be easy. Right? You would say, okay. Only the people who get the the vegetable dishes will get you know, those are the only people we care about. They only want vegetables only. We're not we're not handing out plates to anybody who wants vegetables and fruit because we've removed those people from those. But let's say instead you were comparing exact types of fruit. I wanna find people who like apples and subtract out the people who like oranges. When you get into the to the specifics within within that list, there's apples and oranges don't don't match. They they're both fruit, but they don't match. So the system wouldn't be able to to tell the it wouldn't be able to find the people who want both apples and oranges or subtract the people who like oranges as well as apples from the people who just like apples. That probably got a little bit more confusing but what I'm what I'm trying to illustrate is is that you're coming down to a much more minute and minuscule scale where you're looking at individual journal entries. That's where the system must match exactly date, person, fund, gift, or the received amount. All of that has to match in order for journal entry minus journal entry or journal entry intersecting with journal entry results. That's how that has to work. When it it because journal entries look at a lot more granular, minuscule scale as opposed to the accounts as a whole. Hopefully, that helps. It's a very confusing way to try to explain that. It's not easy for everybody to, to fully grasp, and I completely and totally understand that, but, hopefully, that helped. Most of the time, I'm going to say if you are working from some sort of an of a, if you're working from some sort of a, I wanna find people who gave last year but didn't give this year, the people who gave this year, it would be best if that is at if at least that query is accounts. It's perfect if it's both, if they're both accounts, but it will also be perfect if the people who gave last year are journal entries and the people who gave this year were accounts and you're subtracting the people who gave this year from the people who gave last year. That will be, at least having query number two set as a as an account return type query when you're doing a subtraction is the best rule of thumb that I can give you. Would it be better to create a query that shows gifts from both years and then this could be manipulated in Excel? Not really. Mostly because to manipulate it in Excel, if you if you're really good at Excel, you might be able to program something that would be able to help with that. The problem is is that with that, there's always room to make a mistake there. I would say, especially if you're trying to find people who are giving one year but not the other, I would do that. I would make sure that those people who, you know, who didn't the the I wouldn't I would wanna make sure that the exact people show up in the results first. And then if you do need to do anything manipulative in Excel, it's more for the display and less for the data, if that makes sense. Now here is where I, have an example of journal entries subtracting from journal entries that will work perfectly. So in this example, I have, query number one is set to all of the journal entries from last year, and query number two are all the journal entries that gave to a specific fund. In this example, I put fund a. Well, subtracting that works because there will be some funds that are, you know, that are listed as fund a in last year's giving, and we're subtracting those out from the results. That will show you the the results will be all of the other funds to all, you know, to any of the other gifts that are shown there. So you can subtract journal entries from journal entries as long as there's some way for the system to know that, yeah, they're matching entries here. There are gifts that have fund a marked in last year, and I'm subtracting those. Those will be subtracted out from the results, leaving only the other funds, or only the transactions with the other funds listed. Now what do I want you to remember about compound queries? Well, the number one thing is I just don't be afraid of compound queries. Yeah. There's a ton to take into consideration or to remember about them. But compound queries sometimes are necessary, and they can do, and there's so much more you can do with, like, your mailings or your reporting, especially if you're trying to target certain mailings, to people who meet a very specific criteria. They gave to a specific fund, they haven't given to any other funds. That's a good way of being able to target those people specifically. Compact queries can be extremely helpful in that regard. Reporting can be very helpful, if some people wanted to see that list of those specific people, that gave to a particular fund but didn't give to anything else so that they can take into consideration maybe other things that you might be able to do with that. But the number but the next important thing is that you do have to remember the data return type is going to be super important in the two queries that you are comparing and contrasting. So as I was previously illustrating with those various examples, maybe the most important thing to make compound queries work is the data return type of the two queries that you're comparing against. If they're both accounts, it should always be doing whatever it is that you want it to do, intersect, add, or subtract. If they are journal entries, then you need to make sure that, you know, would is it possible for query number one's journal entries to have entries from query number two? Are there no comparative journal entries to subtract? Then in that case, I might have to do something with accounts instead. So they can be a very very helpful tool. They can be very confusing and they can be very difficult to work with at the beginning. But the more you work with them, the more you understand, oh, okay. Well, if I'm trying to subtract a group of people that do x from group of people that do y, y you know, what would make it work best so that I'm able to subtract these appropriately or intersect them appropriately? If I'm just adding them together, that's that's the one that you would have to worry about the least. But when it comes to adding and subtract or intersecting and subtracting, you know, the more you work with compound queries, the likely it's going to be a little bit more, it's gonna be something that's gonna be become a lot more intuitive to you the more you work with them. Now do remember that with these, with these sessions like this, I also always do an ask the expert. So next Wednesday, there is an ask the expert session that is, you know, that you can sign up for. I will go into a little bit more examples, and sometimes people bring, you know, a specific situation that they work on that, that that they struggle with. You're more than welcome to attend that. Check the community. I I released a blog post yesterday. No. The thirty first on Monday that has the link to go and sign up for those, sessions. So I would definitely recommend that you, take advantage of that and take a look at the ask the expert. A lot more people come in with a lot more questions, a lot more very specific questions that I can then do a little bit of screen sharing with. And those are those are sessions that I know have helped out a lot of people in the past. So if you have more questions, even though we do still have time for some questions here before I get into the, into these last few slides, you know, there may be some things that I can do a little bit more like screen sharing on with questions next week as well. So, if there are any other questions, go ahead and start typing them out. In just a moment, I'm going to move on to a couple of other kind of housekeeping slides here. But, you know, if you still have some questions, please feel free to, send them over. Alright. So as I wait for those to come in, there are some additional resources that I always like to advertise. Blackbaud University, this is a a great, way for you to get into the eTapStreet curriculum. Should be available to most of you. You'll be able to go through, some on demand kind of basics as well as, if you have a learn more subscription, you can get into more instructor led courses as well. Those are a great tool for you to, be able to take advantage of. Of course, we have customer success and knowledge base. This is a great place for you to get step by step instructions. There are several knowledge base articles that talk about compound queries, some of them very specifically. Like, if you wanted to send a mailing a clean mailing list, that's already existing. And there are several others that talk about, like, you know, how to find people who gave last year but not yet this year or who gave, this year but didn't give last year. There are other, step by step, articles in there as well. The Blackbaud community is another great place for you to go to. That is a great way for you to connect with peers. Ask them, you know, what some of the things that they are doing with the tapestry. It's a great way to just kinda build a little bit of a network with other users of the same, you know, of of the same products that you use. Real quick, Alex asked how, oh, I'm sorry. Tiffany asked how you can how she could register for the for the ask the expert. I'm going to put that in the chat bar. So that link should show up now under chat, and that should have not just the ask the expert coming up on the ninth, but other sessions that are coming up through the rest of April and into May. Alex asked, can you have more than one administrator on eTapestry? We've been having issues having to readd me as add multiple times to obtain access to things like Blackbaud you and more. Yeah. You should be able to of course, you can have as many admins on eTapestry as you'd like. Technically, the same thing, can be done with your Blackbaud ID as well. It would just be a matter of making sure that you get, marked as a, as a Blackbaud, you know, that you get invited as a Blackbaud user, that you're marked as a as an admin, and then the same thing inside of the Tapestry. So, yes, you can have multiple admins. So there are a couple of other, ways that you can engage not only with peers, but with Blackbaud too. The Blackbaud champions is a, it's a program that we have that not only helps you spread the word helps us spread the word about Blackbaud products and services, but you also have the opportunity to feed to provide feedback to teams within Blackbaud. There are professional development opportunities that you can participate in. There's even an a rewards program that you can, take advantage of in the champions, in in the champions program. In a way, it's kind of like, community plus, if you will. It's a great way to network, but you're also networking with folks here at Blackbaud. You know, you're also getting, some tips and tricks, some some, you know, like I said, those professional development opportunities, particularly in the fundraising space that that's always helpful. But it would be something that if you are interested in, let me know. I will be more than happy to get the team in contact with you on. The same goes with the reference program. Now the reference program is slightly different. This is where you would share experience with, people who are potentially considering purchasing a Blackbaud product. In this case, it'd be Tapestry. You have total control over how often you take a call. You can you can say I can give, you know, I can give up to one time per week, or I can do one time per quarter or one time per month or whatever you would like to do. That doesn't necessarily mean that we will always take advantage of that. Of course, it's it's going to be dependent on people who are asking for, you know, people to reach out to. But it is something that, we do value a great deal because there's nothing better for a user than to talk to other users. And that goes, you know, that whether you're a champion or you're in community or you are a reference where people are asking very specific questions about, you know, some of the things that you've done with eTapestry. It's it's a really important thing for people to be able to, to to get and to understand. So if you're interested in that, please let me know in the chat or the q and a. The third thing that we have here is the spotlight your success. If you've been successful doing something with eTapestry, no matter how big or small it is, let us know. And this can either become a, a a blog post that we have you write for the community or we bring you into a session, you know, and you help present a webinar, likely with me or, you know, we we have you, you know, speak to, or we speak to you, like, on a podcast or something like that where we talk about that success story. If any of these things sound like something that you would be interested in doing, please let me know in chat, and I will be, you know, I would be happy to get the team in contact with you. And, you know, some of these programs, particularly like the champions, you don't really I mean, even with the references, you don't have to be an expert with eTapestry. What this might do is it may turn you into a better user of eTapestry eTapestry or a power user of eTapestry where you get more and more opportunity to interact with, Blackbaud and with eTapestry itself. So if any and these are all, you know, none of these cost anything to be a part of. So if you are at all interested, please let me know, and I'll be happy to get you in contact with that team. Alright. So we've got a few minutes left here. I'm just going back through the q and a just to make sure that I got everybody's. Questions. I think I did. So last call for any questions. Yes. So, one thing I did mention at the very beginning, Wilmarie, was that, this is recorded, so you are able to go back and re, rewatch that. You'll get a you'll get an email, in about twenty four hours with that link, but you should also be able to use the link that you used when you joined today. So, that should take you into the recording. Alright. I think I've got all the questions for now. Thank you for attending. I know this is a difficult topic. I definitely wanted to talk at least a little bit on a higher level about, compound queries and some of the tips and tricks around that. I look forward to anybody who can attend next week at the Ask the Expert. I will answer again as many questions as I can. The Ask the Expert link is in the chat window, not in the Q and A. So if you are interested in joining that, you can use the link there to find it. And, there are also some other webinars coming up later this month and going into May as well that, I think you'll be, pretty interested in. So, look forward to seeing you here next week and, I'm glad that, you were able to join today. I'm glad that I was able to answer quite a few questions. I know this is a difficult topic, but I think that sometimes you have to kind of just crack the surface and then really kind of try to dig in a little bit deeper with compound queries because they can be so, they can be they can be quite confusing at times, until you get really used to them. But I hope everybody has a great rest of their day. I hope you have a great rest of your week, and I look forward to talking to you again soon.