Hello Sounds like you want to stop storing the data in the database, but to keep any workflow that is associated with the field, is that correct?
If so, I would do the following: 1- take a note of the field ID of xInitialValue 2- in Remedy Admin, select xInitialValue and then go Edit - Copy. 3- delete xInitialValue and save the form (nb ONLY do this if you are happy to lose all the data that has been stored in this field up to now) 4 - Go to Edit - Paste. This will copy the field back in. Make sure that the field ID is the same as it was in point 1. If not, amend it. Change field label and Database Name if required. Before you press save, change the Entry Mode from Optional or Required to Display Only. I'd recommend testing this on a test system first, don't just take my word for it! Or create a test form with an optional field called xInitialValue in it, add some workflow, add some records, then try the technique above and see what happens. If I've understood what you're trying to do, this should be straightforward. Unless of course there are other parts of your system that rely on the data being stored in this field. If you don't want to lose the existing data in the field xInitialValue, DO NOT use this approach! Once its deleted that's it, the data is gone. In fact, before you start, its probably best to extract the data from xInitialValue along with the request ID so that if for some reason you want to restore it, you can change it back to an optional or required field, and then import the data back in. All the best Isabel -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Ponzo Sent: 18 April 2008 00:09 To: arslist@ARSLIST.ORG Subject: Re: Field Conversion Jean, The data is stored in the database using the Field ID, not the label value. Changing the label will not affect the data. If you are considering deleting the old field and creating a new field then you will lose the data. The way to do that is to create the new field and copy all of the old data to the new field. Rick Ponzo Hugo Kom Lan wrote: > ** Hi everyone, > > I've been working with a form for a while where there is a stored > field called, say, xInitialValue. Now I want to convert this field to > a temporary field zInitialValue because we don't need those values > stored anylonger. Does anyone know what the repercussion of such a > conversion will be? What would happen to the values already stored in > the database under the old field name xInitialValue? > We are using Oracle 9i > ARS 6.0 > > Thanks for your help! > > Jean > > ---------------------------------------------------------------------- > -- > Use video conversation to talk face-to-face with Windows Live > Messenger. Get started! > <http://www.windowslive.com/messenger/connect_your_way.html?ocid=TXT_TAG LM_WL_Refresh_messenger_video_042008>__Platinum > Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" Glasgow - Proud Host City of the 2014 Commonwealth Games ---------------------------------------------------------------------------- Disclaimer: This message is intended only for use of the addressee. If this message was sent to you in error, please notify the sender and delete this message. Glasgow City Council cannot accept responsibility for viruses, so please scan attachments. Views expressed in this message do not necessarily reflect those of the Council who will not necessarily be bound by its contents. ---------------------------------------------------------------------------- _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
