Rock U - Reporting - Reports

Transcribed Video Content

Handing a leader a raw query is no way to answer their question. Reports take data views and put them in a structured format that's easy to sort, filter, and export, making finding the right info easier for you. So let's find reports. We'll simply go to tools and then up to reports, click on it, and we have some categorization here. You can add top level categories, but we have a report already added called adult member and attendees. So let's edit that and look into it. We gave it a simple name and description. Descriptions are really nice with reports so that anyone else who sees this report knows exactly what it's about. We have the category set as organization. You can also pick to sort things in this report, and you just pick one of your fields and whether it's ascending or descending. And what's important is picking what this or what entity this report applies to. And based on what you pick there, you can select a data view. So right now we're showing adult member and attendees males, but we can flip this over to adult member and attendees. We can also limit the number of rows we get back. We can add some communication merge fields so that based off of the list of people we get back, we can make sending bulk communications easier. You can also add a query hint, and this can improve the performance of the report. Then we're just gonna close this. We have three fields added. Adding one is super easy. And, again, these are just rows that come from or these are different columns that come from the actual different rows that you get from a data view. So we're getting the people from adult member and attendees. We're displaying their person name, and there's so many great settings for a lot of these fields. , it's easy to name it exactly what you want to. For the person name, we can select to show it as a link so you can go straight to the person's profile. We can pick the order that we display their name in. Also, we have an email, we have an email field type here and age, but there are so many other field types you can add based on the entity and you can just really make sure that everything shown here is the info that you wanna see. And we can even do some advanced field types total giving, which is super helpful. We can pick accounts and we can pick how we're calculating this giving over what date range, and this will just automatically update as time changes, combining giving and using analytics. So that's really nice. And for all of these, you can pick whether they're shown in grid, and I'll save here and show you what that means. If it's shown in grid, you'll see it here. If not, it would mean it only shows up when we go to save this to Excel or something that. But we immediately get this great list of results based on what we've set this report to show, and we can take quick actions on them, and we can go straight to a person's profile just get that info we need. Now a couple more things I wanna cover real quick. For fields, it's great to know what you have available to you so that as you get requirements or you're considering whether a report is the right tool for the job, whether or not it is the right tool. And for people, there's so many great things name, email, phone, attributes, campus, total giving. For a group, you can get the group name, attributes, member count, location, participation rate, and much, much more. So look into those. And something to note is that a Lava field can format or combine any field you've already included. And, again, reports work for any entity type, not just people or groups. Then, we said, a field can be hidden from the grid, but always included in the export if you don't pick to show it in grid. Then the lava field is a special one you can add to a report, and this field type allows you to take information that we got back from, the data view and a field that we've selected in the report, then change what the output looks . So in this case, we'll just show a check icon if a baptism date does not equal null, meaning someone has a baptism date. That's simply an attribute we might store on a person, And it's just a nice way to make your reports look better and make them more flexible. Reports give your data views a friendly face that anyone on the team can read. You can create many off of one data view and your staff has something to run whenever they need an answer.