Data Actions are a way to automatically update Participant Data in real time based on some Action Trigger.


Warning: Data Actions will fire automatically so can be dangerous if you aren't positive that they are set up correctly! Some changes like switching events can cause a whole lot of headache if accidently applied to everyone in the race, so please be sure that you understand how these work and have set up a test event to try it yourself before using on a live race.


TABLE OF CONTENTS



To set this up, first go to the Data Actions tab:



And select Add:



First define the type of thing that is causing the change to occur in the Action Trigger section.



Next define the data that should be updated in the Data to Change section.




How to Switch Events Based on a Read existing at "Check" Location when the Participant is in an Event that should not cross that Location.


The most common use is to switch a Participant's Event (Data to Change) based on their read at a given Stream (Action Trigger).


To accomplish this, use the Raw Read Filters section to select the Stream or Streams (using the "in" operation instead of "==") that you would like to drive this Data Action. You could also use the Timestamp filter to only select reads from a Stream over a certain time period.



Next, open up the Raw Read Filters section so you can set up which Stream you want to drive the Event switches from.


In this example, I want to switch participants to the 10k who are read on my CHECK-FILE Stream that are in the 5k event.


Next in the Data to Change section, select Event from the Field to Assign to dropdown, and the Event you would like Participants to be switched to from the Value to Assign dropdown.



After saving, all future reads will trigger the Event switches set up here. If you need to, you can recalculate raw reads in order to process any existing data.


This Data Action setup will switch the Event as soon as they cross the Check location, so you have to be careful in your setup to ensure that no mistriggers happen because some 5k participants happen to walk over the check mats before or after the race. Because of this, you may want to set up additional time filters.


How to Switch Events Based on a Read NOT existing at "Check" Location when the Participant is in an Event that SHOULD cross that Location.


This requirement has a different setup because we don't want to trigger the Data Action when a Participant crossed a specific split point, but instead want to trigger the Data Action when a Participant crosses the Finish location but happens to be missing a read at a specific split point.


In this case you would need to add a Participant Data Filter to only include Participants in this Data Action whose split time is null (or missing).


Here we have a 10k Race with a 5k split point. 


First set the Participant Data Action to check for null split times at your checkpoint segment.


Then set up the Raw Read filters to look for reads at your Finish location that are associated with the 10k Event.


Then set up the Data to Change area to switch these 10k participants who missed their split time to the 5k.



Another popular thing to do in this case would be to set the DQ flag instead of automatically switching them. This would allow you to review who was DQ'd and manually decide whether you'd like to switch their event or not.


Viewing Data Action History


Data Actions happen automatically in real time, so it's helpful to be able to go back to see what changes actually happened. You can do this using the Data Issues > Log feature.


First select the Data Issues icon on the left, then select the Data Action you set up from the "Issue Source" dropdown. Next select "Log". This will give you a list of participants that were edited by this Data Action.



For more details on Event changes in particular, RunSignup has a Transfer Report which gives you more information about the original registration that was archived as well. That can be found under Reports > Not Registered > Transfer Report.