System Development, Software Updates, Quick Guides and Builder Training InformationAll New Release Software Enhancements and UpdatesNew Releases and Software Updates Performance Enhancements for Speed and Server load: Build 4.665 and above 12/08/2015Linked Calculation Advanced Form Property: used to recalculate state on a specific date, and should ONLY be enabled on forms that link state and need to calculate it retrospectively, during an import, or resave.

Linked Calculation Advanced Form Property: used to recalculate state on a specific date, and should ONLY be enabled on forms that link state and need to calculate it retrospectively, during an import, or resave.

A new work flow was developed and built into the system for recalculating status from a linked field, such that the system could retrospectively pull through the state of an athlete *as of a particular date* (e.g. the injury status at a specific date, not just from the end of the injury). This meant that system need to go back through every single state saved for the athlete for each event which state was pulled from and then recalculate state at that time. To perform this, the system had to do a lot more work to complete these calculations, especially as it was calculating state across all possible entries for this athlete. This change was enabled on all linked fields to ensure accuracy of data when importing and resaving data. However, because it introduced such a large load when saving, and because it is ONLY really needed when pulling through linked state on a specific date, where state could change, this functionality has been set as standalone functionality.

In the Advanced Properties of the Form, there is a new field called "Linked Calculation". By default it is set to "No", which means all linked fields will still work, and they will pull through the correct linked value from any record based on the date at that time. But, they will not retrospectively pull out state if data is backdated. See below for some examples.

When the field is set to "No" you can expect the form to respond correctly and to pull through linked fields. For example, if you want to pull out 1RM from a 1RM form entered on the 1st of the month into strength forms entered for the rest of the month, the system would still pull out the the most recent 1RM data from the 1st and it would pull that into any new S and C forms that were entered. Any resave or imports would also work to pull out the most recent 1RM value and pull it through into the Strength form. So, you do NOT need to enable the Linked Calculation for this work flow.

Alternatively, if state is pulled through from an injury form into a daily monitoring form, you may consider enabling the fields to =Yes. For example, an athlete was Injured and Unavailable on Monday, got Back to Training on Wednesday and was Available on Friday and the injury state is pulled into a daily monitoring form. As long as the daily monitoring form is entered on each day of the week the state would be pulled through correctly on the day the daily monitoring form is entered (e.g. the correct state is pulled through on Monday as Unavailable, Wednesday as Back to Training etc). However, if someone entered in a weeks worth of daily monitoring forms on the Friday, regardless of the day they were entered for, the state would appear as the last saved state (e.g., Available). So, while state has changed in the form, only was most recently saved state on the form will be pulled as a linked field because the history of state is not viewable to pull through. In this scenario, if you set the "Linked Calculation" to Yes,  the system would instead go back through the history of that form in the system (which is hidden from the user) to find the state on that specific day and pull though state on that particular day (e.g. Monday would be Injured and Unavailable). However, because the system has to go back through the revisions which are stored in the system for that entry and link the correct state on Monday with the Monday daily monitoring form, this takes a lot longer to perform.

So, you need to carefully consider WHEN and WHERE you enable this setting. If you set it to "Yes" it will go through every single linked field in the form and factor in any revisions for the form that it links from to pull through the correct data. So, while this adds loading and saving time, it will be accurate.

However, if users regularly enter in data on the correct date, then this feature could be turned off, and then may only need to be enabled for resaves, or imports. You need to consider how your system is used, how many fields are linked, and how performance is affecting when turning this feature on or off.

Just note that any resaves that are done, when this field is enabled have to go through the same process of checking the revisions history for each entry and each state across every date to pull through the state at that time, and it has to do this for all athletes, so this will take a while to perform.

If you link a status field from one form to another and you use "State" or "Current State" you will ONLY need to turn on the "Linked Calculation" if you need to link back to state on a particular date

If you link a status field from one form to another and you use "State" or "Current State" you will ONLY need to turn on the "Linked Calculation" if you need to link back to state on a particular date

This form pulls in state from the injury. It is set to pull through the worst state at the date of entry.

To enable the form to pull through state on a particular date, the Linked Calculation needs to be set to Yes.

To enable the form to pull through state on a particular date, the Linked Calculation needs to be set to Yes.

By default it is set to No.

Set it to Yes to pull through linked fields as of a specific date; where the fields being pulled through have possible undergone changes within an event form (e.g. state in an injury record).

N.B.This is not needed for records when a field does not change within one entry.

0 Comments

Add your comment

E-Mail me when someone replies to this comment