Lost data after merging duplicate custom fields
After we upgraded to 3.7, I noticed that when I went to the custom fields area, I saw duplicates of each custom field PER project. For example:
Custom Field 1 (002) Custom Field 1 (005)
Where 002 and 005 correspond to specific projects.
I saw that I could now assign a single custom field to MULTIPLE projects just selecting the projects in the select box -- so using the example above, I modified the first Custom Field 1 field to be associated both 002 and 005 projects, then I removed the 2nd Custom Field 1 entry entirely.
After this, some issues in one project lost all of its data for the custom fields.
Any idea on why this happened and what we can do to restore it?
jg
tresstylez
· 1 |
|
Thursday, April 28, 2011, 8:00:45 PM |
0
|
What type are these 2 custom fields? Do you have a database backup? |
||||
|
0
|
One was a text box, one was a list box. I'm checking for DB backups -- but I'd still like to know where the data went if you could assist. Thanks. jg |
||||
|
0
|
Did you merge the text to the listbox? The data is probably still there but becuase the type is mismatch you won't see it in the front end. Can you check it in the database (gemini_customfielddata table) |
||||
|
0
|
Sorry, I didn't mean to say we 'merged' the fields themselves -- I meant instead of having separate instances of the same custom field for EACH project -- we kept only a single instance of that custom field and simply configured it to apply to multiple projects (on the 'Edit Custom Field' screen). |
||||
|
0
|
I see, so all you did was to apply Custom Field 1 to all the projects correct? If that is the case then of course that for all other projects it will be empty as the other project's data is still associated with Custom Field 2. |
||||
|
0
|
Hmm.. by Custom Field 2, you mean the 2nd instance of Custom Field 1? :) Its the same identical custom field, except we had one instance of the field per project. All the details and lookup tables were exactly identical -- so we figured we could get rid of the duplicates as long as we associated the remaining custom field with each project it needed to be associated with. I'm trying to wrap my head around why some issues in the SAME project lost all of its custom field data -- and data for other issues (in the same project) remained. |
||||
|
0
|
Unfortunately, it is not the same custom field. Even if the name is the same (or similar) it doesn't mean that it is the same custom field. You shouldn't loose any data, can it be that the custom field wasn't populated for these issues? |
||||
|
0
|
So, what you're saying is -- I could potentially delete a custom field but the data would still persist? |
||||
|
0
|
No, if you delete the custom field the data will be deleted. But if you simply remove a custom field from a project by unselecting the project from the listbox then the data will still be there. |
||||
|