Lyle, I have a very similar problem with 3 table fields that I am copying from one form to another. They get field ID 100, 200 and 300. This seems to be only happening with this particular form and only for those table fields and only if the field ID already exists on the target. This is not the first time we are copying table fields from one form to another, but this is the first time that I see the system assigning the request ID to those values. It usually reset them to null if the request ID already exist on the target. I was hoping not to have to recreate those table.... And, if I add a regular field without being copied from another form on that specific form, I get the expected regular 53687xxxx field ID.
Thank you, Pascale Boyer [email protected] Sent by: [email protected] 09/02/2009 01:22 PM Please respond to [email protected] To [email protected] cc Subject Re: New fields added becomes Core fields ** Thanks for responding, Doug. In our environment, we do not ever directly update the database, so I don’t think this is what happened here. It appears to have changed just as a result of modifying the form. Now, I did manually enter field IDs for many of the fields as I was adding them to the forms (to make them match custom fields on other forms as well as ITSM fields that I was pulling data from). Additionally, I copied and pasted some fields from other forms (such as the Company field from HPD:Help Desk). Could either of those have reset the nextFieldID counter to a higher value? Thanks, Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mueller, Doug Sent: Wednesday, September 02, 2009 1:42 PM To: [email protected] Subject: Re: New fields added becomes Core fields ** Lyle, If I had to guess..... Someone wanted to reset the nextID value -- the ID for the entry ID -- and instead of resetting the nextID column, they reset the nextFieldID column -- the number to start at when looking for the next available field ID that is not used for auto assignment of field IDs. A good example of why to be VERY VERY VERY careful when making direct changes to the data dictionary. Make sure you are updating what you really are supposed to be and not something that looks close. I cannot gaurantee that this is what happened, but I do suspect that this is what happened. The names are similar. If you are not aware that there are two different columns, it is easy to pick the wrong one to update. Since the nextFieldID was added later to the table, it is likely the last column in the table so it is easy to see that one first..... Just a possibility (and a useful reminder to be careful in general regardless), Doug Mueller From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Lyle Taylor Sent: Wednesday, September 02, 2009 12:33 PM To: [email protected] Subject: Re: New fields added becomes Core fields ** So, what would cause it to change the next field ID to another range of numbers. For example, I recently created a new display only form and started adding fields to it with the same field ID as on other forms, and pretty soon, it was automatically assigning new field ID just above the fields I added. Thing is, I created a few related forms that shared field IDs across them, and, if I recall correctly, not all the forms started auto assigning new IDs in the upper range, so I’m wonder what triggers the change. Does that make sense? Thanks, Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Conny Martin Sent: Wednesday, September 02, 2009 1:01 PM To: [email protected] Subject: AW: New fields added becomes Core fields ** if you create a new form nextfieldid is initially set to 536870912, regardless if you create a field with a manually given fieldid or not. Von: Action Request System discussion list(ARSList) [mailto:[email protected]] Im Auftrag von Lyle Taylor Gesendet: Mittwoch, 2. September 2009 20:47 An: [email protected] Betreff: Re: New fields added becomes Core fields ** What sets the initial nexfieldid for a given form? For example, if I create a new form and add a new field and manually set the ID to XXXXX (and it’s not in the reserved range and higher than any other field on the form), will that plus one become the next field ID? Thanks, Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Conny Martin Sent: Wednesday, September 02, 2009 12:31 PM To: [email protected] Subject: AW: New fields added becomes Core fields ** Kali, with the following sql statement you can set nextfieldid to a safe number. UPDATE arschema SET nextfieldid = (SELECT MAX(fieldid) FROM field WHERE field.schemaid =arschema.schemaid) + 1 where name = '<Name of your form>' After that you must restart your arserver. Kind Regards Conny Von: Action Request System discussion list(ARSList) [mailto:[email protected]] Im Auftrag von Kali Obsum Gesendet: Mittwoch, 2. September 2009 03:05 An: [email protected] Betreff: Re: New fields added becomes Core fields ** Hi, The nextfieldid for that form is set to 23 (don't know how it happened). Is it safe to just manually set it to a certain id? How do i know what number is safe? Thanks! Regards, Kali From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Conny Martin Sent: Tuesday, 1 September 2009 2:49 PM To: [email protected] Subject: AW: New fields added becomes Core fields ** Kali, check the field nextfieldid in arschema with the following sql statement. select name, nextfieldid from arschema In normal case the nextfieldid contains something like 5368709xx HTH Kind Regards Conny Von: Action Request System discussion list(ARSList) [mailto:[email protected]] Im Auftrag von Kali Obsum Gesendet: Dienstag, 1. September 2009 08:16 An: [email protected] Betreff: New fields added becomes Core fields ** Hi, Everytime I add a new field in an existing form, the field is created as a Core field (DB id is set to 16,17,18 etc). Any ideas why this is happening? Regards, Kali NOTICE The information contained in this email is confidential. If you are not the intended recipient, you must not disclose or use the information in this email in any way. If you received it in error, please tell us immediately by return email and delete the document. We do not guarantee the integrity of any e-mails or attached files and are not responsible for any changes made to them by any other person. _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation.
