Week of November 2

The new gift entry grid is in staff testing

This week the new grid picked up department and project codes, Gift Vehicle, a Refresh batch button, frozen headers, a pinned defaults panel and saved defaults. Gifts in Posted batches are now locked for everyone. Staff-entered gifts and memberships no longer trigger the automatic acknowledgement, welcome or renewal thank-you emails. The gift data behind the reports was cleaned up, and the renewal email workflow is built in the test copy of Salesforce, with a test with Laurie set for Monday.

146 Gifts given a fund Older 2026 gifts that had no fund now have one, most of them Membership Dues
181 Duplicate 2025 gifts removed $10,170.40 of gifts that had been loaded twice, 156 of them membership dues
3,865 Posted batches locked Batches already sent to Sage, now protected from changes
34 Older batches to decide on Dated July 3 to August 12 and still marked Ready to Post
Gift Entry

The new gift entry grid

Everything below is live in production in the new grid, which staff are still testing. The grid requests from Thursday’s call are all in.

Defaults panel stays at the top

Live November 6

The batch defaults panel stays pinned at the top of the page while you scroll down a long batch.

Gift Vehicle

Live November 6

Gift Vehicle can be set in the batch defaults and on each row. It is set to fill in from the payment method: Donor Advised Fund gives “Donor Advised Fund”, and IRA / QCD gives “IRA Distribution”. I’ll check it on the first real gift of each kind entered in the new grid.

Safer saving

Live November 5

Each gift now saves together with its acknowledgement status and Department in one step, so nothing is left half-saved. A negative amount can’t be saved. The Department follows the fund when the fund changes. The grid warns when a batch’s default gift date is from an earlier day. An acknowledgement already sent can’t be queued again, and a batch closed by someone else no longer takes new gifts.

Add membership never emails

Live November 5

Adding a membership from the grid does not send the welcome or renewal thank-you email.

Send letter only flags the gift

Live November 5

Checking Send letter now marks the gift To Be Sent so it shows in the acknowledgement queue. No email goes out from the grid, and letters are reviewed before they are sent.

Refresh batch

Live November 5

A Refresh batch button reloads the batch’s rows without reloading the page, so the batch stays open and the defaults stay set.

Frozen column headers

Live November 5

In a long batch the column headers stay in place as you scroll down. Donor and Amount stay pinned when you scroll sideways.

Saved defaults

Live November 5

Each batch remembers its default settings, separately for each person. Reopen the batch on the same computer and browser, even after closing it, and the defaults come back.

Department and project codes

Live November 3

Each gift carries a Department (required; filled in from the fund when the fund has a Sage department, otherwise chosen by hand) and a Project, using the lists Laurie sent. The Sage export now takes the department from the gift. Department 2000 now reads “2000 - Stewardship”.

Amount next to Donor

Live November 2

The Amount column now sits beside Donor and stays pinned, so each gift can be checked at a glance. On November 3 the gray text in the grid cells was also corrected.

Sage

Posted batches are locked

Live November 5, and since that evening it applies to everyone, administrators included.

Gifts in Posted batches have already gone to Sage, so their Department, Fund (including fund splits) and Amount can no longer be changed. A Posted batch can’t be un-posted or deleted while it has gifts in it. Campaign and Source Code stay editable. The lock works on the gift page and in both gift entry grids, and staff see a message to use an adjustment batch instead. Open, In Review and Ready to Post batches work as before, and refunds still work.

All 3,865 Posted batches are covered. Corrections to a posted gift now go through an adjustment batch.

Automatic email

No automatic thank-you or welcome emails from staff entries

Live November 5.

Gifts and memberships entered or changed by staff no longer trigger the automatic acknowledgement, welcome or renewal thank-you email. This covers new staff accounts too, with no setup needed. The change applies only to staff entries: online gifts, joins and renewals are set up to keep sending their confirmation emails.

Planned: I’ll move the online automation to a dedicated integration account, kept separate from data entry.

