TntConnect Beta Testers - All Comments

re: A way to run TntConnect on your Mac for free (TntConnect 4.0.43 BETA)!

Troy Wolbrink — Fri, 17 Feb 2023 23:31:21 GMT

I'm so glad to hear your testing of this worked out!

Regarding my thoughts on maintaining things moving forward, I moved that here: www.tntware.com/.../72127.aspx

--Troy

re: A way to run TntConnect on your Mac for free (TntConnect 4.0.43 BETA)!

Jason Maas — Thu, 16 Feb 2023 16:17:29 GMT

I just followed the instructions and everything seems to be working as intended. Slick!

I'm using a 2015 MacBook Pro running macOS 13 "Ventura" via the OCLP project (because it's too old to be officially supported by Ventura). So I have layer upon layer of compatibility hacks going on this computer. 🤣

This installation via Wineskin even picked up my existing TntConnect preferences (opened my database file automatically on first run), so that was an unexpected bonus.

How should users keep both TntConnect and the underlying Wineskin infrastructure updated moving forward? There should probably be a separate article answering that question...

re: A way to run TntConnect on your Mac for free (TntConnect 4.0.43 BETA)!

Troy Wolbrink — Wed, 15 Feb 2023 17:24:32 GMT

Hi Jason, I tested this out on my Mac, and the CrossOver-TntConnect or the Wineskin-TntConnect can co-exist just fine. I even ran them together at the same time. For the most part, they are isolated environments.

I noticed one small issue when I ran them both at the same time.

The Wineskin version won't fully shut down until the CrossOver version is closed down as well. You can't reopen the Wineskin version until its previous session is closed down.

But to answer your question: It will not mess anything up with the CrossOver-installed TntConnect.

re: A way to run TntConnect on your Mac for free (TntConnect 4.0.43 BETA)!

Jason Maas — Wed, 15 Feb 2023 14:31:13 GMT

Wow, that's fantastic news!! For us Mac users that already have TntConnect installed via CrossOver, what's the result of following the instructions to install it again via Wineskin? Will it mess anything up with CrossOver or the CrossOver-installed TntConnect?

re: TntConnect 4.0.2 BETA

Troy Wolbrink — Fri, 06 Mar 2020 16:54:47 GMT

Hi Mark, the cutoff in 4.0.0 and 4.0.1 was March 31, 2020. Since 4.0.2 it was extended to May 31, 2020. If you plan to import from a file indefinitely, you'll need to stay on 3.5.

re: TntConnect 4.0.2 BETA

MarkHallsten — Fri, 06 Mar 2020 16:27:04 GMT

Troy, thank you so much for the ongoing improvements! I have not upgraded to Catalina on my Mac because several of my applications (including TNT) have not yet been able to run on Catalina. You have now removed that barrier. I am looking forward to using TNT 4.0, However...

My organization does not have plans to use DonorHub. Syncing from a file is still my best option. Could you please clarify the TNT roadmap? You announced that the cutoff date for non-DonorHub gift imports is May 31, 2020. Will that cut off be implemented by a future TNT update (to say 4.03)? May I stop upgrades to TNT at 4.02 and still have the ability to import a file?

re: TntConnect 3.5 r16 BETA ... MailChimp API 3.0 compatible

Troy Wolbrink — Mon, 15 Apr 2019 18:31:18 GMT

TntConnect 3.5.20 fixes a few additional items with the MailChimp API 3.0 changes. If you're a beta tester, please install this beta version and test it out. I'd like to release it soon.

Thanks,

Troy

re: DataSync - explicit gift sync date range

Troy Wolbrink — Thu, 21 Feb 2019 22:16:45 GMT

I made a slight change to the particulars. Instead of being added to the [ORGANIZATION] section, a new [FILE] section will be used, and the entries will be called GiftsDateFrom and GiftsDateTo. I've edited the original post to reflect this.

re: DataSync - explicit gift sync date range

Troy Wolbrink — Thu, 21 Feb 2019 21:48:53 GMT

Let's say the organization always provides "the last 4 weeks" of donations in their data sync file. And let's say they email this file every week. In this case both the GiftSyncBegin and GiftSyncEnd will increment by 7 days with each weekly email.

I really can't say how often the organization changes either GiftSyncBegin and GiftSyncEnd unless i know how often they change the range of gifts within each file. These entries tell TntConnect the exact sync range for gifts in *this* file so it doesn't have go guess.

re: DataSync - explicit gift sync date range

Bob Mac Leod — Thu, 21 Feb 2019 21:27:45 GMT

Does the organization manually update that date on some regular cycle? Or does it advance forward automatically like the end date does?

re: DataSync - explicit gift sync date range

Troy Wolbrink — Thu, 21 Feb 2019 21:16:53 GMT

The 'begin date' indicates how far back the [GIFTS] section (in this file) contains knowledge of (all) gifts for this user.

re: DataSync - explicit gift sync date range

Bob Mac Leod — Thu, 21 Feb 2019 21:09:57 GMT

What are the ramifications of this from the organization perspective? If the regular sync file [end date] is being automatically generated every day, when does the organization manually update the begin date?

re: TntConnect 3.4.2 BETA Update

Troy Wolbrink — Sat, 16 Sep 2017 16:11:22 GMT

Just as a reminder, here's the official specifications for creating compatible DataSync files: www.tntware.com/.../how-would-i-send-our-staff-a-monthly-tntconnect-datasync-file.aspx

re: TntConnect 3.4 BETA

Bob Mac Leod — Wed, 13 Sep 2017 19:03:03 GMT

I was the first person to download 3.4, and I really like the encouragement to update donor addresses. I thought I did this regularly, but was embarrassed to discover it had been six months since I last checked. And to my surprise, two of my partners had moved and I did not know it!

I also really like the "catch adjustments" feature.

For years, I have strongly encouraged users to do these things regularly: Check for Address Updates, and set the "Start Date" back in time to catch adjustments. So--especially for DonorHub ministries--these features are a welcome addition.

re: TntConnect 3.2 (Preview)

Troy Wolbrink — Thu, 05 Jan 2017 01:46:04 GMT

Michael, that was a great suggestion on grouping together history for mass group changes. That not only makes things more tidy, it speeds things up. As a bonus, this history grouping works for any similar group changes, when it's the same from and to group, as long as the changes are made within 5 minutes of the last. But as soon as you change the from or to group, you start a new history grouping. (This will be in TntConnect 3.2.1)

As far as the drag-n-drop idea, my concern is that it might be too easy to make unexpected changes by an inadvertent mouse movement by a novice user. You can edit a group and change the parent (in the "Edit Group" dialog). Also, you can easily clone groups by making a duplicate. So the same effect can still be accomplished, in a more intentional way.

--Troy