Video: Reports Everyone Should Know How to Create in eTapestry | Duration: 4564s | Summary: Reports Everyone Should Know How to Create in eTapestry | Chapters: Welcome and Introduction (0s), Reporting Basics Overview (285.86s), Reports and Queries (760.04004s), Account Reports Overview (1080.53s), Grouping Report Data (1944.47s), Grouping and Collapsing (2290.68s), Aggregate Report Functions (2964.325s), Summary Fields Explained (3459.375s), Dropbox Storage Features (4283.6997s), Conclusion and Resources (4382.85s)
Transcript for "Reports Everyone Should Know How to Create in eTapestry":
Hello, everyone. Welcome to today's session. Hope everybody is, has had a good start to August so far. I, of course, am Geoff Arbuckle. I'll do a little bit more of an of, an official, introduction to myself here in a short moment. This session this month is going to be about reports. Now last month, we did the queries part. Right? And what's kind of funny is is that initially, I had intended on the titling of the two, of the two sessions. Last month's five queries everyone, needs to know how to do or whatever. To be something similar to this month, which is five reports that everyone, should know how to build. But when it comes to reports, I decided to do something slightly different because it's not so much about how you build a report. Queries need you need to kinda know and understand how to create queries. You need to understand what it means to include certain pieces of criteria and what are some of the settings around queries that could change what it is that they are providing you. When it comes to reports, it's more about the techniques, more about the pieces of what you can do with certain columns less than knowing how to build a a report necessarily. And I'll get into a little bit more about that here in just a moment. So, so you might see the title of what you signed up for and the title on my title slide differs slightly, but basically doing the same thing here. There is something else that I'm doing a little bit different this time around is this is going to mostly be a screen share session. Because as I was thinking about building this, this slide deck, I realized that it would be a little bit more important for me to be able to kind of show you the workings of the report as opposed to having it be a a screen or, you know, like a slide a screenshot on a slide. So I am doing that a little bit different this time around. It might be something that you might see more of going into the future. So, but with that, let me do some, real quick, some real quick housekeeping here. Of course, the audio, as always, is broadcast through your computers. This is going to be one of those situations where if you do end up running into any, video technical issues, like, for whatever reason, you're not seeing things moving as I am sharing my screen. You know, usually, a quick refresh of the browser will be all that you need to do to, fix that. At worst, you may have to leave and then come back. Then, where typically I make a big stink about saying, hey. Go to the docs section and, get the slides to the presentation. You're gonna notice there are no docs this time. There's no there's no place to even go to docs. That's because, again, this is going to be primarily a screen share. I have a few slides here, at the front and in between each section, but you're going to mostly notice that I am, mostly working within my own test database. So no, no slides for you this time. That does mean that it's really important that you understand that this is being recorded. So if you do want to review anything that I talk about here in this session or if you have to leave early or unexpectedly, you'll get the recording, the link to the recording about twenty four hours after the conclusion of today's session. So look for that to arrive tomorrow afternoon. You can, of course, use chat. I always love seeing everybody already introducing themselves in the chat. That's always fantastic. So keep that up, and you can always use that to ask your questions as well. I already see some, some familiar names and some, familiar, some familiar places. I'm actually, I see a couple of people who I have worked with for a very long time. So, that's always great to see that you're still working with any tapestry and that you're still, getting something out of the, out of the session, that I perform here on a monthly basis. So thank you so much. Alright. So real quick as people continue to get settled in here. You know me, of course, as Geoff Arbuckle, customer success manager here, the ETAP guy. I hope, other people in the Midwest or, in the general area East Of The Mississippi. Also enjoyed some nice milder weather last weekend. That's a great way to start the Indiana State Fair. I'll tell you that much. But I hope, everybody is having a, like I said, a good start to August. And with that, I say let's just go ahead and jump right in. And, I will get to as many questions as I can as I am, kinda going through some of the stuff here. But I do have a few slides to kind of start us off. So here's what we're going to be talking about today. I'm going to start with the first steps and the general anatomy of what you will see in reporting. Then I'm going to talk about the techniques in play of pulling account information, how to use the group report by field. I brought that up a little bit last month when I was talking about queries. So I will go into a little bit more information about that and probably will be able to kind of illustrate a little bit better what I was meaning, about that. Then I'm going to talk about aggregates. What is that? How can they be used? When should you use them? Or what are certain, instances in which you will be using those? I am going to talk about, summary fields as well. How to make a report with summarized giving information and why that's different than aggregates. They're very similar but there's a there's a key difference between, summary fields and aggregates. And then I'm going to talk about something that I always love talking about when people don't realize that it's something that they can do, and that is scheduling reports. We do have the, the capability of saying, okay. Well, if you set up a report, that is always going to be, updating with the current month's information or the previous month's information? How can I get that sent to my board or to my, development director or whoever, or to myself for that matter, at the start of each following month? So, that is definitely something that I will, go into because that is something that can ease a lot of people's stress and worry around, building reports and and doing things like that. So that is something I also expect will be highlighted a little bit in next week's Ask the Expert. Okay. So with that, let's talk about getting started and the anatomy of reports. Now much like with queries last week, these are going to be the primary steps that will take you to creating a new report. First, you'll click on reports, then you'll click on either a category or you can click on manage reports. Normally, when I send directions to folks who ask for them, I normally just say click reports and then click manage reports. That will take you to the screen with all of your categories. You then click on a category. And then, under tasks in that category, you will be able to click to create a new report. So this looks very familiar to those of you who, were in, the session about, queries a few weeks ago. Very same steps. In fact, queries, reports, and communications all have very similar first few steps. You click on the menu, you click to manage or to click on a specific category right from that menu, And then, under, you know, once you select your category, then under the tasks you'll find the new whatever it is that, that you're looking to build here. Okay? So those are the typical first steps. So that's definitely something that I recommend that you keep in mind as we do this. I will illustrate that a little bit more when we get into the screen share as well. Then here are this is what I basically call the anatomy of the report. So what you will typically see is, the first step that you'll see there on the left hand side of the slide is the report basics. That's where you name the report. You can enter description if you would like. You can save it to your favorite tabs on the home page. That's something I didn't really talk too much about with queries last week. You can mark these as favorites. They will appear in the queries or the reports, menu, but they will also appear on the, favorites, panel on the home page when you log in to eTapestry as well. Then the next section after that is the group results. Now that's something I'm going to definitely talk a lot more about, as we continue into this session. So, but this is where you can manipulate whether or not you want it to be grouped by a household, for journal entries, or by or for, you know, anybody that you have, like, marked as head of household. You can also group it by account, especially if you are dealing with journal entries and you're only wanting to see, total information or some of the stuff that we'll talk about when we get into the aggregate discussion. Then at the bottom of the page, this is where you will select your report columns. Now one key thing to remember here is that reports and queries are not really the same thing. Queries do all of the thinking. Right? They're the ones who are being told to go out and fetch people that meet certain criteria. Reports, on the other hand, are a little bit more mindless. They're almost like a shell. It's waiting for information to fill it. So when you're talking about creating a report, you're talking about selecting the columns that you want to see from a journal entry or from an account. You're not so much talking about the criteria. So you don't have to put in things like a date range. That's what the query is doing. The report is just waiting for the query to fill in the information. Now there are some asterisks when it comes to what you can display in a report based on what you have as far as the queries data return type. I'll talk a little bit more about that, here in in a moment as I kinda get into this information, about these various, scenarios that I have for you. But generally speaking, reports, like I said, are kind of mindless. Think of them almost like drones. Right? They're just waiting for something to be done. It's waiting for the information to be filled in. If you think about it, like, when you're like flying a drone around, like, think back when, Amazon was, you know, trying to deliver packages with drones. The drones themselves aren't the package. The drones is the delivery mechanism for the package that was ordered. So it's just waiting for information for it to present you with something. So hopefully, that that helps you kinda differentiate the, the difference there, between queries and reports because it's a pretty major one. Reports just wait for information to fill in. Now when you select your cat or your columns for your reporting, then you can click to run the report. Now every report requires a query. Now one report can use a bunch of different queries depending on what it is that you're asking for. You do not have to create every single report or you don't have to create a report for every single query that you have created to find information. It's just waiting for whatever query it it is that you want to fill in the information for it. One of the things that you can do is, you can either use one of the queries that are already created, like the base all constituents that's in everybody's database, or you can, create the report directly from a query that you just created. Say, all of the people who, wear size ten and a half sneakers whose favorite color is, burgundy and gave something last week. Well, if you just created that query, it's ready now for a report to display information from it. The other thing you can do with reports is that you can remember the query so that every time you come back to the stage to run the report, it will already have that query selected. So that could come in handy for some reports that you run quite often. That will especially be, key when you are doing things like certain campaigns or like Giving Tuesday, for example. Those are, that's a checkbox that you can select because those are times in which you might be consistently or constantly looking for updated information. Well, the query is out there pulling in the information. However, based on how you know, whatever criteria as you are entering the the gifts into the database. But with the report, if you are wanting it to be manipulated in such a way to be able to display it, then you will be able to save that query so that it remembers it the next time you run it. So if you're running a report multiple times during the day, like I said, Giving Tuesday is an excellent example of people potentially, running reports multiple times during the day, that checkbox is a huge help. Most of the time, we skip over the advanced options because 99 out of a 100 times, you are probably not wanting to change anything there. Although, this is where you could change personas if you have household, stuff that you want to take into consideration. Like, if you have a joint persona and you have this group by household, you can make that change there. But then the delivery options, that's where you can actually choose how you want to see the report. You can display it on screen, which is the default, or you can export various different file types, by way of download or email are the most, popular kind. The, Dropbox is found under the home tab, in the home menu on, eTapestry where you can upload things to the Dropbox and go and retrieve them later. And then you either click submit or you can click to schedule for off hours. So, Cindy, great question. If I create a query to see all donors who gave to a specific fund, how can I pull a report that list just that fund and not all giving? So that's gonna be done partly in or that's going to mostly be done inside the query. Inside the query, you'll wanna make sure that the data return type is journal entries and that you have the specific fund selected. Then because of that, it will say it will only be these journal entries with that fund. And then you can, at that point, that will be, you know, that that will then narrow down the results of what the report can display. And Wilma, I will be getting that to, that scheduled, questionnaire that you have. Hang tight. I'll be talking about that before the end of today's session. So alright. Oh, so yeah. So that column, Cindy, I'll talk about that a little bit because what you've pulled there is a summary field. And summary fields don't work the same way as so what you would do is you would say, you would group the you know, you would get the the fund from the query. And in the report, I'll show you in just a moment what you would be doing with that then. Yeah. The summary field is going to pull everything else, and that's that's where you're getting all of the additional information from within that column. But we'll we'll talk about that here in, in just a couple of, moments here. So let's talk about account reports. Now I have a scenario here. We're gonna see these two goobers a lot. They're they're really working hard and pointing at things on the computer screen. We're gonna see them for the rest of the day, I think. But, my scenario for this is is as simple as you can be. You just want to see a list of all your donors and their account information. So maybe like addresses, maybe some attributes, and so forth. So with that, let me, There you are. Now you should be seeing inside my test database. If you do need to, you should have some, controls where you can zoom in or make things a little bit more, a little bit larger on your screen. So, you know, look for those controls there. It should be like a little cogwheel on your, screen there if you need to. But I'm gonna go into reports just like I was talking about earlier. I have my categories here or I can click on manage reports. Now I've already done a few things in advance. I've already created a category that's just called Geoff reports. That's where I'm going to build these examples, or this is where I'm going to work with examples. I also created a couple of queries that are really simplistic. They're not going to be one size fit all for all the possible things that you can do, but here under Geoff queries, all I've done is I've created queries that are only my account and one with only my transactions from my test database. So that's what I'm going to be primarily working on. So if I go into my Geoff reports category and I click to create a new report, I'll just call this account report. Like I said here, you can select this to be your favorite and, you know, to be a favorite report or not. But the most important thing oh, and also private. These kind of tell you what they you can do here with private and read only. Most of the time, you're probably not going to do this. But if this is a situation where you have a bunch of volunteers doing some work inside your database or they're pulling certain things or you don't want them to mess with certain things, you can either set things to be private or read only, which means that anybody less than admin or who is not you, they won't be able to either see it, run it, or make any edits to that report. So that's something to to keep in mind that that's always something you can do with queries and reports. Now for the group results, I am going to leave this as do not group, but you will see that by default your three options are do not group, account, or by household. Now for those of you who work extensively with households, you might consider still selecting household, At which case, if you're wanting to get an account information or if you're wanting to get account details, you would probably just want this to be group by household and collapse groups. I'm gonna go into a lot more information about grouping momentarily, so just hang tight there. Normally, when you get into collapse upgrades and segments, normally, you're going to leave that as no. You can select yes. I don't know many people who select yes. Most of the time people think of, segmented transactions as having their own, individual pieces of information if it's going to be listed individually. Whenever you're dealing with account information, you don't have to worry about those segments at all. But when we get into, selecting our fields, some things that I will select here for this is I just want to see the information of the accounts, their, address, their contact information, that sort of stuff. I can just do account name. I can select address lines. Address lines is only street address. So do keep that in mind that you would still need to select city, state slash province, and postal code. Postal code, not really something a us Americans use as term you know, we usually say ZIP code. But that's, we we internationalize that term so that everybody, would know what that is. So one thing you can do though is if you say, well, I don't know. I just want that to say zip. You can come into this use notice that all of these titles are in kind of like a gray box. You can type in that box. So you can you can say, alright. I want that to be state and zip or something like that. One other thing that I typically recommend people include in their reports, especially if they are pulling account information or especially if they are collapsing, journal entry information just to get grand totals, I recommend that you choose sort name as well. Sort name in the database is typically for individuals last name comma first name. Sort name is a good thing to include because if you click on these little dots next to the name of the field, you will notice that there are that there's a field here that says sort order. And there's an arrow pointing down saying a to z, and then there's a there's another arrow pointing down that says z to a. So I can click on this, first one. There we go. And now you'll see over here in orange, it says I am now sorting this field in alphabetical order. But because we have account name and you don't really need the sort name field to be visible, we can also deselect the visible, option here. This used to be a little eyeball icon that you can deselect. Now what you'll notice here is that sort name is now grayed out, but that is still a part of this report. It's still alphabetizing even though it's no longer going to be showing in the reports, con you know, in the final report. But because this is account information, I can also pull in additional account fields. Like here under account fields, I can separate the line the address lines if I want to. I can also pull in user defined field information. So maybe I also wanna pull in account type. If I want this to appear someplace else in the report, like maybe before account name or maybe after account name, I can click and drag these fields into whichever order I want. You'll know that you can click and drag because you'll see the the arrows, the perpendicular arrows, that then indicate that you can add that. You also have your x's over here to remove that column. Okay? So pretty basic stuff here. I'm just pulling account information. I'm just pulling, contact information. I also have the ability under commonly used fields to pull some phone fields. I can also pull email address from this, category as well. They're also found in account fields. Yes, Abby. If you want to include multiple, sorts, all you have to do is you just go in here and you say, I wanna sort account. Oh, that's not I don't wanna do account name. I wanna do account type. I'm going to also sort account types first, and then change the drop down menu so that the two indicates, like, okay. The account type is going to be the first thing sorted and sort name will be the second thing sorted. So all of your businesses will be first and then individual. But then within that, it will start alphabetizing those as well. Mary Anne, that's something we're going to be talking about here in just a moment. So, yes. You can get, other fields like funds, campaigns, and so forth. We'll talk about that here in a couple of different ways in just a moment. So basically just making this a generalized account information field. I've pulled all the fields I wanna pull. I've organized the fields in the way that I want them to be organized. I have selected sorts. I have made certain fields invisible because I don't really need to see the sort name. If I feel pretty good about this, now I can do save and run. And when I do save and run, I'm going to search by category. I'm gonna select my Jeff queries. I am going to choose my account data return type. I can do the journal entry one and it would work for what I'm doing here because it is only me in that query. However, generally speaking, if you're pulling account information like this and you're you're wanting to pull this maybe for a mail house or you just wanna get a list of your accounts, you don't want a journal entry return type query. You want an account return type query. If I wanted to, I can also remember that query so that it remembers it the next time I come to launch this particular report. Or I can just say, yeah. Leave it alone. I'm only gonna run this one time, or I'm not gonna worry too much about this. Or I might use a different re query down the line for the same report. So that's something to take into consideration. Now I can also select how I want to receive it, my report format. I'm just going to do the schedule results on screen, but because then I'm going to click submit. Now, like I said, if this was your database and you're running it based on a query or based on all constituents or whatever, what you would likely see is a whole list of people. But you'll see here, you got my name over here, You've got my account type. You've got my address, my city, my state, my zip code. It also carried over that I took out the province, then I changed postal code to zip. So it does keep that into the results as well. Now if you looked at this on, you know, displayed the results on screen, everything looks right or you did that just to be careful, then you can export it from here as well. The same export options are here and you just click export and then it will export that out however it is that you wanted to receive that. So that is as simple as it gets as far as an account return type, query pulling account information into a report. You're just selecting report level fields and that's that. So let's return to my category here, and then let me pull up my, my slides here. So now let's talk about journal entry reports and the group report by options. This is probably the most important portion of today's session. Okay? Because this is the one that leads to answering some additional, you know, questions that have already been asked about, like, pulling information for, like, funds, campaigns, and so forth. And also, like, how to make sure that you're only getting certain information. Okay? So let's, let's take a look at our two, business dudes here. So you've pulled a query of giving within a time frame, let's say. And now you want to create a report. So how can you use that group report by to organize the report in the way that you need it to be displayed? Okay. So come back into my there we go. Real quick here, Lisa asked, are there scenarios where it would be preferable to use only a query and not a report? That is if you're pulling a mailing list and you design it in queries, what added value does the reports process at? That's an excellent question, Lisa. You can export, report or you can export query results. That is true. The one thing that the report adds is if you want to include certain columns that the that the query can't, off the top of my head, I don't know exactly what those might be. It might depend on something like a summary field, which I'll talk about here in a little bit. But it the the report is going to be most handy for journal re return type queries. These are the things where, you know, somebody maybe have given multiple times in a time frame. The query is what's going to to display the raw data on that. It's gonna show each and every time that they, that they ran a report or that they, gave a gift. Running a report with that would give you the option to collapse that, to group it, to do a little bit more finagling with that data so that it's a little bit easier to read. In the example that you gave, I can't think of anything right off the top of my head that I would say, yes, absolutely do a report and not just export the query. But when you get into manipulating the data to make it more readable or to collapse, multiple gifts into a single line and with the grand total and all of that, that's what the added value of the report is. So with account return type queries, it could be, you know, that's the yeah. And that's also, Bill, that's another good one too. On the query, it may not break up the mailing information the best way that a mail house could use it. Does that mean that it could be in a way that you could use it? Oh, sure. It could be. But, yeah, it's going to put all of the mailing address into a single field, into a single, box on the on the Excel file. So that is something else to take into consideration as well. But I think it really kind of comes down to what do you need the information for, what is it that you are wanting to see, and how do you want to see it. Might be easier to have a report. If you have a bunch of reports already in your database, there's likely reports that are already doing things with data that you would just say, okay, I'm just gonna plug this query into this five year old report that I had that already has all the columns and the settings the way I want them and I'll just run the information that way. So it it kind of depends on what it is that you are using the data for and what you're wanting to and how you're wanting to read it. Okay. So for this report, let's do a new report. I'm just gonna call this journal report. Names of reports are absolutely not, necessary to be specific. Okay. Oftentimes, I tell people or I advise people, you know, like I said, you're always going to be building more queries than reports all the time. You're always going to be doing more queries than reports. But with reports or with queries, you do want those to be specific. Donors who gave in 2023, donors who gave in 2024, donors who gave last year, donors who, don't wanna be, mailed or whatever. You know, you're you're naming it after its purpose. For a report, oftentimes you can just name it after the columns that you're using or the layout that it's going to have. You don't necessarily have to call a report donors who gave in 2023. So that's one thing to keep in mind as well. I say that a lot. I recommend that a lot. I know still people do that just so that they make sure they cover all of their bases. But a one report can have an infinitude of queries feed into it depending on what it is that you're wanting for that report. So just keep that in mind. Reports can be much more generically named. Okay. Now, when it comes to journal queries and then using them in the reports. So let's say you want to get a list of queries that are or you're gonna have a query that has a list of people in it that gave multiple times throughout the course of the year. But what you wanted to do is have the person's name and then under it have each of his transactions or his or her transactions. Right? So with that, that is a grouping option. That is how you want it to be grouped in the report. So that's where the group results and this group report by section comes into play. Most of the time you're either grouping by account or by household and when you see the secondary drop down menu show up, your options are going to be hide group totals, show group totals, or collapse groups. So let's say you wanted to see each and every gift that somebody has given and you want it put out in in date order or whatever, and you can do that by saying, okay, group by account and then show group totals. Now with that, we can come down here and we can say let's add the account name, let's put in the date, Let's put in the received. We're gonna put in fund. And, yeah, sure. Let's put in approach and campaign just in case here. Now with date, you can come over here and you can sort that so that it shows up in in date order as it, you know, as it lists all of those transactions. So when we save and run this now, now remember this is we're grouping by account and we're showing group totals. So let's save and run here. We're gonna go into my Geoff queries and I'm gonna use my journal entries, my Geoff transactions. I'm gonna go ahead and remember this because this is gonna come into play, for the next example in this section. And let me display the results on screen. Now here, if we were looking at a full database and not just my information, you would see, okay, well here are all of, you know, here's all of Geoff transactions. Here's the next person, the next person, the next person. Now you'll see here that, the way I have this sorted is earliest to most recent, so that comes into play here. I've got a 2015, couple of twenty sixteens, 2017, all the way down here to 2025. I've got my giving, my received. The top will always give the grand total of everyone. But then as I scroll down to the end of my grouping, it will also grand total that grouping. Now again, if there were an entire database, an entire, galaxy of people that are inside your database included in this reports, listing, then this would be the group total for one person and this would be the group total at the top here right under received for everyone. So do keep that in mind. And then, of course, I've got my fund, my approach, my campaign. Now, to answer a question that came up here, what if I wanted it to group, say, by the fund or by the approach or by the campaign? I can absolutely do that. Now let me go in here and I'm gonna click on my report here. There's these little links down here where you can go straight to your query or to your report as well at the bottom of the, screen. Now, because I've selected more fields, my group by options also expand. So now I can select any one of these additional fields that I've selected to group by. So I can group by fund and show group totals. Now what I'll probably wanna do here is I wanna make sure that I move the fund up to the top. And now when I save and run, it's remembered my query. And now when I do this, now you'll see my funds are now the group. And they each have a grand total at the bottom. Diana asked, can you group by one field then subgroup by another? No. Unfortunately, there's only one grouping per, report. That would be something I would definitely recommend. Go into the community. Go under ideas and make that suggestion, or see if somebody else has made that suggestion and upload it. That could be something that I could see someday being a possibility. One of the one of the things about Blackbaud is is that, you know, we are now specifically looking at suggestions from users. As, you know, we pretty much added all of the big, big stuff that we can, you know, add as far as functionality. These types of functionalities like you, asked for there, I think that would be a great, thing to put into the ideas on the community page. If you go in the community and you find the Blackbaud, there's a way that you can search for the different communities or look at the different communities. Go into the eTapestry community. There'll be a tab there for ideas, and that's where you can do that. Now what if we were to say, okay. Well, we don't really wanna see all of the transactions. Maybe this is something for a thank you letter or for a mailing. And what I really wanna do is I really wanna just see the person's grand total. Well now, you do Yep. I'm gonna do that. And instead of show group totals, I'm going to collapse groups. Now the one thing about collapse groups is that it collapse groups does not work very well with things like date, fund, approach, campaign. Now why is that? Well, because those are going to be different for potentially for every transaction. I mean, obviously, date is going to be different for every transaction somebody gave. Fund could be different for every transaction as is approach, as is campaign. So what we'd wanna do is we would want to pull out date, fund, approach, campaign, and just not the just so that I don't make this look, too naked here, I will include address fields as well and I'll move receive down here to the bottom. So now I've got a group by account. This works the exact same way for household as well. So you can you can do the same thing for household as you can with account. I'm gonna collapse groups. Now I'm going to save and run. Let me display the results on screen and what you'll see is instead of all of the entries listed, now you just see one listing, my name, my contact information, and my grand total off to the side there or under that received column. So that is where you can say, okay, do I wanna see the list of of the entries and I wanna see all of the details per entry, or do I want to see the collapsed amount? The same thing could potentially work if you group this. Now where where, if you were wanting to say, okay. Well, I do instead of seeing the individual name, I do wanna see just the fund grand total or the approach, grand total or the campaign grand total. You can substitute that instead of account name. You just would have to come up here and make sure that you are grouping that. It's when you group by account in collapse groups, that fund campaign approach date, those types of things don't work as well. But if you are grouping by the date or by the fund or by the campaign, then it can collapse that and give you a grand total for those individual fields like that. It just doesn't work that well if you're grouping it by the account or the household. Okay. So a couple of questions to to follow-up here. Let's say I have a long list of people. I have one I have a field called affiliation that has a number of values including board member. In my report, I wanna see affiliation, but only if it's board member. That, Diana, would be done actually in the, query. So you would you would make that as part of your criteria in the query. Jolene, if you wanna narrow down Oh, wait. Hang on a second here. Diana, I see your oh, I only wanna see affiliation if they're board members. Gotcha. Gotcha. Blank if they're not. Sorry. Thank you for that, clarification. If it is a, so if there is a if that is set up as a check mark type of field, yes, you could do that because when you have check marks, check mark type fields, the defined fields separates those out into those various check boxes. Okay? Then, then you would be able to say, okay, I only want this to be, you know, this attribute. If they don't have that, that would now if it is a drop down menu, it doesn't quite work that way. So that might be where you would want to, you know, alphabetize that and then just wipe it out if it doesn't have board member underneath it. You can, alphabetize the various options in that field. Okay. Yeah. So, Jolene, you had asked, okay. When you want to narrow down the date range, that would be built into the query. So the date range would be the query because that's part of the criteria. Query always does criteria. Remember that. And so that would be part of the criteria. Haley, to create end of your tax letters, is that a report or a query? It would be a query to find the the transactions that you want to create a a tax receipt for, but then it would be done in their communications. I'm gonna talk a little bit more about communications later this year for that. Under the collapse feature, is it possible to include the number of results collapsed, I e 15? Yes. So Lisa, that's actually going to be coming up here, very, momentarily here. So return type. So return type is a query, it is a query designation. And basically, what that means is what do you want the query to return based on the match that the criteria made? So if you went out there and said, okay, give me everybody who gave last year. The return type would be, if you just wanna see the people who did the thing that the criteria is set up for, the return type would be accounts. But if you actually wanna see the gifts and the entries, that would be journal entries. Right. That's correct. So if you in that case, you would if you would think that you would wanna see journal entries and then right. So when you do an account return type query, depending on what you wanna pull here because when it comes to accounts, return type queries in reports, it can't pull received. It can't pull journal specific information. So do keep that in mind. Now so that is something else to keep in mind. As you're pulling your report columns, if you're pulling things from journals, so like receive, date, fund, campaign, those types of things, that would end up becoming, part or that that would require you to have journal entries in your query to be able to pull that. So that would require the journal entry return type. Okay. So now let's go back to my category here and let's pull up these guys again. And let's go to the next section, which we are going to talk about aggregates. Now, I put the aren't they aren't they a great thing? That is an old joke that I will never forget. An old team member about fifteen years ago, used to say aggregates were a great. I don't know why that sticks in my head, but it's such a bad joke I had to include it here and torture all of you with it. So I'm sorry about that. So let's talk about aggregates. Now let's say in our scenario, you're being asked to find year over year giving to a particular fund or the average amount given by all of your donors or what your donors biggest donation ever was. Okay? So that's your scenario. You're wanting to say, okay. Well, alright. Let's look at everybody's transactions, but I wanna know what the average was or what they're giving year over year was or whatever. Okay? So for that, we're gonna come back in here to my journal report. And when you set this up, when you're working with aggregates, you will always want to collapse groups. The reason for that is is that aggregates are meant to basically be doing some math within a field and showing you the result of that math. Okay? When you are selecting your columns here and you come down here and you say, okay, here's I got my account name, I got, you know, whatever else I want to display. Actually, I'm just gonna do received here. So I got my account and I got my received. When I open up the little menu here, you'll notice that I have this section, this drop down menu here for aggregate. When you open this, you will see a bunch of different options. And what this is is it's telling received what to display. I can display what the average is and you can even set that up. I can come over here and I can pull another received field and for this I can say what the max was. I can also do that for date. So I can say what the date of that largest gift was. This, follows up with a question that was just recently asked here, which is if I pull in another receive sorry. Everything is highlighted there. I hate when I do that, and I can't undo it. There we go. Somebody asked, well, can I see the number of transactions listed? There is a count for aggregate. So I can name that number of transactions and so forth. Now one of those examples also showed, you know, year over year options and that is available as well here. So I can say, what has somebody given year to date? I can also include additional received for one year ago, two year ago, and so forth. But the aggregate is basically telling the field how you want that field to calculate. What you want that field to show. Okay? So now when I save and run my report and I have my Geoff transactions here again and I submit. Now remember, this is grouped by account. It's collapsing groups. And now, it's showing you that my average donation is $240.57. My largest is 2250. Oh, it didn't do the date. For whatever reason, it didn't show me the date of that largest transaction. But then it also had the number of transactions. I have 35 transactions and then my receipt to date is 1350. So it is showing me like, okay, well, this is breaking those numbers down into different, you know, different features like that. So, let me go back here to the date. Yeah. I'm curious why it didn't show the max here on the date. But still, the point is is that this is what it is. Here we go. Let's try this again here. But the but the idea is is that these received amounts are going to now display certain pieces of information based on whatever that aggregate is telling it to do. Can you aggregate a fund or a campaign instead? No. You can only group by, you can, you can only group by the fund or campaign. You can't aggregate that field in particular. Can account funds or campaigns? Yes. So if I were to group this by by fund or campaign instead of account, yes. It can show the number of transactions within that fund. Again, it would just be, you know, doing group by fund. So, like, if I were to come in here, no. Diana, that won't work that way because it it can only calculate the information based on so you wouldn't be able to select fund and say, okay. Now count that. We can test that, but I'm pretty sure it doesn't do that. So let me let me go ahead and add it in here, and let's see if it does do that. Maybe I'll learn something new here today. Let's see if this works here. Now, to why you would put something like max on a date was it used to work in a way to where you would say this was the largest date this was the largest gift date. But apparently, it doesn't work like that anymore. Let's see here if the fund will no. It does. It still says 35. That's the number of transactions I had, not the number of funds that I've had. So, yeah, unfortunately so the fund won't aggregate appropriately. It can do the it can do the so, it can do the average giving total for a campaign, but you have to group it. So the report has to be grouped by that, by campaign. Right? So instead of grouping it by account, I would select campaign and then I would select that to group by. And then it would be able to show this information and then say, here's the number of transactions, here's the average for that fund and so forth. Alright. So similarly to aggregates, there is something else that we have here. Let me pull up our business guys again. And that's summary fields. Now this is similar. It's a little bit more simplistic even, but similar to the concept of aggregates. So let's say you have a list of accounts and you want to see their lifetime giving total shown as well or what their gross year over year over year giving was without needing to have a journal entries return type query. Okay? So we're gonna go back now to my account report. Okay? So let's say I have a list of accounts in a query, but I still wanna show a grand total of what they've given. And I don't really wanna build a journal entry return type query. I just wanna add this field to a report. K? We have an entire category called summary fields. Now summary fields and household fields are very similar. Household pulls for the household, summary fields pull for the individual account. The thing is with this and what differentiates this to aggregates is that summary fields pulls from the entire account, not just from whatever the query is providing it in terms of journal entries or criteria used to pull that account list. So that goes back to a question earlier that there was a specific query built around a fund, a campaign, or an approach, or whatever it was. But the report, because of the household fields, was still showing the entirety of the giving for that year and not just for that specific approach or campaign or fund? Well, that's because summary fields and household fields pull from the entire account. Summary fields are found on an account's home page. So it's giving you a gross total of what somebody has done this year, over the last five years, and so forth. But what you can do here is you can say, okay, well, here's the first transaction date, here's the first transaction or the first let's do first received instead of first transaction. First received date, first received funds, so that'll be the first time I gave. You can also find the last received amount, last received date. You can say lifetime, received amount received total, lifetime transaction count, And then there's also all of these one year ago, two year ago, three year ago. All of these can be used as well as summary fields. So then what you can do is you would do save and run. We're going to choose my account. Now this is just accounts. This does not have any journal entry giving information in the, results of the query if I were to preview the query itself. But now, you will see, it still, along with my account information, still shows what my first received amount, my first received date, what my last date and amount was, what my lifetime was, and how many transactions total have I had. So these summary fields work similarly at aggregates information, but it is more simplistic than aggregates. Aggregates use journal entries to say here are based on these exact journal entries, what the average, what the largest, what the smallest, what the first, what the last, what the, you know, so on and so forth are. You know, what they were, you know, what the giving was one year ago versus year to date or two years ago or whatever. Summary field says, okay, this is just from the account what their gross amount was that they gave total, what they gave one year ago, what they gave two years ago, and so forth. Okay? So these are, you know, summary fields very, very, very useful when it comes to getting this type of information quickly into a otherwise account centric report. Now the big difference is again, why would you use summary fields over aggregates or vice versa? It comes down to the details. If you just wanna see what the account has done as a whole or you have an account return type query, summary fields will work perfectly. If you wanna get into a little bit more nitty gritty about the average amount or what the first three gifts were that somebody gave, or what the average was with within a specific fund, or what they gave year over year within a specific campaign, that would be aggregates because that gets into the exact journal entries that's provided from the query and then be able and then is able to calculate those types of, those types of numbers. Is it possible to get all personas in a single report as in a report of accounts and I want to see personal persona info and then join and but in a single row for not in a single row. It would be listed out individually. So each persona would have an individual line if you were to export all personas. Okay. So that's summary fields. Summary fields are very, very useful. I have a feeling we're gonna talk more about that in and with aggregates next week. But one last thing I wanna cover. Sorry, we're a little over time here. But we have one last thing to do here. Let's talk about scheduling reports. Okay? So now your board wants to see all of the previous months giving at the start of the current month every month going forward. K? So a couple of things to note here, when you get into it doesn't really matter which report I use here because it will be the exact same steps. So a couple of things to keep in to know about this delivery option section, Whenever you select to receive something by email, you have the ability to set up whatever delivery email you want. So if you were to run a report for somebody else, so like let's say your board members want something right now, you can come in here and you can put in all of their email addresses separated by commas, and you can just send it from here. Same thing if you run it to screen and then in your export field you say, okay now I wanna export it to email, you should have the ability to put in email addresses before you click export. But, let's say in this scenario, you have a query and a report set up to always show everybody's donations with all the details that are asked for for last month's transactions, and you wanna make sure that on the first day of every new month, you want that to end up in your board's, inboxes. So what you'll do is you'll select to do an email, and then you'll click schedule for off hours. Now schedule for off hours brings you to this page. By default, it will set itself to daily. It will tell you what the name of the report is and in parenthesis, what the query is. So you could conceivably change, you know, you can conceivably, you know, rename it to whatever you would like for it to say as far as the subject line and make it a little bit more clear what that is going to be. But by default, it's going to be set to daily, but you can just click on monthly to pull up this window. Recur every one month on the first of the month, or you can say the first Monday, or the first Wednesday, or the first Tuesday, whatever it is. It's up to you however you want that to be. But I'm just gonna say the first of every month. Then I can come down here by default. It will always be set to tomorrow's date. So what I can do is I can come over here and say, I want it to start on 09/01/2025. And for the end date, you can set it out to one year. So I'm gonna set it to 09/01/2026. I can always come back in here later, and I'll show you how to do that, to update that date range. Then you will put in your email addresses and then you will click and you can set up your subject title, you know, to be whatever it is that you'd want. And then you would click update. And what it's going to do is, basically, it's always going to run around 12:30 in the morning on that day. Now it says except on Sunday, which I think, just means it's going to run a little later on Sunday morning, like around three instead of but, but what it will do is on the first of every month around 12:30 in the morning, local time based on your databases, time zone, it will create it will run this report and it will create it. You do have to put in an end date, because it does only allow for one year for it to be scheduled at a time. The reason why we limit it to one year is that in the past, you know, people would come and go from organizations and people don't realize what's been scheduled. And so things were constantly running on our servers when, you know, when whatever schedule came up. And there were reports that were no longer being looked at or being received by anybody. So we've limited it to one year so that at least after a year, especially if it's a particularly large report, for whatever reason might be scheduled to run on a regular basis, it's no longer using up that extra, time. So you do need to put in, to to change that. Now, would you need to change the query? Not necessarily. The query can be set up and this was something that I talked about, I think, a few weeks ago in that query session. You you were able to set up a query to not run based on specific dates, but on specific ranges. So you can have a query set up to say, show me everything from last month of $1 or more. The idea is is that you would have a query that would set that up so that the query on the first of every month after midnight would always be looking at last month, which is the month before. And then you would never have to touch that query again. So once you set up that query, then you can set up the schedule to run. And then when you update this, it's now going to, basically start running every first of the month. Now if you need to update the date ranges, what you would do is, like, let's say you're on your home page, and let's say six months have passed now and you need to update your your range on that. You can come into reports and there's scheduled items button right in the middle of the screen. You come in here. When you click on it, it will be orange, and it will show you the setup of this. And then you just come in here and say, now run this from three one, 2026 to 312027. Click update. Oh, I took out the little slash there. Then I update that, and it will now remember that. So that's how you can do some scheduling of reports. Definitely something that can make your life a whole lot easier, especially if you know that people internally or even yourself wanna see certain information on a timely, consistent manner. And that is definitely something that you can, use to, to make your life a little easier on that. Catherine, sounds like you and I are, you and I have been doing the same thing for the same amount of time because I've been almost twenty years working with Etech too. So, yeah. This is always something great. One of the things that I also mentioned was the the Dropbox. You can always have things, sent to your Dropbox as opposed to download or email. The Dropbox is under the home and it's listed here with my Dropbox. It will will say what's in your Dropbox, but you can also click see all and it will list there and it will tell you how much space you've used. You can clear out your Dropbox or you can just click on one of the reports in the Dropbox and download it from there. That is handy for particularly large, like long running reports. So like, if you've got twenty five years worth of data you're trying to export into, Dropbox or if you're wanting to export into a spreadsheet or into something like that, you can select to export it to the Dropbox instead of downloading it, which might take a while for it to download. You can say, okay. Send it to my Dropbox. I'm gonna go to lunch. When I come back, I can go under home, click to see all. It would be listed here in my Dropbox where I can then download it very quickly from there. So, yeah. The Dropbox is just the storage spot, Diana, that you can use to you can, have reports run and be saved here, so that you can come back and get them later. Alright. So again, sorry this went a little over, but I wanted to get into a little bit more detail over, like, how some of this information can be used, how it can be run. I suspect that next week at the ask the expert, we'll be talking about some of these things again a little bit more, in directed, you know, like kind of how to on very specific circumstances. So I look forward to that. I look forward to seeing everybody there. Of course, you can always, utilize these various resources. Blackbaud U is a great place to get a little bit of training. There should be information about reports in there as well. Support knowledge base always a great place to go to get those step by step instructions especially in the knowledge base. And then the community, like I said, that's a great place for everybody to get together, but it's also a great place to put in your ideas and suggestions for future updates to eTapestry. These programs here, Blackbaud Champions references, and the ability to spotlight your success, these are things that we're always looking for. If anybody is interested in joining any of these programs, more than happy to, to basically, invite you into that and get you vetted for that with our internal team. If you are interested in in joining the either the champions or the reference program, let me know in the chat. We can talk a little bit more about that next week as well, if there's anybody who might be interested in that. But, yeah. The champions has a little bit of extra, like, development, programs that you can get into. You can share some feedback with Blackbaud teams. A little bit of a rewards program in there as well. It's kind of like a supercharged community. If community is a good place for you to connect with, other people using ETAP, Champions is a good place not only to connect with those people, but also with Blackbaud. References, that's when we are looking for people to, you know, to talk about some of the successes that you've had, using the product when, talking to a potential prospective, eTapestry purchaser. You have total control over how often you take a call as well. Alright. Well, next week, I will see, everybody at the, ask the expert session. Looking forward to that. I'm sure there'll be some great questions as there was this week. Thank you everybody who hung out for an extra fifteen minutes on this call. I knew this was going to be a pretty big topic, but I wanted to make sure that I got as detailed as I could while also knowing that, I will probably have more to talk about next week. So, looking forward to seeing everybody at the Ask the Expert, and I hope you have a great rest of your day.