When dealing with volume, each click counts. Our BRC comes back with the ID on them. No need for to search. We expect to be able to type the number and the row populate automatically upon hitting tab. After all the point of batch entry is to speed up data entry.

In our constituency, there are a lot of entities with similar names and we often have to rely on the Constituent ID to ensure we are posting to the correct record. We are a nationwide (US) Catholic nonprofit - now just think of how many St. Mary Churches you've driven past in your lifetime, whatever background you have.

Art Gerstein's comment is lovely but does not seem to relate to this question. The need here is for a column for Constituent ID within NXT, as there is in database view. Words (names) are not adequate. You need unique identifiers to ensure the correct record, and that is a constituent ID. This is an absolute MUST in grid batch entry.

with the absence of the Mail merge, RE users started to turn to a third party Technology Partner that developed the most robust “receipting” solution ever integrated with RE. I urge you all to take positive action by looking at this solution as it may be just the thing your organization needs. It somehow has you input your own Business Rules so you can process hundreds of one type of letter per session, like receipts, acknowledgements, etc.

After you select the RE batch from within this third party solution, you let it process the batch for acknowledgement letters, for example. Once (quickly) processed, it presents a list of the “letters” for approval.

While scrolling through the letters, you can hit the EDIT button and the built-in Wysiwyg text editor so you can change/delete/add text AND it has built-in image management so you can embed images as well as SIGNATURES into letters.

The company made every effort to make it flexible to fit a variety of needs, while making it robust enough to free up time for those processing these documents adding greatly to your organization’s need to control labor and time costs.

the product is called ReceipterPro™ and you can find it in the Blackbaud Marketplace. It won’t hurt to take a look.

Stay Well

PLEASE turn this Cons ID field and the constituent search field into TAB ENTRY, no mouse clicking to get through a whole row in batch if you don't want to touch your mouse. This is really slowing down data entry.

Having the Constituent ID as a separate field from the name in a batch is crucial for our org. We have different staff doing data entry vs double-checking and committing that data. The person checking/committing uses the ID field while checking to confirm correct data entry at a glance without having to click into each record to check. Not having this field forces us to keep working in database view.

We are in a legacy phase - we have 3 or 4 generations OR people with similar names from different families. We visually use the ID field to ensure the correct record is selected.

We need the separate ID fields too, eg for Constituent/Appeal/Package.

The separate Cons ID field is very helpful to double check entry.

DBAs and gift entry specialists rely on constituent ID, and this would be so helpful!

To clarify my idea, I understand that you can search by Constituent ID in the Constituent field. That is not what I am asking for here. We do not want to trigger a search to then have to select a result, which slows things down.

We want a plain text field where we can quickly enter or copy/paste a Constituent ID. On pressing tab or leaving the field, that constituent would then be linked in the batch row. If the constituent doesn't, we would be informed that the Constituent ID corresponds to no constituent in RE.

Please do not for us to search for someone if we know their Constituent ID. Batch data entry should be streamlined for bulk data entry, saving as much time as possible. Wasting seconds by searching unnecessarily for thousands of gifts/day can lead to hours of wasted time.

Hi there,

Our Site ID 8620

Last week, I attempted to create a template for our Pledge batch using WebView. During this process, I noticed that several important fields and options are currently missing:

• Constituent ID (Donor ID number)

• Constituent Code (Parish name)

• Language preference – This is especially important since we have many Spanish-speaking families here in Yakima.

• Reminder option – A checkbox or feature to send monthly balance reminders to donors.

These fields and features are essential for accurate tracking, proper parish identification, and effective communication with our donors. The language option, in particular, is critical to ensure we are serving our Spanish-speaking community appropriately.

Could these items be added to the WebView template, or is there an alternative way to access or enable them?

Joyce Mendoza

ACA Bookkeeper and Database Specialist

Diocese of Yakima

PO Box 2189 (use 98907)

101 S. 12th Ave. Yakima, WA 98902Phone:

(509) 965-7117

Hi all. You can already search for the constituent ID in the Constituent field. You can also use that field to search by name, email, alias, and phone number.

agree completely. When entering constituents for payroll giving for example, it's much easier to paste their RE ID as opposed to searching for

them by name

Agree! This is how we speed up batch data entry for checks, pledges, and one-off gifts.

This would really help! Thanks!

Agree 100%!

100%. Entering gifts and pledges by constituent ID is vital to our gift entry efficiency.