Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Aggregation is the most important of the three 'A's because it is about which fields have already been added up, the most basic example of which is the date - e.g. the system has already added up how many of X or Y happened yesterday or last Thursday. This means that it already has that data available when you ask, and just has to display it - i.e. when the arithmetic is already done, reports can appear quickly.

The things the reports automatically aggregate on are:

...

The things the reports optionally aggregate on are (and this is the exciting one):

  • Custom attributes that you add to Almost any attribute in the schema

Best practice with accounts is to use custom schema attributes for any data that needs to be consistent over multiple sub-organisations (e.g. job roles, specialities, temporary status) and reporting is the same.

Reporting goes further and enforces that practice as it will not generate a report for permission sets or user groups that covers more than the current one organisation. This is going to be a significant factor in any approach you take.

...

If you do not have any sub-organisations, or if those sub-organisations are left to their own devices and you do not need to report on them, then you do not need custom attributes. You may still find them useful, however user groups and permission sets may be sufficient for your needs - just allocate them as required. Groups are one per user, but multiple permission sets can be assigned to a user. 

...