Elizabeth Anders
My feedback
19 results found
-
2 votes
An error occurred while saving the comment -
0 votes
An error occurred while saving the comment Moving the toast notifications to the middle is helpful although I still need to wait for them to clear out sometimes while working with records. If you added the formula names to the Activity History tab, you might be able to remove/reduce the toast notifications or give them shorter display times. Just a thought.
-
4 votes
-
13 votes
An error occurred while saving the comment Have you tried creating a custom Data Queue tab? We have the ability to create up to 4 custom Data Queues that allows you to include formulas regardless of integration source and put them in whatever order you'd like.
-
1 vote
-
Send to a specific triage bucket based on a Mailchimp status field results returned during matching.
1 vote -
3 votes
An error occurred while saving the comment An update on why I think this is important. I define duplicates as multiple records having all the same data fields in the formula except the OC record ID. This means if I have multiple gift records from a single donor, they should have some other piece of information that’s different so will not appear as duplicates, but if everything is identical, I consider them duplicates and those are the ones I’m usually deleting. I do this because I don’t want to get in the habit of sending the same thing multiple times. Especially since eventually I’ll get near the Blackbaud API-call threshold and I’d rather not get extra volume charges from them. If I had a Dedup button along with the Delete, Reprocess all, and Send buttons, I’d be able to have the computer removed the duplicates which is a huge time saver especially if I’ve been away from work for some reason (think vacation or medical leave).
An error occurred while saving the comment As my coworkers and I work in RE, performing maintenance, global updates, and the like, I'd like to be able to dedup records within an OC formula triage bucket. I understand that sometime records may look like duplicates but aren't (ie, a donor giving more than one gift to one of our team challenge appeals).
If all the data fields mapped in a formula are identical (which would not be the case in the example above), then deduping would greatly reduce the number of records that need triage review. I don't care if the deduping is an automatic function when reprocessing records or is a separate action selection (similar to Delete All, Reprocess, Send Page or Send All).
-
1 vote
-
3 votes
An error occurred while saving the comment Have you looked at participant attributes? I've used them to track some information specific to an event (like how many tickets they purchased of which type for our annual on-site visitation tracking). They have the added benefit of being available in queries in my CRM database (Raiser's Edge).
-
11 votes
-
6 votes
-
3 votes
An error occurred while saving the comment I think of this in terms of records instead of users so that it doesn't matter what type of formula is running but I too have situations where there isn't a match between two software packages and I don't want to add new records if they're not warranted. Just being in one package is often not reason enough to add them to the other.
-
2 votes
-
6 votes
An error occurred while saving the comment It would also be nice to be able to adjust the column width. Some of my Error Reasons are rather long. Is there a way to make the column wider so I can see more records on a single screen? And/or is there a way to not show suggested resolutions as that’s what’s making them long?
-
2 votes
-
0 votes
-
5 votes
-
1 vote
-
2 votes
Wait! What?!? I currently have a formula that does just that.
I have a primary match criteria on email address and multiple secondary criteria (first/last names or a custom id or RE constituent id). Then on the routing screen I have New Records (no records found based on my match criteria) are routed to ready. Also, 1:1 matches that match on email address and RE constituent id also route to ready. If it's a 1:1 match for any other criteria, they end up in the 1:1 match bucket.
What am I missing?