CiviCRM Community Forums (archive)

Great to see this in the 2.1 roadmap http://wiki.civicrm.org/confluence/display/CRM/Proposed+nestable+groups+implementation

Am just about to set up 200+ more subsets in our system and just wanting any advice that can be offered in order to make the transition to nestable groups as smooth as possible when they arrive as we are very keen to use them, especially if, as documentation suggests, it will not restrict children to a single parent.

So, given the above and the fact that most of these subsets will be used with CiviMail, should we set these up, for now, as groups or as custom data?

The usage will primarily be by some of our Users who would ideally have a profile/custom page so they can more rapidly find the right groups to add to a CiviMail.

Given the large list of Mailing List groups we are going to end up with, what can we hope to do to avoid Users having to scroll down the long list of groups in the Include Groups box on the "Select Recipients (step 1 of 5)" page of CiviMail?

Understood - except it is something I was aiming to deliver on this month so keen not to sit on it for 8+ days