Name: Ask the Expert About Accounts in eTapestry
Uploaded: 2025-09-17T18:30:41.136Z
Duration: 59 min 56 s
Description: Ask the Expert About Accounts in eTapestry

Transcript for "Ask the Expert About Accounts in eTapestry": Hello, everybody. Welcome to this week's, Ask the Experts session. This week, we're going to be, talking a little bit about, more on the accounts. And there are a couple of things I definitely want to, talk about for certain that kinda came up last week that were also, things that were, I think, people had some questions about as well that I definitely want to, to kind of go over, in a little bit more detail, give a little bit more, context around that. Yes. Hello to Addie, Amanda, and Cindy. Already saying hello and good morning in the, chat. Always glad to see folks, introducing themselves, saying hello to everybody listening in. Of course, during the course of today's session, you are, more than happy to ask questions of your own as I go through some of this stuff. Oh, Laura from, Bern is, Lord, where is Bern? Kinda curious about that. I haven't seen that, pop up before. South Of Fort Wayne. Okay. Great. Yeah. So another Hoosier. Of course, I'm here in Beech Grove, Indiana. Been with, Blackbaud for twenty years. I go back to, E Tapestry before it was part of Blackbaud. So, of course, I'm also here in, Central Indiana, Laura. So that's that's great. Fantastic. Okay. So let me hello, Danielle. Hello, Chardonnay. Always, glad to see people coming in and saying hello, like I said. So, let me go ahead and, pull up my database here. Yep. And you should be seeing my home page here. So a couple of things that I really kind of wanted to kind of get into a little bit more, context around. One of those things was let me go into my account here again. Was the importance of and and how to better utilize the personas. Right? So one of the things I mentioned was if you create a household relationship with two accounts so, like, let's say you have, partners or spouses that you wanna have in a in a household relationship, not only would you go into the relationships and you would create the relationship by going in the new relationship and all of that, but you also put in the household designations. One of the members of the household is the primary, the other is the member. One of the things that I always recommend is that whoever you dignify or assign the concept of head of household or the primary person in that household setting, I always recommend that you create a joint persona. The joint persona is simply there so that you can have the salutations also pull up, you know, the the first names of the two of the two spouses, the the first names of the of the two partners, whatever the case may be, as well as having the long salutation also indicate, you know, mister and missus or whatever the you know, however you're going to, kind of address them in a long citation situation. And then, of course, the envelope citation is a little bit of a combination of the short and the long salutation. But all of this is set up so that one, you have one persona on the head of household account that allows for you to address two people at once. So this is when you're dealing with, like, household groupings in a report or household, household groupings within communications and so forth. So the way that you would end up utilizing that is if you were building a report, we go into the report here and let's say, in our report, we'll use this mailing labels one here, we have it grouped by household and then you select collapse groups. At that point in time, you can have the account name, you can have citation fields, you can have whatever it is that you want to display in this report. But it's grouped by household, meaning that if you have Joe and Jane Smith, they are, related to each other as a household. You have a joint persona set up in Joe's account to say, you know, hello, mister and missus, Smith. Hello, Joe and Jane. However the case is that you want that to be set up. You would be able to start utilizing that first by grouping the report by account or by, household instead of account and then collapsing the group so that if you are, displaying, like journal entry information or whatever the case is, you want to make sure that it all collapses into one line. And when you save and run, under advanced options, you'll see here this option for personas. Now by default, it will always list the primary. But if you click the little pencil icon, you can say I want this to be a hierarchy. And here you can say first, pull joint personas if the accounts have them. So in this case, if you have a joint persona set up in that head of household account, it's going to pull that. Now for anybody who's an individual account, you're just single or, you know, they're not in a household relationship, they will still get their primary persona pulled afterwards because this is only indicating for those who have this type of persona, pull this information. And for those people who don't, you know, just pull whatever their primary persona is. So this is where you can adjust what personas you want to see pulled into your report. And that's under the advanced options on the launch screen of your report. Similarly, in communications, if you have a letter that you want to send out to, you know, to people asking them to make a donation or inviting them to an event or whatever. The very first step under criteria, this is the hierarchy for the personas. So you don't even have to open a special field for this. You would say, I want to pull the joint persona. You select whatever query it is that you're working with, but you would say, I wanna pull the joint persona first. And then under document, options here, you can say group one document per household. So on step one, you would adjust the personas to export. Step number two, you would say group it by one document per household. Deborah, great question. Brings me to another thing that is worthy of showing you. Yes. So how hard would it be to add that joint persona if it is currently not an option in your database? So first step is to go under management and go in to system defined fields. So it's the very first listing under database configuration. And persona types is one of the options here. So when you click on persona types, this works just like a user defined field. You just fill in whatever value you wanna add. You'll see here that I have joined already. You can click and drag these into whatever order you want them to appear in in, any drop down list. And then you would just click save and finish at that point. So that would allow for you at that point, if you were creating a brand new account, it would then give you the option under personas to select the joint. If you go into an account and you say, okay. Now I want to add a joint account, it will be one of the options when you go to the account's persona page as well. So at that point, yeah, you would still have to go in and add the information. But one of the things you could do is you can always pull a query to find out who has a, so, like, if you go into queries. And this would be something that you would probably want to set aside some time for. You could go into a query to find everybody who has, let's see. I believe it's under account. Let's see here. Yes. So I'm sorry. Right here. So you have household relationship as one of the options under the account, menu in a query. You can say, you know, find everybody who is listed as a primary, and that will pull all of the people who are primary, you know, head of household at that point. And then there, you would have the ability to go in and add the information to their joint. Now, another quick tip here for you. Let me see. Do I have a Smith in my database? Yes. So let's say let's say you've now added that. You've gotten a query. You find that John Smith has a head of household, designation. You can go into the personas And now you'll see here his primary persona is the personal, but he does not have anything in his joint persona. That's indicated by not by there not being an asterisk next to it. And when you click on it, you'll see that it's blank. But if you go to the personal, scroll down to the bottom and you'll see a copy button down here. In the drop down menu, select the, the joint persona and click copy. It will say, you know, does it gives you a little warning that would say, you know, just to let you know, there may or may not be information in that joint persona where you're moving this information to. If there is information there, it will override it. But if there isn't anything there, it just fills in the blanks. And if you click yes to this, it will now take you to joint. You'll see that there's a little, asterisk there. And instead of having to go in and fill in all of his other fields here, you can just now fill in the information that is, that's missing there. And at that point, now you have filled that in without having to go in and fill in every single field. So there are some shortcuts there. Yes. You would have to fill in the joint information, but there are some shortcuts that you can work around that. You can you can pull all of the people in a query that are a primary member in a household, and then you'd be able to, then be able to work from that list. Copy over the primary persona. Fill in the the citations. Save it. And now when you go into, John Smith's account here, you go into his personas. You'll see, okay. Well, here's his personal. I can click on his joint. And now all of the address information is the same, but now the the salutations are lined up. So little bit of work, but not terrible. There are some shortcuts in the process. Now another thing that I want to also talk about, because this is a big one. And that comes to how you deal with the user defined fields within an account. So, like, when you're looking at an account, it's like, okay. Well, you know, you go to a persona, you'll see that there are a couple of user defined fields down here for company and job title. You'll see that if you go into define fields, there are a lot more fields. So, you know, what is the appropriate place for these user defined fields? Oh, Danielle, adding in an additional persona would only duplicate the information if in the report, like, on the launch page where you say, you know, I want to, edit which persona shows and you say, show all personas, that will be the only time that it will duplicate anything that you wouldn't normally see. So just adding a persona to an account just keeps it one account, but now there are two different addresses that you can pull from and work with. So the report is the only place where you would have the option to say, I wanna see all of the personas that this account has. So what is the appropriate thing or where is the appropriate place to place your user defined fields? Because a lot of people because when you click on somebody's account, the first place that a lot of people wanna go to are the personas. It's where the address is. It's where the contact information is. And a lot of people see that as a way to say, okay. Well, we don't. If this person doesn't wanna receive mail, we should put something there on the persona that says as such. That is not what we would recommend. And for somebody, like I said, you know, I spent twenty years working with eTapestry. I've I've heard just about every question and every problem come across, in my time and support the first half of that twenty years. And one of the biggest things that ends up happening is that people either will place user five fields on too many pages, the same field on too many pages that is, or they place the field in the wrong spot and it ends up creating issues for their data keeping. So let me try to explain this a little bit more succinctly here. When you go into a user defined field and let's say we go into base and we're going to create a new field, we'll just call this, test field number one. And we're gonna make this a text field. It's going to be, various options in a drop down menu that we want this to appear. On the very next step is the all important field application. Now, and for those who may be, listening from overseas in Europe, this is also where you have your consent options that are available to you. That's part of, EU and, mostly a lot I think most of the European countries have adopted the consent laws. So, but one of the things here is under help, not only does it describe what each of these three different categories technically are and where the fields would appear if we check constituent or if we check, personas or if we check transactions, whatever the case is. But also down here there's an asterisk that says, in most cases, it is recommended that you only apply your field to one area of your database. And let me show you why that is. So let's say this field, we we get a little crazy and we say, okay. I want this to show up in constituents. Of course, I want it available for transactions because, you know, whatever the case may be. And I want it to appear on personas. Now my thought process is if I check it in one place, it will appear in all of those places. So that's gonna be my process. I always wanna be able to see if they have a selection in this field. Field attributes will skip this because we don't need it to be required or anything else. But we do want this to be a drop down menu. And under add value, we'll have example one, we'll have example two, and we'll have example three. And we are going to click save and finish. Now if I go back to my account here, and now I'm going to fill this field in for this Geoff Arbuckle character. Right? So I'm gonna go into the personas, and I'm gonna say, alright. I want example two to be checked off in Geoff account so that I always know regardless of what page I go to what his selection is for this field. K? And when I click save and edit oh, we're not gonna do that. We'll just leave that as not duplicates. That was from the the example in the webinar. Here, now we have I come down here and yes. Okay. Great. Example number two is selected. Now I'm gonna leave and I'm gonna, you know, go and do some other things. And I come back to this guy's account. And I say, okay. What's going on with Geoff here? And instead of going into the personas, I come into my account and I say, let's check his defined fields. Okay. So I see, okay. He's an individual. He's a staff member. He's a former board member. All of this stuff. Wait a minute. There seems to be something missing here. Wait a minute. Didn't I fill in test field number one? Let me check his personas here. Wait a minute. I did. It so one, there's one problem right there. Right? I go from one page to the other, and it did not remember or did not know to send that example to to be the filled in selection under the find fields. Similarly, if I were to fill it in here, so let's say we remove this and I fill it in here. So it's not on the persona page, but I fill it in here and I say save and go to personas, it can't communicate that back to the other page. Those pages are independent of one another. Now eTapestry is smart enough to do some things, but it's not smart enough to be able to say this is the same field and the purpose behind the user that added this user defined field is to carry this over into every, place that it shows up at. Similarly, if we made a selection here in the persona so here are my primary persona, my personal persona. I have example two filled in. Let me go over to my joint persona. It doesn't carry it over there either. So the reason why we only recommend that one place gets filled in first is that if you have it in multiple spots, it doesn't carry it all the way over, which can be a little problematic when you're doing a query because you may think I'm gonna query on this user defined field from the personas, but it's always being marked in the defined fields page of the account. Or some are marked in persona and some are marked in, defined fields, you're going to have incomplete data in your query. And that leads to the other problem that it creates is that if you have multiple users utilizing the system, some people may come in here to the persona and fill in the field here, not realizing that it can also or should be filled in on the define fields page. It leads to inconsistency. And when you have inconsistency in the data, you have inconsistency in your reports. So that's why we always recommend that you have it only in one place. Now, if you do notice, and I think, Cindy, you're you're bringing this up here. You know, before you arrived at your current job, they put mailing status in both persona and constituent. That is the most common one that ends up in both places because what I typically say is when I'm asked what information should be added to the personas as user defined fields as opposed to the defined fields page. My answer always is, if you're adding something to the personas page, does it have something to do with how you are contacting them? So, like, for example, company and job title can be put on an envelope. Maybe maybe you would have a contact availability in, you know, because each persona may have a different contact availability. If you have my business information, if you have my personal information, there may be two different times in which I would want you to contact me there at those two different places. But when I say, what does, you know, does this field have something to do with how you are contacting someone? That doesn't necessarily mean if you are contacting them or not. Because some people will say, don't send me an email or don't send me mail. I will always make the, I will always make the, the the donation that I'm that I plan to make every week, every month, every quarter, every year. I don't need you to send me anything, you know, save save the money on postage or whatever. That is a descriptor of the account. So it is saying, this person does not want to receive mail period. They are always going to make their donation. They're always going to be now, of course, that doesn't count like tax stuff. But, you know, like, solicitations and invites to events and stuff like that. Maybe they don't wanna receive stuff like that. So you can reasonably say that it doesn't matter which persona you are sending to or it doesn't matter how many personas that they have, how many different addresses you have of them. It is reasonable to assume that they don't want you to send them mailings to any of those addresses. So that becomes a descriptor of the account, which means that is the defined fields page of the account here. So mailing status would be here, not on the persona. Because let's say, you know that somebody is going to, somebody has given you their home address and their business address. But then they say, I don't want you to ever send me anything to my business address, but it's just a secondary email address for whatever reason. If they adamantly don't want you to send something to their work or to their home and send everything to their work, I wouldn't worry about even putting the home address into the or whatever that address is that they adamantly don't want you to send to. It's just extra it's extra data entry that you really wouldn't need at that point because, yeah, maybe maybe you know where the person works and you put that in as a business persona. But if they're if you're never gonna communicate with them that way, there's no purpose in having that in the system, really. So when it comes to contacting people, it is good to have some fields in there that would be descriptors as to where they work or what their job title is for the envelope or what an attention line would be for a, for a mailing or something like that. But, preferences, you know, preferred communication method, the mailing status, those are really more descriptors of the account as a whole. So that I would put on the define fields page with your other attributes, like they're an individual, they are a past board member, or, you know, their favorite color is blue. That's always my favorite example, is to have the favorite color in there. So that is where, you would do that. Now you will notice that each persona has this opt out settings. That is for mass email. All mass email that you send has a an option to opt out. Now this opt out settings is specific to, the basic mass email. If somebody opts out of basic mass email, eTapestry gets that information and it changes it to this opt out of all mass emails. If you send advanced mass email, it may say not opted out, but that's being managed and handled by our partner, Delivra. And there are reports under the standard reports that will that will show you all of your opt out people and when they opted out as well. Yes, Daniel. You absolutely could do that. Now again, that would be a defined field that you would set up and I would set it up on the defined fields page. So, yeah, you could certainly like, let's say test field number one is, you know, the actual interest email or something. Or you could potentially put it into mailing status. So, you know, like here, I have a no newsletter option instead of do not mail or do not solicit. So, you know, I could say, oh, you know, do not solicit, which means later you could create a query to find anybody who does not have that selected. And you can use that for other mailings, it'd be it, you know, newsletters or whatever the case may be. So, yes, you can absolutely create a field or include that into any of your other statuses as well to be able to say, okay, this is going to be specifically targeted to people who want to receive all mailings or just, an athletic, email or, you know, newsletter or just solicitations or whatever the case may be. So, yeah, you can certainly set up a field that would do that. And that would be a good field to have, especially if you know that there are segmentations like that with your with your folks. But again, I would put that on the define fields page, not on the persona, just because the define fields page would be where you are including, excluding people based on their preferences and attributes. Alright. So those were two key things that I definitely wanted to talk about because, now if you ever run into a situation where you say, okay. Well, I've got stuff that is in the wrong place. I don't want it to appear, you know, on the personas anymore or I want to move it from the persona to the to the define fields page. There there is a way to do that. You can do that with, this mass update option, where you can say, like, you can create a query for every, for every persona or for every account that has example two marked on their persona page. And then say, okay. Now I want it to be marked on the defined fields page. You create that query. You come in here to mass updates. You can say, update existing accounts. You select your query, you say assign, and you come down here and make your selection for that field that's going to be filled in with this mass update. You run that and then afterwards, you can run a second mass update to go into ex update existing personas, use the same query, say, remove, and then you can come down here and say, remove this selection from those accounts as well. And then once you do all of that, mass update options there as far as getting that information moved over to the proper place, you can come into, the defined fields at that point and very easily say, now, I only want this to appear on constituents. You can then save it and then there you go. It will, it will only then appear for new accounts or accounts that don't have that field filled in on the, constituents page. I currently have accounts linked via relationship, employee and employer, but they really are the same person. So in something like that, Michelle, I think it would be okay. So are you saying that the employer the the contact person that you have, like, on their persona is the same as that additional account that you have in the relationship? Is that what you're saying there? Yeah. So if you merge the into the existing account in that sort of situation, to a business persona. So there let me pull up one of my accounts here. We'll use John's account. You go into the account settings, and there's a merge role button here. And what you'll do here is you'll see if you can find their business accounts. So let's say, John Smith and a b c organization are really just I mean, it's John Smith is my contact for a b c organization. I don't really need John's separate account. You can click on a b c. It will take you in here and it will say, okay. John Smith is the duplicate and a b c is the target. That's the account that everything is moving into as indicated by the arrow at the top. You can come down here to persona and you can say move the persona to the business persona, specifically. Merge only if the addresses that are displayed are the same. Because when you move the persona information from the person's account into the new account, you do have the option to either merge or replace. Now if it already has all of the business persona if if the business persona is completely and totally empty and blank, you can just say merge. That's fine. If it is already filled in, you can select ignore and it will just keep the original information. If you select replace, keep in mind that anything that is filled in on both accounts will be replaced with the information here from John's account. So the the the duplicate account. So just keep that in mind that it would replace anything that was already filled into the business account. But, but, yeah, you can select exactly which persona you want that information to move to. And it's done right here. Now as far as, you know, any other personas, like, if you do have anything, it will list them as well, but you don't necessarily have to do anything there. You can just say ignore on those. But when it comes to, like, journal entries, all of that will transition over from the original account to the target account. So all of that will move. Journal entries are not the only time journal entries are mass removed from the system is if you delete an entire account and you say, yes, I want to go ahead and delete the account, all the relationships, and all of the journal entries within. That's the only time that that's ever done on a mass basis. If you do a merge, it just pulls it all over. Will they keep their name under the business persona? Now that is one thing. So the account name would not necessarily transfer over. So but what would would be their citations. Their citations should move over. But in the journal, no. It would just the journal entries would then be owned by the business account in that case. So, like, if if John Smith was the contact person, was making the donations for ABC organization, that really wouldn't change anything because ABC organization would be the taxable person. But in the business persona, if you move that information from whatever his persona was over to that business persona within the business account, it will it will pull over the salutation. So his name would still show up. It would just pull over the salutation. So let's see here. Mailing status so Alexis asked, mailing status versus attribute. If I want to identify my young members, should I do that in both fields so I can segment for email or snail mail? Or is one place one place will be plenty fine. Just do that within the accounts, date, the the fine fields page. That's where I would identify them as a young member. And then when you're building your list for snail mail or for email, that would be the that's the only identifier you would need in that case. So if someone is an employee and you want their account to be under the company, this would be a joint account? Not necessarily. So when it comes to business accounts, Kelly, the big thing there is to know so, like, let's say you're gonna create an account. In this case, we'll we'll use my a b c organization account here. So I have a b c organization. They make donations. They, you know, they are sponsors for events and so on and so forth. In this case, when I create the account and I have the business information here, I say, okay. Well, okay. Geoff is the contact person for this account. So I will put his name and information into the salutation fields. I will also make sure that his job title and I will go ahead and use a b c organization in the company field as well. Just so that when I build out a mailing, I would have, you know, ABC organization as the company on the front on the first line. Second line would be, you know, mister Geoff Arbuckle. I can put the title there or I can put, or I can put the title in the third line or whatever the case is. And all of that would pull through. Now this wouldn't be a joint account. This is just the business persona of this account because it is a business. And because you know the contact person there and the person that would always be, I be, approving donations to your organization, you would put that person into your salutation so that you can directly address him or her on any mailings. So there are some, so that would be one thing to take into consideration. Now, of course, you could have contacts at businesses if they all have different purposes, in communication to your account, or, and to your organization that is. You can have them in as separate accounts related to the business. It really kinda depends on who you are working with within the organization or within the business or organization that you're contacting and who's making donations. Not many people that I know will have more than maybe two or three people ever that they will talk to at the organization. Most of the time, it's going to be just one person at that company slash organization. So it really would come down to who is it that you reasonably will be communicating with, reasonably be working to gain a donation from, then that would be either a separate account that would be linked to the business so that you can just directly communicate with that person, or they would be listed as the salutations in the business account so that you would then be able to address an envelope appropriately to get to that person. What if you deal with multiple employees at the company? Would I add them to be a joint I would add them as individuals with business personas that would then be related to the, to the company's account. I wouldn't put them in a household because if you ever work with them personally and you learn about their home household, you would want them to be related to their people. Let's see here. Is there an article that talks about what you mentioned regarding not having UDF and personas and why, that it doesn't populate other that is that might be in the knowledge base. It might be listed as, an article about, why is my user defined field not showing up, or something like that. I would search the knowledge base something like that. Why isn't my u user defined field appearing in a person's account or something like that. That, there should be something there that would explain the pitfalls as to why something wouldn't show up like that. So yeah. Sharon has a, great question here about soft credits. So yes. So when you are creating a, gift for somebody so let's say you come in here to their journal, you're creating a gift of, you know, whatever it is, $100 and, to whatever fund. And over here I'm just gonna put that in as cash so I don't have to fill out anything else. Over here under tribute soft credit matching gifts, I can select who the soft credit account would be. So we'll just say that you talk to me. I'm in the contact at ABC and, you know, ABC made the donation, but it's thanks to my relationship personally with your organization that the company is making a donation. So we can add me in there as the soft credit person, Put it in for the full $100. And when you save this, now what ends up happening is is that both accounts will receive a journal entry. ABC organization has a gift now in their journal, and my account now has a soft credit. When you are doing a thank you letter or you're doing a report and you want to be able to pull what that person, or what the soft credit person was on that, one thing you can do is when you are let's let's do this with reports. A little bit easier to see in reports. All those the same category when you're adding the field to a to a letter. So we do account name, we got our address line, all of the other stuff that you would normally pick. Then you would have your received for the donation that was there. But you can also go into journal fields, and you can pull in things like linked soft credit. Let's see. Where is it at here? Links of credit account name, links of credit amount. So that would pull the information regardless if you're doing a a report like I'm showing here, or if you are wanting to add these sections to a or you wanna add these merge values to a letter, they're both both places. They're found under journal entries, and you'll see linked soft credit amount, linked soft credit account name. Those types of fields can be used to pull over that information. Now if you are thanking the soft credit person for having the influence over the gift, that would start in the query. And what you would do in the query is you would create, of course, you would have your journal entry date so you can find the actual date and entry. But under journal, you can pull in, actually, you can do this under sorry. You can do this under commonly used fields. Do use, journal entry date and journal entry types, and you can pull in soft credit without hard link. So when I do this, we'll say, for today. So you'll do, you know, journal entries as your data return type, soft credit without hard link from journal entry types, journal entry date, whatever date range you want. But when you do this now, when I pull this, there's my soft credit. Everything else in queries or in, communications and reports, again, pretty much the same thing here, but this time instead of pulling the linked soft credit name, under journal fields, you'll find linked hard credit. So I can say, okay. Well, here's the, you know, here's the person that was actually made the donation. You know, you can put in linked hard credit account name, linked hard credit amount. You can also pull the soft credit amount to show what was credited to the soft credit. In this case, would be the soft credit. The person who showed up in the soft credit query. That's what I'm trying to say. So hopefully that, that helped out there, Sharon. There should be a knowledge base article that will kind of go into some of that, like, how to find the soft credits. But, yeah. It's regard whatever another tip that I'm not sure everybody realizes, but if you're creating a report or if you're creating a thank you letter, these categories are exactly the same. The only difference is I don't think they're sets in the communications, but, like, commonly used fields all have the same fields in them. Account fields, summary fields. All of this stuff is also available as categories when you are adding a, merge value to a communication. All of the same fields appear. From chair okay. So you, you received donations from charitable organizations. So when you are entering that, the hard credit, the actual received amount should go to who wrote the check. Soft credits would go to all of the people who contributed or the person who contributed to that, you know, who gave to the RMD to be given over to you. So, like, the, why can't United Way is an excellent example, of the one that we always talked about the most in the past, in support. You know, United Way, you know, a lot of organizations work with the United Way. A lot of people donate through the United Way. And sometimes companies will make contributions from their employees to something like that. United Way cuts the check to the organization. So the United Way would then be the hard credit, and then they usually will or they should provide a list of the people who made up that donation or, you know, who was connected to that donation. And then those people were always put in as soft credits. So that would be, you know, the whoever wrote the check should be the hard credit because ultimately, you know, you would notify United Way, here's the, total contribution for the year. United Way is telling all of the individual donors, here are your tax credits for that year. Yes. Exactly. Exactly, Michelle. You wouldn't have to worry about doing the tax receding because that third party is already handling that to the individual donors. Yeah. Same thing goes if you're getting a company check. You know, it's like all of our employees are donating to this organization through a big company contribution, the company contribution would be the hard credit because it's coming from the company. But the individuals, the employees can then be put in as soft credits. In the past, when entering address information, the company name was added in the address field. Thus, company name line one come is there a way to easily remove the company names from address line one? Deborah, you could potentially do that with an import. The only real thing that that is at play there is if you ever go into the management and click on the address finder, the The USPS or or postal services in various countries don't like when the address first line of the address is a business. They would prefer that not to be the case. You could potentially export your businesses, clean it up in an Excel file, and then reimport it so that it then overwrites the information appropriately and places everything into the appropriate fields. That's one way a lot of people work with that. And that would probably be my recommendation barring that it's not like, you know, a 100,000 businesses or something like that. But if if you're dealing with hundreds of businesses, then that would be you know, even even a couple 100 wouldn't be that bad to to work with. Alright. So we are getting down to the last ten minutes or so. Next month, I will say this. One thing I'm going to talk about, is one of my favorite tricks inside the entire database. And it's something that I think people don't realize how flexible it is, but I'm going to be talking about journal entry contacts. Most of the time people think, oh, contacts. They either think, oh, that's what we call our accounts or our constituents. They're our contacts. Or some people think, oh, no. This is the this is the journal entry in which you place all of your notes about when you communicated with somebody, sent them an email, or sent them a letter, or had a phone conversation, or had lunch with a major donor. It's much more usable than that. It's much wider in terms of what can be used there. And I I'm hoping that some folks who maybe have bigger ideas about maybe getting into 2026 with a new approach with how they're going to track certain pieces of information, certain, ways that they work with, be it events or donors or volunteers. The contact entry is going to be a major, major benefit to you. So just to give you a little bit of a tease of what to expect next month, might be one of the shorter sessions that we do, but still gonna be scheduled for an hour. But we'll just see, where we go from there, and then we can, then we'll, of course, have the ask the expert after that to, to kind of go into a little bit more detail or or answer some additional questions around that area. So, hopefully, I'll see most of you there next, next month at that. I think it is if I'm not mistaken, it's October 8, I believe, is the session. It's either the eighth or the or the, fifteenth. Either way, it's one of those dates. The, the, let me pull up the let me pull up my eTapestry page here so that we can double check that. Yes, please. Excuse me. Oh, October 15. It's October 15 is the eTapestry's hidden treasure, the journal entry contacts. So, yeah, that's gonna be my, that will be, I think that'll be a fun little, conversation because I think that is something that is definitely going to be something that people will get a little bit better idea of maybe we can track some things that we didn't think or we didn't know how to do before. Put the link there in the chat here. Chardonnay, for the purposes of verification with physical records and inputting them, is there a way to, search specific gifts? Not really in terms of, like, the search features. Like, if you go into, find account or if you use, like, the little quick search at the top, there's not really a way to utilize actual gift information. You could potentially do something like that within a query. Now you could set up one query that is always used for searching, you know, any type of entry. So, like, let's say, you know, you you just set up a query that will say something like, gift search or something like that. You can set it up to be data return type journal entries. And then you could come down here and you can say, okay. Well, I know that the, you know, I know that Geoff made this. Yeah. I know that Geoff Arbuckle made this gift, and I know basically when he made it. So you could use the the commonly used fields of journal entry date. And you can say, well, I know it was sometime in the last ninety days. And you could use that as the, as a search feature. You just do save and preview. You could do that and I mean and of course with a query, you would be able to expand that a little bit more because you could say, oh, I know it's, specifically a payment to a pledge, you know, or I know that it was, a specific note that I entered or something like that, you could narrow it down a little bit more by using other criteria like the journal entry types or whatever. So that would be my recommendation on that. You know, queries can get as advanced or as basic as you want them to be. I know some people probably heard my answer to your question and cringed a little bit. It's like, oh, no. Not another query. But you wouldn't have to do a new query every time you wanna do a search. You would just come in here, take out the fields you don't need, add the fields you do need to find that specific gift or transaction or journal entry or whatever. K? Alright. So in the last few minutes here, I've got my normal spiel that I need to go through as always. You know, you always have the resources. I've already mentioned that the knowledge base, that's just kb.blackbaud.com. That's a great place to look for some additional tips and tricks around, like, entering information into accounts or creating user defined fields. Why aren't they showing up? So on and so forth. Of course, there's always, Blackbaud University and our customer support team that you can always reach out to. And then the community is a great place too to find out how others are potentially using the, the eTapestry program and maybe even be able to, pick their brains a little bit as to what might make things a little bit easier for you too. I'm always looking for people who might be interested in joining one of these programs, particularly the Blackbaud champions or the reference program. Champions is a great way to, work with members of the Blackbaud team as well as with one another. It's kinda like community plus, if you will. There are some development opportunities within that. There's also a little bit of a rewards program that you can, take advantage of. If you're interested in that, let me know in the chat. Or you can, go to blackbaud.com/blackbaud-champions and, get some information there as well. Reference program is where, you know, we're we might be talking to a perspective eTapestry customer, and, they want to find out maybe how other people are utilizing the system or how, you know, what are some of the things that just what are some of the things inside the system that might help them decide whether or not they would like to go with eTapestry or a different product? You can have complete and total control over when you accept a phone call. It can be, however often or as, or as light of a schedule as you would like it to be. You can always, you know, say, yes, I'm available or no, I'm not available. And, we always, are looking for folks who would be, willing to share their experience. And to spotlight your success, now this is one where you could potentially participate in a, in a webinar like this where, you know, maybe you and I would, have a conversation about something that you've been doing or something that, you would like to share with other folks that you've been able to do successfully. You could also potentially write a blog in our community as well. But if you're interested in any of these, please, you know, feel free to, you know, let me know in the chat or in any of these webinars, and I'd be more than happy to, put you through the nomination process there as well. Thank you so much for attending. Alexis, I hope this was helpful to you and Kimberly as well. So happy that, people have been coming to these, webinars on a monthly basis. Again, you will get a link to the recording of this in about twenty four hours. So, feel free to rewatch or go through anything. Again, if you have any questions, you can always reach out to customersuccess@blackbaud.com. And, they will be more than happy to help you with your, with anything that you have questions about or struggling with, get you to the right place if need be. We're always there to help you out. So thank you so much. I hope you have a great rest of your day, a great rest of your week, and I look forward to seeing you at next month's sessions.