Importing Event Participation Records

This topic provides additional details related to importing legacy event participation records from a demand response management system (DRMS) into Digital Asset Management / Digital Asset Cloud Service.

Event Participation Import File Format

Legacy event participation import files use the following tab-separated values format:

Field Name

Optional/Required

Notes

Legacy Event Participation ID

Required

The id for the event participation record in the DRMS application.

Reservation Start Date Time

Required

The start date and time of the event.

Reservation End Date Time

Required

The end date and time of the event.

Participation Start Date Time

Optional

The start date and time of the device's participation in the event, Some devices may participate in only a portion of an event. If not applicable, this field is blank.

Participation End Date Time

Optional

The end date and time of the device's participation in the event, Some devices may participate in only a portion of an event. If not applicable, this field is blank.

Legacy Controllable Device Id

Required

The id for the controllable device in the DRMS application.

Legacy Program External Id

Required

The id for the program in the DRMS application.

Legacy Program Subscription Id

Required

The id for the enrollment (program subscription) in the DRMS application.

Preemptive Opt Out

Optional

A flag that indicates if the event participation had opted-out of prior to the event. Valid values are values for the Preemptive Opt-Out (PREEMPTIVE_​OPT_​OUT_​FLG) lookup, and include:

  • D1NO (No)

  • D1YS (Yes)

Event Outcome

Optional

A flag that indicates the outcome of the event. Valid values are values for the Outcome (OUTCOME_​FLG) lookup, and include:

  • D1SP (Successful participation)

  • D1IO (In-flight Override)

  • D1ND (Non-responsive device)

  • D1ER (Error)

  • D1CN (Cancelled)

Event Participation Status

Required

A text string that specifies the status of the event participation. Valid values include:

  • PRE-EVENT

  • POST_​EVENT

  • CLOSED

  • CANCELLED

Sample Record

Below is a sample file:

EXTEVTPART2    2022-09-01T08:00:00-05:00    2022-09-11T08:00:00-05:00    2022-09-01T08:00:00-05:00    2022-09-11T08:00:00-05:00    EXTDVC2    LEGACYPRG1    EXTENR2    D1YS    D1SP    PRE-EVENT

Upload Batch Process

Legacy event participation import files are uploaded using the Legacy Participation Event File Upload  (X1-PTUPL) batch process. Use the Batch Control portal to view the parameters used by this batch process. This process should be run as needed for the initial import. 

This process creates inbound sync requests in the "Pending" state (see below).

Inbound Sync Request Business Object

Event participation inbound sync requests are based on the Event Participation Sync Request BO (X1-DASyncReqEventParticipation) business object.

Inbound sync requests are created in the "Pending" state. The Sync Request Monitor (F1-SYNRQ) batch process is used to transition these to the "Transform/Validate" state where the data is validated and transformed as needed for import and moved into the "Validated" state (or "Validation Error" if an error is encountered). These are processed by an "Initial Sync Request Load" batch process (see below).

Initial Sync Request Load Batch Process

Legacy event participation records are created from inbound sync requests using the Initial Sync Request - Load Event Participation (X1-SLPAR) batch process. Use the Batch Control portal to view the parameters used by this batch process. This process should be run as needed for the initial import.

This process transitions the inbound sync requests to the "Loaded" state.