Profile Reports vs. Event Reports

Custom criteria can be created from Profiles World data or from Events World data. The process of creating criteria is nearly the same for both. However, there are some functions that are available for custom Profile reports that are not applicable to the Events reports. and therefore those functions will not be shown on the Report Form for a custom Event report. And, the World for which you are building the criteria will determine what data tables will be available when constructing the criteria statements.

Profiles reports are dependent on the constituent id from the selected data rows. This id is present in every data row in the Profiles World, and it is the way that rows belonging to the same constituent are linked together. The standard generic export table that is automatically constructed when a Profile report is run uses the id as the link between information belonging to the same constituent.

In contrast, the Events data tables use the Event Code field as a link between the related data rows in the Events World. Many of the data tables in that world have no associated constituent id. And many of the data tables that do contain a field for a constituent id do not require that it be present.

Example: An Activity data row is not specific to a constituent and therefore there is no field for a constituent id. A Registration data row always identifies a constituent and therefore a field is present and mandatory to track that information. But, an Event Guest data row may identify a constituent or a non-constituent. So, while the data table contains a field to identify a constituent, but it may be left blank if the guest is not a constituent.

Event reports are dependent on the Event Code that is contained in all of the data rows in the Events tables. Therefore, the standard generic Events export table that is automatically constructed when an Events report is run will use a different layout than the export table that is constructed when a Profile report is run.

When constructing criteria for an Events report in the Reporting World, you must begin with either the Millennium Explorer Custom Profile item, with one of the templates from the Events report template group, or with another report that was previously constructed as an Event report. When you do so, the system will recognize the criteria as an Event report and will show the names of the Events World tables and fields (only), and when run, will generate a generic Event export table.

When constructing criteria for a Profiles report in the Reporting World, you must begin either the Millennium Explorer Custom Profile item, with one of the templates from the Biographical, Comparison, Daily, Financial, Mailing, Membership, Pledge, or Prospect Tracking groups, or with another report that was previously constructed as a Profile report. When you do so, the system will recognize the criteria as a Profile report and will show the names of the Profiles tables and columns, PLUS the tables and field names from the Events World that include a field for a constituent id. These Event tables are: Attendance, Event Guest, Event Solicitor, Organizers Registration, and Speaker. When such criteria are run, the system will generate a Profile generic export table.