Difference between revisions of "Common:SpecifyingEnumerationValues"
From LongJump Support Wiki
imported>Aeric (Created page with "*When you select this type for an object field, a text area lets you enter values. ** Enter the names of the values, one per line, in the order they will be displayed. **When t…") |
imported>Aeric |
||
| Line 3: | Line 3: | ||
**When the user makes a selection, the value that is stored is the text entered on that line. So: | **When the user makes a selection, the value that is stored is the text entered on that line. So: | ||
**#If you change the order later, existing values are not affected. | **#If you change the order later, existing values are not affected. | ||
**#If you remove an entry at a later date, existing records that have that value are not affected. | **#If you remove an entry at a later date, or change the spelling of a value, existing records that have that value are not affected. Either clean up the object data, or take that possible value into account in your design for backward compatibility. | ||
Latest revision as of 22:47, 7 September 2011
- When you select this type for an object field, a text area lets you enter values.
- Enter the names of the values, one per line, in the order they will be displayed.
- When the user makes a selection, the value that is stored is the text entered on that line. So:
- If you change the order later, existing values are not affected.
- If you remove an entry at a later date, or change the spelling of a value, existing records that have that value are not affected. Either clean up the object data, or take that possible value into account in your design for backward compatibility.