Well, the issue with creating a standard for this is that there are multiple ways to do it effectively, none probably significantly better than the others.
As to why the 536...* range isn't preferred, for me it is merely cosmetic. Anything that starts with a 6 or higher means a custom field. As to ranges, you can separate those by application, developer, field type, form, etc. I have done it a few different ways, and it really depends on what system works best for your team and that you have the will and the means to enforce. You could easily use the metatables to create a form that would choose the next field IDs for you based on any formula you wished, or just keep one master form with all of the custom fields on it, and copy all new fields from that form to ensure consistent characteristics and attributes. I would bet that there are one or more of the good Remedy utility programs that could assist you with choosing the next field ID for a form. Lots of ways to skin that cat. So which system you use isn't nearly as important as using one that works for you. Rick On Fri, Sep 9, 2011 at 6:31 AM, Andrew C Goodall <[email protected]>wrote: > It would be nice if BMC helped drive that effort! > > I like the idea of the prefix - or perhaps some other flag to denote > company creator. > > Can someone please explain why the default 536xxxx range is not a good > choice for custom fields - thanks. > > Regards, > > Andrew Goodall > Software Engineer 2 | Development Services | jcpenney . www.jcp.com > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Meyer, Jennifer L > Sent: Friday, September 09, 2011 8:26 AM > To: [email protected] > Subject: Re: EXTERNAL: Re: "Outside of Reserved Range" warning? > > This thread is fascinating. I think this may be the forum to decide on > a development standard for Database IDs so when we share workflow with > each other, we are all using the same standard. > > Jennifer Meyer > Remedy Technical Support Specialist > State of North Carolina > Office of Information Technology Services > Service Delivery Division ITSM & ITAM Services > Office: 919-754-6543 > ITS Service Desk: 919-754-6000 > [email protected] > http://its.state.nc.us > > E-mail correspondence to and from this address may be subject to the > North Carolina Public Records Law and may be disclosed to third parties > only by an authorized State Official. > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Reiser, John J > Sent: Friday, September 09, 2011 9:20 AM > To: [email protected] > Subject: Re: EXTERNAL: Re: "Outside of Reserved Range" warning? > > Joe, > Re. your rant about field IDs needing alphas. That would be a great > idea if > BMC could pull it off. > The range of ID numbers that I use a pulled from the telephone keypad. > TPAG forms all have ids that start 872400000 - 872499999 > MRBC forms 672200000 - 672299999 etc > When I get a prefix that would be below 536870912 (that number in burned > into my memory) I add 1 as the left most digit 1536870912 which is still > in > the acceptable range for developers. > > The place this has failed me is when I want to reuse a modular > form/workflow > combination and the key field ID starts 8724xxxxx and the modular part > is > looking for a field id of 6722xxxxx. > Makes me want to rethink it and build everything as if it will always > interact with other objects in the system. > > --- > John J. Reiser > Remedy Developer/Administrator > Senior Software Development Analyst > Lockheed Martin - MS2 > The star that burns twice as bright burns half as long. > Pay close attention and be illuminated by its brilliance. - paraphrased > by > me > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Joe Martin D'Souza > Sent: Thursday, September 08, 2011 3:02 PM > To: [email protected] > Subject: EXTERNAL: Re: "Outside of Reserved Range" warning? > > Yup :-) I think that was when I first learnt the use of archgid.. > > Unfortunately we found it out at a customer that didn't have a separate > development server.. Fortunately for them though, they had very few > customizations that were lost and were able to redo it within a few > days.. > And they still didn't bother to invest in a development server after > that.. > Go figure.. > > Joe > > -----Original Message----- > From: Meyer, Jennifer L > Sent: Thursday, September 08, 2011 2:40 PM Newsgroups: > public.remedy.arsystem.general > To: [email protected] > Subject: Re: "Outside of Reserved Range" warning? > > I remember that upgrade! > > Ahh, the good old days. > > Jennifer Meyer > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Joe Martin D'Souza > Sent: Thursday, September 08, 2011 12:20 PM > To: [email protected] > Subject: Re: "Outside of Reserved Range" warning? > > David, > > There was one version, I think when moving from 4 to 4.5 or somewhere > thereabouts, where Remedy Engineering accidently used the starting > non-reserved range 536,xxx,xxx that messed up some customizations that > were > done using that starting non reserved field ID's. Since that time my > personal preference was never to use that, even if it is a trim field > (line, > > box, text) you are creating.. Until then I happily used that range for > those > > kind of fields. With the introduction of shared workflow, choosing your > field ID's became even more important even for some trim fields like > text > fields.. > > So my personal preference was to use the 800,xxx,xxx to 999,999,999 > range > but I see nothing wrong with starting from 600,xxx,xxx... > > Choosing this higher number deliberately, you can almost guarantee > yourself > that an accidental intrusion by BMC Softwares engineers on the > 536,xxx,xxx > in any future patches or releases will not impact your customization.. > There > > is hardly a chance they would use the 600,xxx,xxx to 999,999,999 range > deliberately.. > > Cheers > > Joe > > -----Original Message----- > From: David Durling > Sent: Thursday, September 08, 2011 8:43 AM Newsgroups: > public.remedy.arsystem.general > To: [email protected] > Subject: Re: "Outside of Reserved Range" warning? > > Is starting at 600,000,000 just a convention people in the ARS community > > have chosen, or is there a real risk of running into a problem by > starting > at the 536,xxx,xxx range the system will use by default if you're > creating a > > new form? > > According to KA315200, a field range of 536870913 to 2147483647 can be > used > for ARS 7.1 and 7.5. > > David Durling > University of Georgia > > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) > > [mailto:[email protected]] On Behalf Of White, Michael W (Mike) > > Sent: Wednesday, September 07, 2011 4:20 PM > > To: [email protected] > > Subject: Re: "Outside of Reserved Range" warning? > > > > "I seem to recall that 600,000,000 to 999,999,999 is reserved for > custom > > development.". > > > > We roll our own and use that range. > > > > Mike White > > EMail [email protected] > > Office 813.978.2192 > > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) > > [mailto:[email protected]] On Behalf Of Logan, Kelly > > Sent: Wednesday, September 07, 2011 4:14 PM > > To: [email protected] > > Subject: Re: "Outside of Reserved Range" warning? > > > > "One. . .Two. . .I think you're right. . ." > > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) > > [mailto:[email protected]] On Behalf Of Tommy Morris > > Sent: Wednesday, September 07, 2011 12:20 PM > > To: [email protected] > > Subject: Re: "Outside of Reserved Range" warning? > > > > Yeah, I meant 600 million. I still have trouble counting to 5 so > numbers > > larger > > than that stump me. :) > > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) > > [mailto:[email protected]] On Behalf Of Meyer, Jennifer L > > Sent: Wednesday, September 07, 2011 11:19 AM > > To: [email protected] > > Subject: Re: "Outside of Reserved Range" warning? > > > > Huh. I suspect it's the number of digits in your ID that's causing > the > > issue. I > > seem to recall that 600,000,000 to 999,999,999 is reserved for custom > > development. Field IDs 599,999,999 and below are for BMC's use, but I > > don't > > recall anything about using IDs above 1,000,000,000. > > > > Jennifer Meyer > > Remedy Technical Support Specialist > > State of North Carolina > > Office of Information Technology Services Service Delivery Division > ITSM & > > ITAM Services > > Office: 919-754-6543 > > ITS Service Desk: 919-754-6000 > > [email protected] > > http://its.state.nc.us > > > > E-mail correspondence to and from this address may be subject to the > North > > Carolina Public Records Law and may be disclosed to third parties only > by > > an > > authorized State Official. > > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) > > [mailto:[email protected]] On Behalf Of Reiser, John J > > Sent: Wednesday, September 07, 2011 12:03 PM > > To: [email protected] > > Subject: "Outside of Reserved Range" warning? > > > > Hello Listers, > > ARS 7.6.03 > > MS SQL Server 2005 > > VMWare Windows 2003 Enterprise > > I've been working in the Dev Studio for a while and I keep getting the > > following response when I create fields. > > "You have specified an id for the following fields which is outside > the > > BMC > > reserved range. Do you want to continue?" > > I could see a warning for creating a field inside the range of > reserved > > field ids > > but outside? > > Is there a config setting in Dev Studio to stop this message? > > The field ids that I use are all between 1,587,700,000 and > 1,587,711,199 > > > > Thanks, > > --- > > John J. Reiser > > Remedy Developer/Administrator > > Senior Software Development Analyst > > Lockheed Martin - MS2 > > The star that burns twice as bright burns half as long. > > Pay close attention and be illuminated by its brilliance. - > paraphrased by > > me > > ________________________________________________________________________ > ____ > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > > ________________________________________________________________________ > _______ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > > ________________________________________________________________________ > _______ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. If the reader of this message is not the intended recipient, > you are hereby notified that your access is unauthorized, and any review, > dissemination, distribution or copying of this message including any > attachments is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete the material from any > computer. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
