Just a guess, but double check all arschema entries for the 21 and here goes the standard question ... You did commit the changes when you updated arschema directly didn't you?
Fred -------- Original Message -------- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Kali Obsum Sent: Monday, September 14, 2009 9:38 PM To: arslist@ARSLIST.ORG Subject: Field Id being set to Core Field Hi, I've asked this question before but the proposed solutions doesn't seem to work. Background: everytime we create a new field in this form, the database id is being set to a core field (e.g. 21) We tried the following approaches: 1. Manually set the database id of the field to 702xxxxxx before saving. Result: database id still set to core field id after saving. 2. Set the nextFieldId in arschema to 702xxxxxx directly in the database. Result: database id still set to core field id after saving. after checking the nextFieldId in arschema, it has been reverted back to core field id. Anyone have any ideas how to solve this and why the nextFieldId is not being followed and being modified back to core field? Thanks! Regards, Kali _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
