Insights Data Dictionary

This stored procedure generates a set of data that can be used for a standard room utililization report.

Input parameters:

        IN startDate DATETIME,
        IN endDate DATETIME,
        IN includeProspect BOOL,
        IN includeTentative BOOL,
        IN includeDefinite BOOL,
        IN includeMoveInMoveOut BOOL,
        IN includeDark BOOL,
        IN venueIds VARCHAR(16383), &mdash optional
        IN roomIds VARCHAR(16383) &mdash optional

Output fields:

        date,
        room_id,
        room_name,
        venue_id,
        venue_name,
        square_footage_in_use,
        total_square_footage

Each row represents a physical/mailing address associated with an account.

Each row represents a credit applied to an account.

Each row is an email address for an account.

External IDs for accounts. This data is populated only by integrations.

Each row represents a note associated with an account.

Each row represnts a payment made on an account for rental and event services. These payments are then allocated to one or more invoices.

Each row is a phone number for an account.

Each row represnts a refund made to an account.

List of account tags.

Each row is a tag applied to an account.

Each row represents an account (in the CRM). These are typically companies or organizations (though sometimes a single person) which is a sales lead or a client.

Each row represents a booked space in an event, plus all details of the event and room. A room may be booked several times on the same day, and each will show up as a separate row.

List of business classifications.

List of categories.

Each row is a mailing/physical address for a contact.

Each row is an email address for a contact.

External IDs for contacts. This data is populated only by integrations.

Each row is the assignment of a contact to a contact group.

Each row is a phone number for a contact.

Each row represents a contacts (in the CRM). They must belong to an account. They can be assigned to events with roles.

List of contracting statuses.

Each row is an "external" identifier for a credit, These identifiers are typically used to "map" the credit to another system &mdash typically a financial system.

List of credit types.

This view has:

• A row for every date (from 1990 to 2038!), with a NULL in event_id.
• A row for each booked space &mdash data is similar to vw_booked_spaces.

This view has:

• A row for every date (from 1990 to 2038!), with a NULL in event_id.
• A single row for each event &mdash date is the start date of the event.

This view has:

• A row for every date (from 1990 to 2038!), with a NULL in event_id.
• At least one row for each event &mdash with date holding every date that a function is on (there may be gaps).

This view has:

• A row for every date (from 1990 to 2038!), with NULL in all columns except date.
• A single row for each function &mdash has data similar to vw_functions.

List of departments.

List of deposit types.

List of discount types.

Each row represents additional revenue for an event.

If an event has contacts, there will be one row per contact, along with that person's role at the event.

Each row is a credit which has been attached to an event.

There is a row for each unique combination of event, date, and room. Note: If the same room is booked multiple times in a day, it will only show up once.

Each row is a discount applied to an event.

Master list of document folders.

Associates an event with all of its documents &mdash either physical or referenced via URL.

External IDs for events. This data is populated only by integrations.

A single row per event, with a summary of financial data.

Each row is an event genre.

A row per instruction on the event.

Each row represents an invoice scheduled installment.

A row per item allocation on the event. (Does not include rentals-- if you want both items and rentals you should use vw_event_item_and_rental_allocations.)

Combined item allocations and instructions.

Combined item allocations and rentals for events. Any particular row will be either an item allocation or a rental allocation.

A row represents a note on an event. An event may have zero or more rows.

Each row represents a package allocation on an event.

Each row represents a payment schedule for an event.

Each row is a payment made against an event.

Each row is a pre-sale date for an event.

Each row represents a price schedule assigned to an event.

Each row is a refund on an event.

A row per rental allocation for events. (Does not include items &mdash if you want both items and rentals you should use vw_event_item_and_rental_allocations.)

Each row is event revenue.