Apr 16th, 2012, 1:15 PM
Hey guys,
gabunt:
Strange. On the main Option Lists page, could you sort by Option List Name - do you see multiple records with the same name? If so, that shouldn't have been allowed, so there's a loophole in the code somewhere.
But don't wouldn't worry about renaming it - any fields that reference the Option List do so by the ID, not the name, so changing the name won't cause anything to break.
kououken:
Yup! This is actually intentional. Any time you change an Option List, all form fields that reference it will be updated to show the changes. Otherwise I think it would get pretty confusing and out of hand... any time an Option List changes there would be multiple versions assigned to the same field, so depending on when it was first submitted, it would show different options. Bit weird and very hard to keep track of.
But I see your problem. Are you using the same form again and again for multiple years / events / whatever? We do this a lot for our own work. Since each year brings about changes to the fields and Options Lists, we always make a copy of the entire form each year, effectively "archiving" the old form. Then with the new form, we make copies of any Option Lists that need to be changed, thus keeping the old data for previous years intact.
Not sure if this helps in your scenario, though...
- Ben
gabunt:
Quote:I have gone to the Option List, found the field and chosen edit, chosen the import option list at the bottom. When I do that the new option value appears in the list. However, when I click the Update button I receive the error message saying "Sorry, this option list name is already taken. Please choose a new name."
Strange. On the main Option Lists page, could you sort by Option List Name - do you see multiple records with the same name? If so, that shouldn't have been allowed, so there's a loophole in the code somewhere.
But don't wouldn't worry about renaming it - any fields that reference the Option List do so by the ID, not the name, so changing the name won't cause anything to break.
kououken:
Quote:I am having a problem I think is related, but with the opposite effect. Removing options from an option list hides those values when viewing previous form submissions (though they are still there in the database fields).
Yup! This is actually intentional. Any time you change an Option List, all form fields that reference it will be updated to show the changes. Otherwise I think it would get pretty confusing and out of hand... any time an Option List changes there would be multiple versions assigned to the same field, so depending on when it was first submitted, it would show different options. Bit weird and very hard to keep track of.
But I see your problem. Are you using the same form again and again for multiple years / events / whatever? We do this a lot for our own work. Since each year brings about changes to the fields and Options Lists, we always make a copy of the entire form each year, effectively "archiving" the old form. Then with the new form, we make copies of any Option Lists that need to be changed, thus keeping the old data for previous years intact.
Not sure if this helps in your scenario, though...
- Ben