Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Custom fields lost during migration to Gemini 5

admin
custom-fields

None of the project custom fields came through in migration to Gemini 5. I didn't seen any documentation in the Migration Guide on how to confirm Custom Fields migrated with their projects. Re-creating the exact same Custom Fields in the project after migration doesn't carry over the values previously assigned to those fields. We need to be able to reference Custom Field values of previous projects without having to manually reenter them (which isn't always possible anyway). Is there a way to go about doing this?

User21899
· 1
User21899
Replies (5)
helpful
0
not helpful

All custom fields should be migrated to the migration template. Are you sure you have selected the correct template? Did you move the project from the migration template?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Thank you, I did miss that the Custom Fields were assigned to the Migration template. I duplicated the Custom Fields from the Migration template into a new template and the fields are visible in all projects. The problem remains though that after being duplicated out all custom fields are showing as their default values (default as assigned in v. 4.0.0) and not their actual set values. Am I missing another step somewhere?


User21899
· 1
User21899
helpful
0
not helpful

Did you move templates and mapped the custom fields?


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Following Section 5 in the Migration Guide, I created a new template, recreated all the Custom Fields used in existing projects (v4.0) within that template and then moved the migrated project into the new template. Mapping these custom fields showed only the custom field name, not specific values contained within. It didn't give me the option to map over the individual values like I could with other fields (e.g.: Priority showed the field name and below that each of the field values). All my Custom Fields are now showing in the projects, but they're showing unassigned default values, not the actual assigned value. Not sure what other step I'm missing here.

On an additional note, I redid this process on a template for a project I'd already moved out of Migration. Since the values weren't mapped at that initial move, does that mean I have to re-migrate the project into v5 to 'start over'? If so, is there an easy way to go about re-migrating just the specific projects and not the entire database?


User21899
· 1
User21899
helpful
0
not helpful

Yes, you will have to start over. Before you do, check if you have any data in the gemini_customfielddata table


Mark Wing
· 9108
Mark Wing