Allen, I would put using reserved field ranges to create your custom fields to be a number 1.. By reserved I do not mean AR System reserved but the ones that Remedy Developers use for their application.. If in case you have created custom fields and using their range that they usually create fields from, then in the event that they use the same ID, it could break your upgrade..
I would say the same thing for using the immediately available user range.. Avoid those too.. I have seen Remedy engineering using some of those fields for trim fields etc. too in the past, as they do not bother to give those trim fields a specific ID.. stay clear of those.. use ranges above the 6, 7 or 8 million range.. That way you could be sure that they would not invade that range.. In case you have already done the above, I would use the archgid to correct the problem and give your fields an ID on or above the 6 million range.. Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Moore, Christopher Allen Sent: Wednesday, March 12, 2008 12:56 PM To: arslist@ARSLIST.ORG Subject: What specifically breaks upgrades? ** Hey everyone- I’m putting together a plan to upgrade from 7.0 to 7.1. We have done some modifications to the system, but nothing too drastic. Form changes, additional workflow, but (as far as I know) no changes to the BMC OOTB workflow. What sorts of changes specifically are problematic when upgrading? Windows Server SQL DB Thanks! Chris No virus found in this outgoing message. Checked by AVG. Version: 7.5.518 / Virus Database: 269.21.7/1327 - Release Date: 3/12/2008 1:27 PM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
