Timeline for Can we restrict the movement of the multivalued field in a schema
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2013 at 0:43 | history | tweeted | twitter.com/#!/StackTridion/status/394987873021485058 | ||
| Oct 23, 2013 at 16:34 | comment | added | Quirijn | Why not have 2 multi-value fields then? If the values are not interchangeable they should not be in the same field together. | |
| Oct 23, 2013 at 15:20 | comment | added | Patan | @Quirijn. Thank you. Here the Max occurance is uncertain. | |
| Oct 22, 2013 at 20:15 | comment | added | Quirijn | It would seem to me that if you want to impose such restrictions, you might be better off defining two or more fields instead of one multi-value field. | |
| Oct 22, 2013 at 16:59 | vote | accept | Patan | ||
| Oct 22, 2013 at 15:28 | answer | added | Jaime Santos Alcón | timeline score: 4 | |
| Oct 22, 2013 at 15:17 | history | asked | Patan | CC BY-SA 3.0 |