Mapping events

Mapping data for a one-time event

Required fields

The only requirement for creating an event is that it have a name. In the context of importing constituents to an event, you need to have a value in the "Gen. Event Name" column/field.

NOTE: When loading gift records, you can associate gifts with events by using the "Gift Event Name" field.

Special fields

Custom categories and attributes (different types of fields) can be imported into an event in LGL. During import, those custom fields will be available to you if you choose to display them and you choose the event within your import.

To access the custom attributes/categories for your event during an import, select the event in the dropdown menu from within the Appeal and event connection section of your import mapping page:

Now you will be able to match the columns in your import spreadsheet to the appropriate custom category/attributes in your import mapping.

If your import file does not contain a column and mapping for the event name, be sure you also assign a rule by using the “set defaults” rule for "Gen. event name”.

NOTE: It is possible to import to custom fields for only the one event you select in the Appeal and event connection section of your import mapping page, and the event must be active (not archived).

Example

Import file

Field mapping

Record Preview

Mapping data for a recurring event

NOTE: You can also import data for a recurring event into LGL. Read the Recurring events or classes - how to record attendance knowledge base article for more information about this option.

The key difference between mapping data for a one-time event versus a recurring event is to add one row to the recurring event import file for each date the constituent attended. The "Date attended" column that contains the attendance dates can then be mapped to the "Date attended" field in LGL.

The remaining columns in your import spreadsheet can be mapped as described in the previous section of this article.