The names of item tracking fields 'Custom1' and 'Custom2' were lost after upgrading to 2.0
I had to rename them to their previous settings after upgrade.
Custom Field names missing after 2.0 upgrade
Moderator: SourceGear
Re: Custom Field names missing after 2.0 upgrade
I'll make sure this gets checked out and will post back after we try it. Thanks for the report.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Custom Field names missing after 2.0 upgrade
Could you tell me what version you were upgrading from?
Did you perform an in-place upgrade, or did you perform an uninstall/reinstall, or move to a different machine?
What is the server OS?
Did you perform an in-place upgrade, or did you perform an uninstall/reinstall, or move to a different machine?
What is the server OS?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Custom Field names missing after 2.0 upgrade
It was an in-place upgrade from 1.1.4. Server is Win 2003 Std SP2 x86
Re: Custom Field names missing after 2.0 upgrade
We've tested 3-4 upgrades now where we had custom fields and our field names didn't change.
Did you have information logged to those field names?
Did you have information logged to those field names?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Custom Field names missing after 2.0 upgrade
Yes, we had data in those fields and the data has not been lost.
Notification e-mail snippets showing the issue:
Pre-upgrade:
Requestor:
Validator / Reminder Week(s):
Post upgrade:
Custom1:
Custom2:
Notification e-mail snippets showing the issue:
Pre-upgrade:
Requestor:
Validator / Reminder Week(s):
Post upgrade:
Custom1:
Custom2:
Re: Custom Field names missing after 2.0 upgrade
We haven't been able to reproduce this and haven't had other reports. If other users have enountered this, let us know; we'd like to track it down.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager