Difference between revisions of "Value Stores To"
From SmartWiki
| Line 1: | Line 1: | ||
| − | For most types of [[Custom Fields]] (all fields that store data rather than files) the '''Value Stores To''' option allows you to select another | + | For most types of [[Custom Fields]] (all fields that store data rather than files) the '''Value Stores To''' option allows you to select another field 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 [[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. |
Revision as of 11:51, 17 November 2009
For most types of Custom Fields (all fields that store data rather than files) the Value Stores To option allows you to select another field 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.
Anytime values need to be passed between levels you should use Template/Type Formulas.
The exceptions are Web Page View, MS Word Merge and Single File/Multiple Files fields which allow selection of a file storage location using Value Stores To.
Value Stores To 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.
