Difference between revisions of "Value Stores To"
| Line 11: | Line 11: | ||
| − | The exceptions are [[Web Page View]], [[MS Word Merge]] and [[Single File]] or [[Multiple Files]] fields which allow selection of a file storage | + | 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). |
Revision as of 10:58, 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 a Template / Type Formula.
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).
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.
