Yes its a 9 digit number .. so a 600 million range and above is good.. JT, thank you for the correction..
So if you have used the 500 million range or below as the custom field ID, change that to a higher.. You will not get that warning if you use the 600 million range (9 digit number). It is specifically fields you have created that you 'let the ARS assign the field ID's' that you should be worried about as it is highly likely a careless developer at BMC may use that ID for trim fields.. It has happened before and giving the benefit of doubt to the Remedy engineers and developers, could happen again.. Sorry for the confusion.. Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of J.T. Shyman Sent: Thursday, March 13, 2008 10:42 AM To: [email protected] Subject: Re: What specifically breaks upgrades? ** I think Joe missed a word. It should be in the 6 hundred million range. (600000000-699999999) --- J.T. Shyman ---------------------------------------------------------------------------- -- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Moore, Christopher Allen Sent: Thursday, March 13, 2008 10:07 AM To: [email protected] Subject: Re: What specifically breaks upgrades? Joe- Sorry if I’m confused here, but I want to be sure I have this straight! I was just creating a field and I gave it an ID of 6,500,000 (you said “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..”) and got popup saying “You have specified a field ID in the reserved range…proceed?” I did not- but is that ok? Are you saying when we create new fields/workflow we should give it IDs over 6mil and ignore that warning? Chris ---------------------------------------------------------------------------- -- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of J.T. Shyman Sent: Wednesday, March 12, 2008 4:08 PM To: [email protected] Subject: Re: What specifically breaks upgrades? Rick, if you have the 7.1 Patch 2 email.linux.tar.gz file you can open it with Winzip or 7-zip and find the archgid utility in the /arsystem/linux folder. You can then copy this to your server. Unfortunately, getting the Windows version requires installing the Email application. --- J.T. Shyman ---------------------------------------------------------------------------- -- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Wednesday, March 12, 2008 4:41 PM To: [email protected] Subject: Re: What specifically breaks upgrades? ** Must be a Windows thing. It is not installed with AR System or Email on Linux RHEL. That's using the 7.1.0 patch 2 installs. Rick On Wed, Mar 12, 2008 at 11:38 AM, Joe D'Souza <[EMAIL PROTECTED]> wrote: ** Rick, It is released to the best of my knowledge.. It usually gets installed with the Email installation of 7.1? These are the initial results I get if I run it which sounds like it is the new version.. E:\Program Files\AR System\AREmail\KCH1D001>archgid Action Request System Change ID Utility Version 7.1.00 Build 200707311333 (c) Copyright 2002-2007 BMC Software, Inc. Enter user name: I haven't used this version of it to say if it works or not but I would assume it should.. Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Rick Cook Sent: Wednesday, March 12, 2008 2:11 PM To: [email protected] Subject: Re: What specifically breaks upgrades? ** Good advice, Joe, except that AFAIK, archgid isn't available for v7.1 yet - if it ever will be. I don't think the 7.0 one will work against 7.1. Rick 2008/3/12 Joe D'Souza <[EMAIL PROTECTED]>: ** 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: [email protected] 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.519 / Virus Database: 269.21.7/1328 - Release Date: 3/13/2008 11:31 AM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
