CiviCRM Community Forums (archive)

We need to provide the management with a list of groups - name and number of contacts in the group.
Something like:

Corporate members - 1220
Non-corporate members - 2011
Journalists - 561
.......

I've been searching trough this forum, but did not find a solution for my problem and I am quite surprised that Civi does not have this simple feature.
I can manage simple things in php and mysql and I was looking at database level, but I am stuck with select_tables and where_tables fields.

At the API level I am stuck with the 25 results limitation.

At PHP level I am stuck with crm_get_groups - no such function.

Can you propose a solution?

I agree that having the 'contact count' showing on the Manage Groups screen would be a great addition - do you have any skills to apply to this? If so probably worth jumping on IRC to get some guidance
Some question with a Smart Group
- do you show just a single number for 'all'
- or 2 numbers, one for 'smart' contacts and other for 'standard contacts'?

good to hear - jump on to irc - http://irc.civicrm.org/ - and see if any of the core group or knowledge developers (not me) are around ;-)

there are a bunch of people on there right now - not sure why you ain't seeing anyone

You might want to use the API and/or the BAO functions, rather than using those columns directly

lobo

the 25 limit can be overridden. see http://book.civicrm.org/developer/techniques/api/ (search for limit)

some info on baos here: http://book.civicrm.org/developer/introduction/the-codebase/

On ajax, the syntax is option.limit. Could you update the wiki?

http://drupal.demo.civicrm.org/civicrm/ajax/doc/api#/civicrm/ajax/rest?json=1&sequential=1&debug=1&&entity=GroupContact&action=getcount&gid=2&option.limit=10000

returns 109.

I haven't checked, but if the api doesn't implement a specific getcount, the default version does do a normal get, count how many were fetched and trashes the result.

If you plan to do this query often, I would suggest to contribute a getcount for GroupContact (if not done already)

In my experience, we don't have any consistency on the label for limits on the API, e.g. http://issues.civicrm.org/jira/browse/CRM-9110

Xavier, as API queen, would you be able to preside over a judgement here?

We discussed it in apeldoorn, we got a few issues wrapped up

options => array (limit => 42)

is the preferred syntax. This syntax obviously doesn't work for ajax, so &option.limit=42 is the closest we could get.

As for the lack of consistency, agree, it sucks and we should fix it. However, as some api relies on bao that don't have a way of setting the limit, fixing becomes a "wee bit" more complex and we are more than welcoming any patch that would add the feature to the BAO (or move to the DAO)

Makes sense?

X+