Historical Date Calculations have been added to the system. These can be used to pull out date to match a specific query such as the date a personal best was achieved.
The ability to use a Date Field in a Historical Calculation has been added to the system.
Dates can now be used in historical calculations
To write in the historical calculations, you can use firstvalue and lastvalue before the name of the historical date field. But, do not use historicalmax or historicalmin for the historical date calculations as these will not run.
Historical calculations can be used to pull out first date or last date entered
Historical calculations can also be used in more complex set ups to pull out a historical date to meet a specific target criteria; for example, when a Best Score was entered onto the system
Needs to have a date format on the form item properties
In this example, a Historical Date calculation will pull out Date when the Score was equal to Best Score
To calculate this use the following calculation
valuewhentargetmatches(target_value, Historical Target_Field, Historical Desired_Field)
Remember to set up the Advanced Properties, and to set up the date format that the historical field needs to appear in
N.B. Here are some additional pointers about the "valuewhentargetmatches" calculation functionality
This is the new function we have built to get information from a field on the same date as a PB was reached.
valuewhentargetmatches(target_value, Historical Target_Field, Historical Desired_Field)
The idea is that you have a particular field you care about (Target_Field) that is tracking a certain value - e.g. the time taken to complete an event
The Personal Best for this field will be the entry (at some point in the past) where the athlete got the best result. You could set up an historical calculation to work out what this value was - in the way that I presume you would be calculating a PB anyway if you wanted to display it in the form (e.g. historicalmin(Historical Target_Field). This value would be stored in the field target_value.
The final part you want to work out is the value stored in Desired_Field at the time when the athlete managed to achieve their PB. That is what this function retrieves for you.
Example:
You have the field 'Event Time' that tracks how long the athlete took to complete the event.
You have the field 'Personal Best' which is an historical calculation working out what the best value ever entered for 'Event Time' has been - historicalmin(Historical Event Time).
You have the field 'Tiredness' which allows the athlete to track how tired they were at the end of the event. This could be a text field, a single selection field, it is up to you.
Finally you have the field 'Tiredness at PB' which is an Historical calculation (there are 3 types: text, number, or date available - use the one that matches the type of the field 'Tiredness') using the new function: valuewhentargetmatches(Personal Best, Historical Event Time, Historical Tiredness)
Note: this does require that you set up the calculation for each field you wish to track. But this provides the best way to be sure that we get the correct matching value.
When data is entered into the system and saved, the historical calculation will run. The date matching Best Score will be shown on the athlete history page, or can be viewed in the form if save and continue are added to the form.
The form will save and the calculations will calculate through all of the historical data entered on the system. The Best Score and the date of Best Score will be shown in the form (if you have save and continue enabled)
N. B. The Historical Date calculation functionality can also be used with the Match Entered By
See the section on Match Entered Date to find out more about this special filter
This means the date that a Best Score was achieved for a particular event will be calculated
0 Comments
Add your comment