Hi Vidyasagar, Unfortunately, no...Remedy is going to display the set of "Selections" (as they call them) in increasing order of the "ID" (the underlying number). To be clear, the "Custom" mapping mechanism you asked about in your first email would not change this.
If this is important, I can think of a work-around (using a display-only field and some workflow). But before I seriously suggest making the situation that much more complex, I'd first suggest that you re-examine your reasons for making the change in the first place. You didn't discuss these reasons, but my first guess is that someone wants to consume the data in a report, and wants those values mapped in the "new" way. If so, a simpler solution might have been to make the change when querying the data for the report in a way similar to the UPDATE statement I mentioned last time. So, when pulling the data for the report, that user could do something like: SELECT <other stuff> CASE WHEN Text = 0 THEN 1 ELSE 0 END AS "Text" FROM SomeForm If the user can't execute a SQL query (and their reporting tool doesn't provide a similar mechanism - which would be surprising), then you could create a SQL view that has this remapping and have the user use that SQL view. Though, again, this would be adding a lot of complexity to solve a seemingly simple requirement (it's at this point I'd really start to drill into those reasons for the requirement to see just how important it is). If you want to use a purely Remedy based way to get the underlying values you want along with the "Yes" then "No" ordering of the radio button, do this... 1. Copy and paste the 'Text' field to create a new field and change it's database name to 'DO Text' (or something), but leave the label alone. 2. Set the "Entry Mode" of the 'DO Text' field to "Display". 3. Change the Selections mapping (of the new 'DO Text' field) so that it's matches the original "Yes" - 0, "No" - 1 4. Put the existing 'Text' field onto some hidden page, or make it invisible, and move the new 'DO Text' field into the original's position so that it looks like nothing has changed. 5. Create an Active Link triggered on Window Loaded that sets 'DO Text' to "Yes" when 'Text' is set to "Yes", and "No" when 'Text' is set to "No" 6. Create an Active Link triggered on Return with the Field set to 'DO Text' that sets 'Text' to "Yes" when 'DO Text' is set to "Yes", and to "No" when 'DO Text' is set to "No". Again, this is a lot of additional complexity to meet a seemingly simple requirement. I wonder if it's worth it. Let me know if any of this is not clear or you have any questions. Thanks, Charlie On Fri, Apr 25, 2014 at 12:33 AM, vidyasagar kommu < [email protected]> wrote: > ** > Hi Charlie , > > One more question . > Once we change the attribute value of as Yes =“1” and No =“0” form the > front end radio button field is displaying like (field No Yes). > I belive it was taking assending order while displaying the fields. > Is there any workaround on this? > > > On Fri, Apr 25, 2014 at 12:53 PM, vidyasagar kommu < > [email protected]> wrote: > >> Thanks a lot charlie........ >> ... >> >> On Mon, Apr 21, 2014 at 12:08 AM, Charlie Lotridge >> <[email protected]>wrote: >> >>> ** >>> No, there's no need to use the "custom" enumeration type, you just need >>> to go in and switch the "Yes" name (and labels on all views) to "No", and >>> the "No" name and labels to "Yes". >>> >>> HOWEVER you must change the existing data to match the new mapping. I'd >>> recommend using SQL to execute a command like the following (let's assume >>> the form name is "SomeForm"): >>> >>> UPDATE SomeForm >>> SET Text = CASE WHEN Text = 0 THEN 1 ELSE 0 END >>> >>> Note that I'm assuming that your enumeration doesn't have any other >>> values besides Yes (currently mapped to 0) and No (currently mapped to 1). >>> >>> Hope this helps. >>> >>> -charlie >>> >>> >>> On Fri, Apr 18, 2014 at 6:59 AM, vidyasagar kommu < >>> [email protected]> wrote: >>> >>>> ** >>>> Hi All, >>>> >>>> existing behaviour In a regualr form i have radio button field name >>>> ‘Text’ = ‘YES’and Data base value as “0” and ‘Text'= ‘NO’ and the >>>> Data base value as “1”. >>>> There is no default value >>>> >>>> >>>> >>>> New requirement is 'Text'= ‘YES’ and database value should be “1” >>>> and 'Text’= ‘NO’ then database value should be “0”. >>>> ‘Text' field Default value should be “No” >>>> >>>> Could you please let me know how do I change the database Id of the >>>> existing field i.e 'Text' >>>> Is there any Impact on existing Orders ? >>>> >>>> Should we convert the field Linear to Custom ....If you go to field >>>> properties under Attributies---we have option call Custom should we change >>>> the data base ID ? >>>> >>>> >>>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>> >>> >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>> >> >> >> >> -- >> Sagar > > > > > -- > Sagar _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"
