Difference between revisions of "Value Stores To"
| (8 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | For most types of [[Custom Fields]] (all fields that store data rather than files) the '''Value | + | For most types of [[Custom Fields]] (all fields that store data rather than files) the '''Value Storage''' section allows you to select another field on the same entity (or within the [[Universal Tracking Application]] at the same level) to store the same data. |
| − | |||
* This can be useful if you wish to display the data in another location on the record. | * This can be useful if you wish to display the data in another location on the record. | ||
* It also allows you to have another field that displays the information with different [[Status Field Permissions]], [[Role Field Permissions]] and/or [[Visibility Condition]]s. | * It also allows you to have another field that displays the information with different [[Status Field Permissions]], [[Role Field Permissions]] and/or [[Visibility Condition]]s. | ||
| + | |||
| + | Whenever values need to be passed between levels, a [[Template / Type Formula]] should be used. | ||
| − | + | The exceptions are [[Web Page View]], [[MS Word Merge]] and [[Single File]] or [[Multiple Files]] fields which allow selection of a file storage [[Custom Field]] using '''Value Stores To'''. The [[Single File]] or [[Multiple Files]] field selected in the '''Value Stores To''' option can be at the same level, or on the parent or grandparent levels (if available). | |
| + | The '''To Custom Field''' option can also be used in [[Shadow Application]]s that don’t inherit their [[Custom Fields]] from the parent. Again, Value Stores To only allows storage of data to Custom Fields on the same level, either in the [[Shadow Application]] or in the Parent UTA. | ||
| − | |||
| + | The '''To Custom Field''' option can also be used with dependent (child) fields on [[Custom Field Type: Dynamic Data – Dynamic Control Field|Dynamic Control Fields]] to store to other fields on the same level. | ||
| − | |||
| + | The '''From Custom Field''' displays the name of the source field that the current field is pulling data from. | ||
| − | [[Custom Fields]] | + | [[Category:Custom Fields]] |
Latest revision as of 14:13, 6 June 2016
For most types of Custom Fields (all fields that store data rather than files) the Value Storage section allows you to select another field on the same entity (or within the Universal Tracking Application at the same level) to store the same data.
- This can be useful if you wish to display the data in another location on the record.
- It also allows you to have another field that displays the information with different Status Field Permissions, Role Field Permissions and/or Visibility Conditions.
Whenever values need to be passed between levels, a Template / Type Formula should be used.
The exceptions are Web Page View, MS Word Merge and Single File or Multiple Files fields which allow selection of a file storage Custom Field using Value Stores To. The Single File or Multiple Files field selected in the Value Stores To option can be at the same level, or on the parent or grandparent levels (if available).
The To Custom Field option can also be used in Shadow Applications that don’t inherit their Custom Fields from the parent. Again, Value Stores To only allows storage of data to Custom Fields on the same level, either in the Shadow Application or in the Parent UTA.
The To Custom Field option can also be used with dependent (child) fields on Dynamic Control Fields to store to other fields on the same level.
The From Custom Field displays the name of the source field that the current field is pulling data from.