Data and reports

Cleaner numbers behind the reports

What changed in the gift data, the reports and the Sage export this week.

Gifts with no fund

Updated November 2

146 2026 gifts with no fund were given the right fund, most of them Membership Dues, so reports that group gifts by fund now place them correctly. Gift totals did not change. 6 2026 gifts still have no fund. Refunds now copy the original gift’s fund, so a refund no longer creates a gift with no fund.

New reports

Live November 2

Ack Letters Still To Be Sent and Tribute Notifications Not Yet Sent are in the Acknowledgements and Tributes folder. Membership Raised This Year is in Membership Reports. On November 3, the gifts on the acknowledgement report with no entry channel were marked Import.

2025 membership duplicates

Updated November 3

181 duplicate 2025 gifts ($10,170.40), 156 of them membership dues, were removed. The 2025 vs 2026 membership report is on hold until the remaining 2025 gifts flagged for review are checked.

Web gift dates in Eastern time

Live November 4

Gifts, joins and renewals made online in the evening are now dated in Eastern time. Earlier evening gifts were moved to the correct date and to that day’s web batch. Totals matched before and after.

Sage export

Built, not switched on

The export file now has the Batch Total column Skyfin asked for. The nightly send is built, but its settings and schedule are not set up in production yet. Before it goes on, the 34 older batches dated July 3 to August 12 that are still marked Ready to Post need a decision, because they would all go out on the first night.

Member portal

Updated November 4

A missing 2023 dues payment was loaded for the member whose portal looked wrong, and that member’s membership dates were updated to match. The two portal display issues (a fixed “Started” date and a gift list that shows donations only) have been sent to the portal vendor.

How to

Refunding a gift in Salesforce

1Open the engagement.
2Set the status to Fully Refunded and save.
What happensA matching negative engagement is created with the same fund, so the two net to zero in reports. It goes into that day’s refund batch automatically.

Still to do from Thursday’s call: move the status field higher on the engagement page so it’s easier to find.

Coming next

In progress

Mon Nov 9
Renewal email workflow

Built in the test copy of Salesforce, not yet in production. It takes members expiring August through December and sorts them into three lists: Remaining, Removed and Needs review, with a reason on each one (no email, already renewed, duplicate, opted out, odd expiration date and so on). Laurie can remove people by hand or by pasting a list of emails or member numbers. Nothing is sent until she approves and sets a send date. Once approved, it is set to send from membership@adk.org in batches of 50. I’ll test it with Laurie on Monday, starting with a single email. Goal: a monthly send on the first Thursday, starting in December.

Letters
Swapping in an edited acknowledgement letter

A small card on the gift page where an edited letter is uploaded. The auto-saved Word copies come off the gift in one step, and the originals stay in the Files of whoever generated them. Tested in the test copy of Salesforce; not in production yet.

Forms
Apple Pay on the donation, join and renew forms

The Apple Pay donation form will be matched to the full donation form, using Laurie’s markup, before it replaces it. Join and Renew are planned to move to Stripe Checkout, with Renew pre-filling from the portal login. An HPIC renew form that looks up the member is planned for later.

Users
Salesforce access for the intern

A new data-entry access level is live: the intern can add and edit records but cannot delete them, and does not see the gift entry grids. The intern’s user is created on an existing license. I’m checking what the intern will see before the start date.

What I need

From ADK

1. Laurie: the markup of field changes for the donation form.
2. Laurie and Sara: whether this round of renewal emails goes through Mailchimp or the new workflow.
3. Laurie: edits to the wording of the draft renewal email, so it is ready for Monday’s test.
4. The 34 batches dated July 3 to August 12 still marked Ready to Post: send them to Skyfin, or close them before the nightly export starts.
5. Funds for the 6 remaining 2026 gifts that still have none.
6. Laurie and Bridget: tell me when staff testing is done and the new grid can replace the current one.

Earlier recap: week of October 26