It would also be great if we could change the tribute in the gift batch before approving. We could then change the tribute for Bill to the existing one for William. Now we have to approve the batch, open the gift record, add the correct the tribute and delete the newly created tribute then merge. When we get a push, I have to do this process on 10 or more records a day.

This is also not helpful because we're charged by record band. After 20 years of data, I have many, many empty records I can't delete because there is a gift associated with it. So, they just sit there, taking up space, and we get charged more for it. Lame.

This is why I refuse to use NXT credit card forms and still use Online Express. Majority of my online donations are memorials and I can not keep up with all the duplicate accounts it would create.

Please! This is my only major headache with RE NXT. We are an animal shelter and records get created for deceased pets all the time. It would be nice if we had the option for the acknowledgee to become the constituent instead of the deceased person/pet. This would benefit our org greatly and keep our data cleaner!

Even when it isn't automatic, creating a new record for a tribute that only has one gift is not ideal. If tributes could work more like non-constituent relationships that would make much more sense. We occasionally have people giving in tribute to someone who has no history or connection with us. It would be great to be able to track these types of tributes without having to create a new record related to one gift that is likely not renewable.

YES! This would solve a lot of problems for my organization.

Yes please! This is super important for nonprofits that have suporters who give in tribute of their pets.

YES, please! I work at an animal shelter - I can't tell you how many dogs and cats names have been added to my database. CONSTANT cleaning!

I agree that automatically creating a new constituent record is not helpful and we are running into so many problems with this. I've even had duplicate constituent records created although the person has a unique name and already existed in our database. This flaw is adding more work and makes us not want to use the tribute feature. So far it was easier to handle tributes and memorials before this feature became available. I was told by customer support that this is working as designed but engineers are aware of the complaints. Hopefully something can be done to prevent all these unnecessary extra constituent records.

so much agreement for this. A significant amount of time is spent searching for duplicates of tributes with different name spellings / nicknames/etc. and so many tributes for "my uncle" or "Sadie's dad" that don't need an individual tribute record

This is amazing and honestly we learned this the hard way. This would be a great addition to the tribute module.

This! Everything about this. I have a constituent created today named: My beloved sisters of SHA '86 small but mighty ! It's ridiculous. And we are trying to work within the limits of our paid storage too so additional constituents who will never have another gift attached to them is unnecessary. But I don't want to miss these when we do our Annual Report either. AND I can't see the tribute information in batch in NXT so I have to go back and look at the record and then if it needs to be edited, I have to go to the database.