Video: Ask the Expert About the Most Common Queries in eTapestry | Duration: 3660s | Summary: Ask the Expert About the Most Common Queries in eTapestry | Chapters: Welcome and Introduction (5.2799997s), Welcoming Participants (67.205s), Soft Credits Overview (160.235s), Understanding Soft Credits (286.665s), Soft Credits Explained (737.34503s), Advanced Query Techniques (1566.8049s), Advanced Query Techniques (2184.095s), Query vs Report (2830.875s), Conclusion and Resources (3039.15s)
Transcript for "Ask the Expert About the Most Common Queries in eTapestry":
Hello, everybody. Welcome to this week's Ask the Experts session. Primarily going to be focusing on, queries, like we had talked about last week. But I did also have a few, or one thing in particular I did wanna talk a little bit more about that, kept coming up as a question during the course of, last week's query session that I wanna definitely, make sure that I, that I talk about here. But, most of you know me. I am Jeff Arbuckle. I am, as I put here on the slide, the etap guy. Happy Wednesday. We are, right here on hump day. It's all downhill from here. Right? It's well, hopefully, we'll be easing ourselves into what is very likely going to be a very hot week, rest of the week weekend here in most of the, at least on the Eastern side of this country. Hello, Dolan. Pleasure to see you as always. Yes, Lindsay. The eTapestry guy. Yes. I'm, yep. That is that's that's also an internal nickname that I have here at Blackbaud as well. So yes. Yes. People checking in. Yeah. Addie, I have a feeling, they they, you know, they started using this term called a heat dome. Don't ask me where that came up from or when that started to be, to become a thing, but, seems like the entire country is going to be under one here very soon here. Yeah, Jasmine. Certainly, Ohio. Yep. You and I here in Indiana, you and I are gonna be, sweating it out, I'm sure, this, this weekend. Alright. So just letting some people get in here. Happy as always to see people saying hello. No. No, George. You're not late. We're just getting started here. Just wanting to make sure, that, that we are getting things, you know, getting everybody settled in before I dive into any kind of content. Yeah. So it looks like, yeah, Canada had a, heat adviser. I think now it's moving south. So, yep, I think that's where we're getting that from. And Rebecca from Alabama. I'm sure it's been hot all summer. If I if I know anything about the South, it is, even hotter than it is here in Indiana. So yes. Welcome everybody. I'm glad everybody is getting settled in and joined. So let me go ahead and pull up my database here. You should be seeing my eTapestry database now. So one thing that I do wanna make sure that I call out, there are some controls for you to, zoom in a little bit or, make it full screen on your screen. So, I'm hoping that, you know, most of you will, will be able to very easily and clearly see, some of what I'm going to be talking about here. But, while people were getting some, questions put together for me, anything that comes to mind here before I get started, please go ahead and put into the chat. But, one thing I will also remind everybody, this is being recorded. I'm not saying that for you to be on your best behavior. You can say whatever you want in the chat. I'm fine with that. But, I'm saying that because a lot of people always ask, you know, can I watch this later? Is this something that will be recorded that we can go back to? Absolutely. So, always know that just like any other, webinar that we do, here at Blackbaud, the, about twenty four hours after the conclusion of today's session, you will receive an email thanking you for attending and giving you that link to make sure that you can get into the recording. A little bit later, it will also show up on our resources page, which is one of the tabs I have here that I'm going to, touch upon, before we close out today's session as well. So, let's, let's talk about a few things here. Now one of the things that did come up, The question about soft credits came up last week a few times from a couple of different scenarios. First of all, people asked, you know, what is a soft credit? For those of you who maybe had to leave a little early or weren't there in last week's session. The the question came up about, mostly about, like, how to query on soft credits, but also, what soft credits are also came up. So soft credits, simply put, is a way to credit somebody who didn't actually give physical dollars. So, like, let's say, for example, I made a donation, but, let's say Amber, who's in our chat here, let's say that she was the one who talked to me about, like, oh, I support this really great organization. You know, they they're a shelter for for homeless cats or something like that. And I say, you know what? I'll send $50 over to help them buy a bag of food or something for all the for all the kitties. And, what they could do or what the organization can do is as they put in my information so, like, let's say that I'm already, put in as a new donor, they come in here to the journal, They create a gift for me. And as they fill out the gift, they can come over here under this tribute, soft credit, matching gift relationships. It's the third little panel here on the side. They can then add in that somebody was responsible for maybe influencing me to make a donation. That person didn't make a specific donation, or not a monetary one, a physical one, but you wanna credit that person for that, you know, for that influence that they had over that gift. So the the idea there is is that it gives you the ability to search for somebody. Let me see if I can find yeah. I'll just put Bob here for an example. You can even provide, you know, how much of a soft credit. So the idea is is that you could potentially later pull a report to say, Bob Smith not only gave $3,000 last year, but he also is self credited for $200 from friends of his or people that he knows or or, colleagues of his also making a donation. These are really good things to do with donor advised funds where you have, you know, maybe I'm making a donation through a donor advised fund. The donor advised fund is the per is the entity, I guess, would be the right word, the entity for the actual physical donation that you received. But the donor advised fund is doing that on orders from me. So you would be able to credit me still as an individual even if you are placing that gift, that physical gift, into the donor advised fund account at that point. So it's just a way for you to still be able to say here is the, you know, here's the influence that somebody has or here's the total, the total concept of what they do for us, the physical money that they give and the and what their sphere of influence has also provided us. It should not be something that is considered a physical dollar amount. It should not be something that would be tax credited, but it would just be something for internal purposes to see, you know, what that relationship really is all about. And, yes, Cindy, you you do have a good point there. The soft credit from, like, influence from a board member or just any other person that might be donating to you and has a lot of pull. But, yes, it is, you know, it would be something at that point to say, okay. Well, the donor advised fund is just an entity. It's very similar to how, like, a business account would be entered into the database. But, yes, if you want to steward that, if you want to have a little bit more, opportunity to speak directly to that person or to the person behind the donor advised fund. One thing you could certainly do is within queries, be able to go into queries. I'm gonna go into manage queries. I'm gonna click on my base category just because it's the first one on the list. And when you're creating a new query for that, what you would be able to do here is, in the, down here in the criteria section, you can say, okay. Well, I wanna find all of the, gifts from last year, And all of the types that fall in will be, like, the recurring gifts, a payment, a gift, and the soft credit without hard link would pull those soft credits without necessarily pulling in who that, you know, without necessarily pulling in who the, hard link is. You're already kind of pulling in gifts, so you may already be doing that. But you could also, include various other pieces of criteria like, you know, I talked about account type. If you have the individual marked as individual and donor advised funds marked as organization, third party, donor, donor advised funds, however you have that mark, you would be able to specifically find those accounts that you want to reach out to and talk to. This could, with this soft credit without hard link, potentially pull in that person who would have the influence, that would have the, the the person that you are trying to steward into making a donation through that, through that donor advised fund. Yes. Now, Elena, you are right there. They are going to still, show up as lapsed if you do give them a, soft credit because most of the time when you're doing a lapsed donor report, you are looking primarily at either the journal entry types of gift, recurring gift and payment, or you are using the commonly used field of the individual transaction received. That would not take into consideration, soft credits. One thing you could consider is replace the individual transaction received with the journal entry types so that you can pull in that soft credit. You can also use under amounts. You can also use individual let's see. Well, there's individual transaction soft credit, but there should is there also? No. Actually, take that back. Instead of using the individual transaction received, I would use this journal entry types and then make sure that you're selecting one of these, soft credit or soft credit without hard link options there. Okay? That would help you be able to pull in those lapsed people as well. And, Lindsay, that's an excellent, point there that you that you make. This soft crediting this is soft credits in general are great for peer to peer fundraising, for any other kind of scenario where you have somebody who is going to be collecting money from people. You say you work in a, ad in education. So you have a student that gets 10 people to to make a donation or they're, like, buying those chocolate bars or whatever. You're taking their information. You have who gave that money. So, yes, you could say, okay. Well, the student brought in this or you could say the individuals brought in this money and the student is soft credited or or however that you're entering that in. So yes. That is an excellent way of of recording that information so that either it ties back to the student while all well, it would tie back to the student while also collecting the donor information from the people who the student collected money from. Yeah. It's a great great option there. One other thing I wanted to talk about real quick before I, really kinda dig into some of these questions that have already, come up here. And, yes, Joanne. That's, yes. So you, just to kinda go off that soft credit conversation, we use the soft credit to track the membership paid to their local branches. The local branches then pay us for the organization membership. Exactly. So yes. So the the, the branches are the ones handing over the physical cash, but then you can also soft credit that membership paid to those local branches by the individuals. That's a that's another great example of of how that's used. The most common used, circumstance, at least here in The United States, is when you receive donations from United Way or some sort of third party, collector like the United Way, you know, you're receiving a big check from that third party and they're listing all of the people and the individuals that have made that donation. The check goes into the United Way account, and you're putting the soft credits into the individual's accounts. So that's an excellent, way of recording that type of information so that you're not only recording the dollars that have been physically received, but you're also recording the information from the individuals who made those donations. K? So, yeah, a couple of, little things I wanted to talk about that wasn't as well illustrated in the slides that I had last week. First and foremost, by default, you're going to see the search by name, and this is something that you can certainly use the, search option if you know what the name of the of the query is that you're looking for or if you know enough of the title that you can find it. But I almost always switch this to search by category. I'm an old timer when it comes to eTapestry. I'm used to seeing the two drop down menus. So if you switch to search by category, then you can select the exact, queries, the exact, categories, whatever it is that you're wanting to choose. So that is one thing I did wanna make sure that people were aware of because it probably did look a little bit different in the slides compared to what the reality, was when you're creating a brand new, a a brand new, query. The other thing I wanted to talk about were these results. Almost always, I'm going to say choose either the accounts or journal entries, but you'll notice there are a bunch of other options here. All household accounts will pull specifically, all the households into the results of the query or I'm sorry, all the household members, that based on the results of the query. So like let's say, you said give me everybody who donated last year. Well, if everything only went into the head of households account, this all household accounts would still pull all of the other household accounts as well even if they didn't make that donation in the, in the, date range that you put in there. There's head of household accounts, which will only pull the head of household, even if the member was the one who made the donation in that time frame. The main reason why I don't really talk about these household criteria, and this is something that I will talk a little bit about in a couple of weeks when I do the, reports session. These data return types were created before our reports. Were a little bit more able to do grouping. And what I mean by that was was that we wanted the ability to be to say, okay. Well, we're gonna pull the head of household for you so that you're only sending one mailing. Well, that was a very, very early version of eTapestry. Later versions of eTapestry, even before I started working here, already had grouping options within reports and within communications that really took out the need for us to have anything like head of household grouping. It was very, very rare that all household accounts or all or these journal entry household options were used. And it's not something that that I ever really recommend people do in the query side and instead do in the report side. So I wanted to make sure that it was clear that, you know, we do have these other options, like the related accounts, matching gift accounts, that all have something to do with relationships and aren't very commonly used, nor are some of them even something that I would recommend using only because we have better ways of grouping that information and getting that information displayed later in a report or a communication. And, yes, Cindy. So basically, grouping reports, not necessarily queries. Keep it simple and use accounts or journal entries and queries. Absolutely. I say I think you really had a perfect, a perfect little idiom there. Keep it simple. That is the number one thing I would like to, like to try to impart on people whenever I talk to them about queries. Queries are the easiest thing to overthink and oftentimes don't need to be as difficult as they are. So, yes, when we're talking about grouping, a lot of people will take into consideration households because they use them extensively in their database, but they don't have to be as complicated to the point where you necessarily need to stray too far away from grouping by accounts or I'm sorry. Displaying accounts or displaying journal entries. And that way, you know, we can worry about how it's grouped and how that information is going to be displayed in the report, which is what the which is what the purpose of a report is, is to settle the way that this information is going to look for you once you export it from eTapestry. Alright. So I wanted to kinda go over those because if anybody was kind of building any queries or doing anything and they were coming into this drop down menu, they might say, Jeff didn't talk about these other, you know, data return types. It's because I very rarely ever talk about the other data return types, outside of accounts and journal entries. So I just wanted to make sure that I talked about that as well. Okay. So let me slide up here a little bit earlier. Deborah was saying, I'm hoping you can help me alleviate needing to do 12 queries to get my final answer, please. I've, only been using eTapestry for three months. So yeah, Deborah. What are, so some of this might come down to exactly what it is that you're trying to to query on. A couple of the things that there are a couple of things to take into consideration. Like I said, there are ways that you can make some queries a little bit easier, a little bit e a little bit more direct in what you're wanting to get. There are ways that you can, instead of saying, okay. Well, I'm not gonna pull journal entry date here because down here I have this set up as, you know, one one twenty twenty four to 12/31/2024. I always wanna look at last year. You don't necessarily have to pull that data or that, criteria. Instead, we do have a way to say, okay. Well, we have this category called constituent journal entry date, and you could use the starting query of last year. On January 1 every year, it will always say, okay. Last year is now 2024 or 2025 or whatever. So there are certain things there that might be able to help, alleviate that. But when, let's see here. So Deborah says, unfortunately, a lot of the queries were set up before me, and I want to simplify them. So one of the things, Deborah, that I would probably recommend doing to try to get this to be a little bit more, a little bit more direct and simple, I would recommend compiling, like okay. This is what we ultimately want to see in a report. Understanding what you want the end result to be and what you want it to show. And what I would say is compile that information into, what I would say is reach out to the customersuccess@blackcloud.com. Tell them that you attended the session and that I recommended that, that you reach out to them to maybe get a little bit of advice or a little bit of information about how to get to a much more direct. And, you know, this is exactly what I would like to see and how we want to do this. You know, you can explain that, you know, you've got all of these other queries that are kind of built to do, you know, to do this. You wanna simplify it. They will probably confer with me on that, and, we'll be more than happy to try to figure out a way that we can help you, get that information. I think it's probably I think it's gonna come down to, can we make it simple simpler? Possibly. Depending on what the end result is, sometimes it does get a little bit more complicated. But I think it would be good for us to kinda get a a totality of what the, of what the need is. And I think that would be a good, good way to go as well. So I'm glad to see that the fur that the tip there as far as, like, you know, possibly having, you know, starting queries be something slightly different might help. But, yeah, if you continue to see it's like, okay. Well, this is getting really convoluted or I feel like I can maybe condense some of the information that might have been you know, I'm looking at 12 queries. Four of these things could be handled inside one query. That's where I would say, you know, certainly reaching out to the customer success inbox. That team there, is going to be the customer success manager for most of your, of the people listening to the session. So I would start there and maybe see if we have some advice or something that we might be able to recommend as far as some options that that will make that a little bit easier or trim down the number of those queries. I think that, you know, when you're talking about, like, queries that are built upon other queries that need to be constantly edited, I think the big question comes down to is, okay, where can we find possibilities to streamline that? And instead of you know, maybe we still need multiple queries, but maybe we don't need 12 queries. That would be my, that would be my goal if I were looking at just your database or if we were just having the that conversation, separately. So yeah. Okay. So Cindy asked here, lapsed owners that include households and soft credits. Cumulative giving with households and soft credits who donate to a particular funds, but not all funds, run a report on median gift for all of the donors in a time frame, run same report by segments on approach. So okay. So a couple of things here, Cindy. One, lapsed donors that include households and soft credits. So that is where I was talking about. It's like, okay. Well, what we would probably wanna do is we would want to do journal entry types as, as one of your pieces of criteria, as well as the let's see here. Let me pull up here the journal entry date with the date range. So you would basically be creating this query twice. So let's say you are creating first the the people who gave last year. Right? Then, you would do this a second time where you would then have this be the twenty twenty five people, and you would save that. So this would be you would basically be doing two queries with two different date ranges the exact same way. Now your data return type must be accounts so that it will properly, so it'll probably or properly subtract out the people who were lapsed at that point. Your starting criteria would be to base all constituents as well. Okay? Then you would do this exact same thing a second time, change the date range, and then what you would do is you would ultimately create a compound query, which I believe so in the compound query, you would do the subtraction. Query number one would be the queries of all the people who gave before the first date range, whether it's 2024 or 2025, whatever the whatever the lapsed, whatever time frame you want the lapsed to be from, that's going to be query number one. And query number two or I'm sorry. Query number one will be the people before whatever time frame you want that to be. So in this case, if I wanted to find the people who lapsed in 2024, my query number one is going to be the donors who were before 2024. Query number two is going to be the donors in 2024. When I subtract that, then what you would have is the people who were lapsed. So the people who did not give in the more recent time frame, but they gave before. So that would be and, you know, like I said, the the query itself, instead of using individual transaction received as your criteria with the, journal entry date, you would use journal entry types, and you would make sure to include the, soft credit option there. Yeah. I would still stick with, the data return type in the is account in the compound query as well. Okay? Only because, again, in the report itself now this is a little bit of a teaser for, two weeks from now. In the report itself, there is an option to include what we call summary fields, and you would be able to show what the last received date and last received amounts were. So you would still be able to pull that information even if you have accounts as your return type in the query. Cumulative giving with households and soft credit. So, again, with the households, this is also a a little bit of a teaser for two weeks from now. It's this is in the report where you would say group by and you would have household collapse groups. And that would squish everything with the head of household being the person displayed. Now with the cumulative giving so we're going to do something here where, let me get back into a new query here. So let's say you wanted to find all the people who cumulatively did something, within the last year or whatever. You would start with a query that would be like all the donors. So it would basically be the same query that you were using with one exception. So, like, here in this case, we have all of these donors that have, recurring gift, gift, payment, soft credit without hard link. We have all of these selected, but the only difference here is we want these are going to be journal entry. So it's the similar thing to what you were doing with the lapsed, except this time it's going to be journal entries. So what we want is we specifically want the journal entries from this date range. Okay? Once you have that saved and you select that as your starting query, for cumulative amounts, there is the cumulative received and soft credited. And then you would just set that to be whatever you want, 1,500, 2,500, whatever the amount is that you want that to be. So very similar situation with two exceptions. Number one, your starting query is going to be that, gave in 2024 just like with the lapsed or whatever date range you were wanting, making sure that it's journal entry return type because you wanna pull those journal entries. You wanna select that for the starting query in this query and then pull oh, I'm sorry. This says household. Hang on a second. Sorry. I don't didn't mean to pull this. Pulled the wrong one here. Cumulative received and soft credited. You would want this to be the greater than or equal to 2,500, whatever. Then, in the report, you would group by household at that point. Although, actually, no. Take that back. Take that out. I'm sorry. I'm sorry. I did select the right one. You do want the cumulative received and soft credit in this situation because you wanna make sure that the household makes it to 2,500. And then you would still be able to collapse or you would still be able to group in the report by household, collapse it, and then the household's grand total would appear at that point. Data return type in this situation would be journal entries for this one. So journal entries for the first query that finds all of the people who had, those journal entry types in '20 in whatever year, 2024, 2025, whatever it is that you're looking at with the date range. And then journal entries here for this household cumulative received and soft credited. And then whatever amount that you want the household to meet. Now as far as the reports go in this situation, so this is gonna be another little bit of a tease. I'll talk a little bit more about in the in the, in the next couple of weeks, in the next session. So one thing you could do is you could say, okay. Well, I wanna find the funds, and I want this to to you know, you want fund or approach or whatever, you can then group by fund. You can either collapse groups or show group totals. One of the things that you can do with the received amount, if you were pulling all of the gift information from a query, is you do have when you click on these little this little menu button there, you do have the aggregates where you can do, like, an average. Now average is gonna be about as close as we can get to what would be, like, the median. Average might help in a lot of ways, but if you were looking for something a little bit more specific, you might have to just export the raw data, grouped by the fund and then create, like, a pivot table or something or some sort of formula in the Excel file that you download. I would probably I would probably recommend playing around with that a little bit first, and then we'll we'll kinda take it from there. Alright. Just going back up here through some of these other questions that were asked. Just Okay. There's Cindy. Ah, yes. So great question here. Please explain how to use this criteria in queries. First slash last journal entry. Excellent question. So this is found under journal fields. Nope. I lied. It's not found under journal fields. It is found under dates. Let's see here. And I'm not even in a query. I'm in a report. Sorry about that. Okay. We'll just come into this query here. Under dates, we see this first last journal entry. Now how is this used? So let's say you wanted to find what somebody's last x number of entries that they had from, a day range. Okay? What their gifts were from the start of 2024 to today. Okay? You can choose this you can have this set up to where it'll say individual transaction received, dollar or more, journal entry date, set up, you know, whatever date range you want. And when you use the first last journal entry, by default it's going to say the first one entry, which means what was their first entry period in that date range. Okay? But then you can say, okay. Well, I wanna see the last or I wanna see the first three that they made in this time frame, or I want to look at the, last three. Now there's also second, third, fourth, and fifth. So you could say, okay. Instead of saying the first one, I wanna know what their second gift was in this time frame. And this criteria would now if they don't have two gifts in that time frame, they won't show up. It will only show the people who had a second gift if it was used this way. Now if you said I wanna see the first five gifts in this time frame, well, if somebody doesn't have five gifts, it should still show what gifts they did have and display that so that you can get that into a report. But, the last is mostly I just wanna see what their last gift was. You could say what their last two. You do not necessarily have to use a date range. You could open this up totally to say, okay. Inside the database as a as a whole, what was everybody's last gift that they made? And it would display that, you would want the data return type to be journal entry so you can actually see the journal entry information, and then you would also be able to report on more information from that. So, yes, the first last journal entry can be used in conjunction with other criteria. It is not like the cumulative fields where you have to have something as a starting query. It should just be able you can include that and just say you should be able to just say, okay. Give me the last gift in this case. What was the last received amount somebody, you know, made it, gave to or whatever or what? And then you would be able to go to the report and use that to pull more information from the account, from the journal entry, whatever the case may be. Does this only apply to gifts? No. You can use it for any entry. I mean, that's why it says first last journal entry as opposed to gift received or whatever. So you could say if you had it listed like this where it was the only piece of criteria, it will show you what the last journal entry is from anybody's account, whether it's a contact, a note, a gift, a pledge, or whatever. You can be more specific and say, I wanted to show me the last let me go back to commonly used fields. The last contact entry from an account. So you can apply it to whatever you would like for it to apply to. So if you're using contact entries more extensively, that's something else that I have a topic coming up later this year about. I love using contact entries because they are more than just recording information about contacting your donors. It can be used for all sorts of different stuff. You know, you could potentially use that, as a piece of criteria. So it does not necessarily have to be gifts. It can be any type of journal entry. Hopefully, that helped out there. So Amber has a good question here also. Sometimes I'll run a query and select my criteria and date range for the year, and it comes back with fifteen years worth of history or it comes back with zero entries. Why? So there could be a couple of reasons for that. Number one, why it may be coming back with fifteen years worth of history may have to do with this criteria matching. Now one of I did bring this up in the last, in the session last week where match all of my criteria is like saying and in between each piece of criteria that you select. This has to be a contact and it has to be their last contact. Matching or so match at least one criteria puts or in between these statements. This either needs to be a contact entry that I wanna see in the results or it is a, the last entry of theirs. Most of the time you're going to leave that as all. There are certain circumstances where you might wanna say at least one criteria, but most of the time you're probably leaving that alone or you're not you're not really sure what the difference is between, between that. But it could have a play in how you are, what your results are ultimately going to be here. So one of the things that could also be is if you're coming in here and you're saying, I wanna see everybody who made a donation of at least $1, last year. This piece of criteria would match all criteria should pull exactly the gifts in the date range that you're looking for. But if you are doing something like, here's my entry date range and I'm selecting cumulative received instead, what this does is something very strange. It looks at any account that has a journal entry in the date range and then pulls all of their journal entries going back potentially fifteen years as is the the case in your situation here. So it could be a situation like that that your that could be mismatching criteria that ultimately does not do what you might think it does. So, like, if you're looking for actual transactions that gave in this date range, you want match all criteria and you want individual transaction received with the greater than or equal to a dollar. If you are not seeing any results, there could be a couple of reasons why match all of my criteria and you're starting to compound a bunch of different criteria might ultimately lead to zero results. One of the things that you might be doing is saying, okay. Match all of my criteria and I wanna find anybody who made a gift at some point. Doesn't matter when, just at some point. And I also want to see contact entries. Well, match all criteria. Contact entries don't have received amount, so this would give me zero results. So there could be certain things like that. I think it kinda comes down to what the exact criteria that you are selecting or what you're putting into the query, but there are things that are usually fairly easy to, they're fairly easy to fix. It's just a matter of figuring out what it is that's been put into the query that's causing either too many or not enough results. Normally when you get into a situation like that, you should be able to get some some assistance either from the knowledge base or from from our support team if you go through the chat. More often than not, there are going to be some sort of, knowledge based solution that gives you the steps for almost any type of query that you're looking for. I'm gonna talk a little bit more about that here in just a moment too. Yeah. So you leave that to all most of the time. Yeah. So with all, there could be like I said, you know, with all and this is something I mentioned last week. All of my criteria, the more criteria you select, the less and less and less your results will be. For at least one criteria, the more you select, the more and more and more results you will get. So, if you're using match all criteria and you are selecting a whole bunch of different criteria, which aren't always necessary in queries. Sometimes when it comes to queries, what you wanna do is you wanna say, okay. They just have to meet that they gave something last year. You know? So they have individual transaction received and this journal entry date. They just had to give something. I don't need to put anything else into this, query because this will give me the results I'm looking for. I can then go to reports and say, okay. Now give me the name, the address information, contact information. Maybe I wanna throw some attributes in there. Maybe I wanna display not only what they gave, but to on what date and what fund and what approach or what have you. So the report does a little bit more as you are plucking more and more, report columns to display. Then queries need all of that stuff to be included. So the report, yes, include whatever it is you want to see. Queries just need to know what's the common denominator that finds all of these people that you're looking for. And so, normally, criteria has much fewer things to choose from, or that are needed to be chosen to the to get results. Whereas, reports, typically you want to fill up whatever columns it is that you do want to see. But, yeah, I mean, that's the main difference between query and report is that queries just goes out and finds information based on search terms. It's it's you know, think of it kinda almost like Google searches. If you don't put in if you put in just one word into a Google search, you're gonna get a whole bunch of results. But if you put in a paragraph into the Google search, you may not find all the different opportunities or all the different options surfaced up to you, the right way. It might become more difficult to find the information you're looking for. So, so when you say, so yeah. Here's another great question here as well. How would you build a query to capture amount received and gifts in kind value? So one thing that I would do is okay. Again, you might use the journal entry date. What I would do in this case is use transaction gift type. And then you can say, okay. I want I want credit card. I want cash. I want check. And I wanna find all of the entries that have gift in kind. More likely than not, you're not putting a dollar amount into a in kind gift entry in you know, when you're creating that gift. So doing it this way will find not only the people who have cash, credit card, check amounts, but also pull in those gift in kinds. And then in the report, you would be able to pull, from the oh, let's see here. Where's the field? Gift type fields. You would be able to say gift in kind cash value, and you can include that as a column. Alright. So we just have a few minutes left here. A couple of things I did want to, discuss also is when you come into the knowledge base oh, it's making me sign up. I was gonna sign in again. Okay. Yes. Yes. Yes. Apparently, I was making it wait too long and they got mad at me. When you come into the, when you come into knowledge base like this, you're going to usually see this screen. Now knowledge base can be found by going into the question mark icon. Knowledge base is listed fourth in there. Help will take you into the help center where you can find the topics. You can also, you know, find some information from the customer success side of things. You can also search for relevant topics and so forth. But if you actually go to the knowledge base, you can say you can say, okay, I want to find a lapsed donor query and for the product, you should just be able to put in ETA. You'll find eTapestry. And when you submit, how can I find donors that gave in one date range but didn't give in the other date range? The very first response here. When you click on that, it will give you all of the steps that you need. So, you know, you can use this to search for query steps to find, you know, how do I pull information about gift and kind value? Should be something in there. The knowledge base for eTapestry is rather robust. It's been around for a long time, so you should be able to find all sorts of different topics in there as well. One other thing, and I'm gonna link this in our chat, All of, so I've got a bunch of past content here. I'm putting that into the chat right now, the link to this page. That has some past, eTapestry webinar stuff. I have some information about, like, standard reports. That's a good one if you didn't watch that a couple of months ago. That's a good session to get a little bit more analytical type of information. I also have, information about, like, compound queries, and then there's a little bit of an on demand section as well. So I would certainly recommend that you check those out as well because these are, these are past webinars, past sessions that I've done. Bookmark that. If you ever miss any of the sessions, that are scheduled on a monthly basis. Let me, get there. On this page, if you ever miss any of these sessions that come along here, these will ultimately, eventually end up on the other page there. So, you know, definitely the the page that I linked in the chat, definitely recommend that you bookmark that, you share that with other folks that might be, looking for some additional information. A little bit it goes a little bit, you know, like a couple of steps further from training. Whereas training gives you, like, kind of that basic, like, level understanding of how things, work inside of eTapestry. This kind of goes into more application use like, okay. Here are certain circumstances or here are certain things that you might want to take a look at. Definitely recommend that you, make sure that you have that link available, to you that you can take advantage of. That will take you to this page here. Beyond that, let me step forward. Of course, we have the Blackbaud University and customer support Blackbaud University being our training, section. That can also, that should also be able to be, linked from eTapestry either in the question mark icon or there should be, like, a little quick links, window on the home page, like a little tile. That should take you to Blackbaud University as well. Customer support, get that get to that through the question mark icon as well to, chat now with support. You should be able to, either get some answers from the chatbot or be able to ask for a member of the team to help out as best as possible. We talked a little bit about, the knowledge base there. I would definitely recommend that you take advantage of that as well. That should be let me type in the You should be able to get to that by going to kb.blackbaud.com. But you can also access that through that little question mark icon inside of eTapestry. Then, of course, the Blackbaud community, That as long as you're able to log in to blackbaud.com, you'd be able to get to the community. That's a great place to share ideas, ask questions, kind of connect with fellow users. And I keep saying this, and I do mean it. At some point, probably later in the summer or into the fall, expect some blog posts to come from me there as well. I post the stuff in the past. Just kind of some informational stuff and stuff to help you with, little things. You know, little things that a lot of people do a lot of, and provide you, some, direction and some, places where you can get resources on that. So I would definitely recommend that as well that you get a little bit active in there. Then, we have these sessions or we do have these programs as well. If you're interested in any of these at some point in the future, please feel free to let me know in one of these sessions. Blackbaud champions is a great program to get into. Not only do you get the opportunity to talk about Blackbaud products and services, you can provide feedback directly to the Blackbaud team, that's involved there as well. You can participate in professional development opportunities. There's even, like, a little reward program inside there as well. The reference program, if you, you know, neither one of the champions or the reference program do you necessarily need to be an expert in eTapestry. By no means do we look for anything like that, you know, in these programs because it is meant to kind of bolster your knowledge and and to get a little bit a little bit wider thinking or a little bit wider idea around how you might be able to use your program. But the reference program, is definitely, something that you can take advantage of as well. We that's when we have prospects that are looking to purchase eTapestry or another Blackbaud product like Blackbaud Merchant Services, they wanna ask questions about this before they, sign on. We're always looking for references who would be willing to talk about some of the successes that they've had or some of the things that they've been able to do with that. If you're interested in that as well, please feel free to let me know. As far as, the spotlight your success, that might be a situation where if you get really proficient in a particular area and you would like to, you know, share that success or talk, come on to a webinar and and, co host that with me to talk about what it is that you have done, by all means, that would be fantastic. I would look forward to, you know, having one of these co hosted by people who are actually doing some neat things in the database. A few years ago, I, we did have a couple of sessions like that with, an organization that was really doing a lot of really cool stuff with eTapestry. But if you ever get into, that sort of, realm or if you want to present something that you have been having a great deal of success with, be more than happy to, share the spotlight with you. And either by way of writing a blog about that or having you on for a webinar, whatever the case may be. Yes. So to confirm once again, this, training is, this session is being recorded. So about, about this time tomorrow, you should see an email from Goldcast or from, Blackbaud saying, you know, thank you for attending. Here is the link to access the the recording, and then you'll be able to review this. You'll also be able to, you know, pause it and, you know, kind of pick it apart, rewind, whatever the case may be. So alright. So I think we are at about the end here for this week. Now, in two weeks, I will be doing the, session about reporting, with, you know, five, I think I called it something very similar, five reports every day eTapestry database needs. It's really kinda more techniques than that, but I will be getting into some stuff that I also kind of previewed here a little bit today and some of the questions that were answered. So, definitely recommend, definitely recommend that as a kind of second part to this session, or to last week's session, really. And I look forward to seeing you there. I hope you have a great rest of your week. I hope you have a great weekend ahead, and I look forward to talking to you again soon.