Run Historical Calculations to Match By Options (e.g., to run a historical calculation for all events matching a specific option)

New filtering option called Match Entered Data to filters all historical records based on the answer to the matching/grouping field in that record.

It removes the need to build in a lot of calculations to match when the option equals a certain option. For this example a Swimming Personal Best is being built using this functionality.

For this example a form is built to track swim races times across different swimming race types and distances

For this example a form is built to track swim races times across different swimming race types and distances

A historical calculation is added that will pull out the min time in the Event Time field

A historical calculation is added that will pull out the min time in the Event Time field

Now set the Filter options correctly to ensure that is pulls out the minimum dependent on the Event (e.g. concatenated race type and distance)

Now set the Filter options correctly to ensure that is pulls out the minimum dependent on the Event (e.g. concatenated race type and distance)

Then select "Match Entered Data". This means the historical calculation will find the minimum for all entries on the system that match "Event"

Then select "Match Entered Data". This means the historical calculation will find the minimum for all entries on the system that match "Event"

On the main application, data can be tracked for different race types and lengths on the same form.

However, using the Match To filter in the Personal Best Calculation will ONLY calculate PB for the specific event data entered

However, using the Match To filter in the Personal Best Calculation will ONLY calculate PB for the specific event data enteredZoom: However, using the Match To filter in the Personal Best Calculation will ONLY calculate PB for the specific event data entered

The image in the example here shows that the Personal Best on that date will be calculated, but the Personal best is ONLY calculated for that swim event type. For example, the swim PB for Back 25m is 3.190, but it is 6.740 for Back 50m. Previously these PB's would have had to each be built in one by one for each type of swim event, but now they can be display in the same column.

Date restrictions can be used, such as last month or last year (as also show in the image here).

N.B. DO NOT USE ALL HISTORY AND FUTURE AS THE DATE FILTER BECAUSE THIS WILL BREAK THE HISTORICAL CALCULATION

When new data is entered, note that because the calculations are using historical calculations, click save and continue to see the calculations in the form. Note that they will still run when saved and appear in the athlete history

When new data is entered, note that because the calculations are using historical calculations, click save and continue to see the calculations in the form. Note that they will still run when saved and appear in the athlete history

After clicking save and continue the calculations will run and display any updated PB's (if there are any)

After clicking save and continue the calculations will run and display any updated PB's (if there are any)

N.B. If you are importing in Data, you may need to run a resave after the import to get the calculations to correctly factor in the date the data was imported, and the correct PB at that time.  

0 Comments

Add your comment

E-Mail me when someone replies to this comment