As I understand it now, any mass update for accounts' UDFs will not allow a mass update for only one specific checkbox without affecting other checkboxes with data.

Example: We have a committee of volunteers that changes from year-to-year (like many organizations may have gala committees, for example). We have a checkbox for those that were on the 2011 committee, 2012, committee, 2013 committee, and so forth. I now want to mark the checkbox for those are part of the 2017 committee. However, I cannot do this via mass update without wiping out the old data for previous years.

I would either need to create a variety of queries to mass update (First query is for those that were on in 2011 & 2017, then 2012 & 2017, then 2013 & 2017, as well as 2011, 2012 & 2017, and then 2011, 2013 & 2017, and so forth). For this scenario of committees between 2011 and 2017, that would mean having to mass update via 720 different queries!

The other alternative is to update account-by-account, which will take less time than the first option, but still is -- for my particular case -- over 100 single updates. The larger the committee, the worse it would be. National associations, for example, often have committees and chapters of hundreds/thousands of members, and also would have a lot of time devoted here. Or if you are looking to use this UDF as someone that attended an event (though I use journal entries) such as a gala or conference using a checkbox/UDF, the same applies.

eTapestry needs the ability to update only one checkbox at a time in a UDF without affecting the other checkboxes.