Yes there are a few core forms (User, Group, AR System Email Messages) that have some system fields IDs (often 3 digits) that can wreak havoc if you do a Save As of the form. Even if use a few those very special field IDs on a custom form the system will often reference your form for its special purpose. At least it would in 6.x or early 7.x.
Jason On Tue, Aug 26, 2014 at 9:38 AM, Joe D'Souza <jdso...@shyle.net> wrote: > ** > > This is a custom form (that will stage data to massage it if required and > then push to the Load forms), so BMC won’t be touching it unless off course > if by chance they happen to name a form that starts with STG: followed by > the exact same name I use J. Then I’ll be pretty much shot down J. > > > > To further ensure that won’t happen, I’m thinking of naming them > STG:<customer abbr>:<form name> > > > > I won’t be creating anything in the reserved ranges – just copying the > ITSM foundation fields that I am mapping with an external data source. > > > > A long time ago I recall a problem when the whole user form was backed up > and saved as User 2. I think we had the system confused and we started > getting authentication errors although the original User form was intact. > This was either in the 3.2 days or early 4 days. > > > > That’s why I thought I would be cautious just in case some of the > Foundation form field ID’s meant something internally to the system. > > > > Joe > > > ------------------------------ > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *arslist > *Sent:* Tuesday, August 26, 2014 11:15 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Using an ID like 1000000001 (BMC Software's development > field range) in a home grown custom form... > > > > I have always considered it best practice that if you are using a field in > a custom form for the same purpose it exists in the ITSM Suite, to actually > use the same field id (sometimes doing a copy and paste from the ITSM form > to the new form). > > > > Main caveat is permissions and ensuring you get the ones you need. > > > > If you are creating a new field for a new purpose, then the reserved > ranges are important since you don’t want BMC to create a field with the > same field id you used. > > > > Dan > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Joe D'Souza > *Sent:* August 26, 2014 10:25 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Using an ID like 1000000001 (BMC Software's development field > range) in a home grown custom form... > > > > ** > > Is there any repercussion from using a field ID like 1000000001 in a > custom build form? > > > > This field ID is the Company field ID in the COM:Company form and I wanted > to build a ‘staging/integration’ form to accept data using AIE, process it > if necessary, before I push it to the ‘Load’ form. To make the Push fields > easier and speed up my development time, I wanted to use the same Field > ID’s and Field names. > > > > The above specific ID was just an example. I intend using the same ID’s > for other staging forms I build for location, site, people etc. as the ID’s > in their respective foundation forms. > > > > To the best of my knowledge from the documented reserved ranges, the > ranges used for the foundation data in the foundation forms, are not > reserved ranges for any functional type of fields. Sure they are within the > BMC Software range that is used by their developers for their applications, > but since this staging/integration form is fully custom, I see no harm > using those Field ID’s.. Did anyone have any issues doing the same? > > > > Joe > _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: > "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
