Thanks to everyone that replied. I finally decided to take a different approach to the filter so I wouldn't have to deal with this issue. Only so many hours in the day and one must make the best use of them.
Thanks again, Susan On Tue, May 17, 2011 at 3:36 AM, Ben Chernys < ben.cher...@softwaretoolhouse.com> wrote: > ** > > There are two “names” for enums. One is the definition of the enum as you > have queried for below. The other is a View based name and can change from > view to view. The view based name is called an “Alias”. > > > > Ensure that the view based names match the actual names by using the admin > tool and selecting each view in turn. The admin tool sometimes uses the > default or current view to resolve enum values and field labels (used in > query qualifications). > > > > Cheers > > Ben > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Susan Palmer > *Sent:* May-17-11 00:42 > > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Selection field enumId and value - where else can it be > hidden? > > > > ** > > select value, enumId FROM field_enum_values WHERE schemaId = '236' and > fieldId = '7' > > > > The actual number of values in this field have not changed since the field > was modified after initial form creation. > > > > > > On Mon, May 16, 2011 at 5:35 PM, Joe Martin D'Souza <jdso...@shyle.net> > wrote: > > ** > > No offence meant Susan.. Sometimes the best of us tend to overlook the most > simplest things.. That’s why they call our errors human errors :-) > > > > When you checked in your field_enum_data, what query did you use? I am > wondering if the old rows were not deleted in that table when the new rows > were inserted.. > > > > Joe > > > > *From:* Susan Palmer <suzanpal...@gmail.com> > > *Sent:* Monday, May 16, 2011 6:21 PM > > *Newsgroups:* public.remedy.arsystem.general > > *To:* arslist@ARSLIST.ORG > > *Subject:* Re: Selection field enumId and value - where else can it be > hidden? > > > > ** > > My apologies for not including our version info: > > ARS 7.0.1P2 using admin tool v7.0.1P3 > > Oracle 10g > > Custom form > > > > Only one view (default) on the form. > > Filter works when you eliminate that part of the qualification. > > Not wrong form or wrong field (trying not to be insulted.... :) ) > > Checked the alias and everything is appears as expected. > > > > Thanks so far ...... > > > > Susan > > > > > > On Mon, May 16, 2011 at 5:01 PM, Joe Martin D'Souza <jdso...@shyle.net> > wrote: > > ** > > > > You have checked in the right places and I am inclined to say that its > almost impossible for the old values to be validated as valid, when saving a > filter.. > > > > Since you say that you have even tried using the fields enumerated value > while saving the filter, the only other possibility is you are checking it > on the wrong form, or the wrong field or both.. > > > > Also, for a good measure, make sure that they don’t have the old value in > the alias.. > > > > Cheers > > > > Joe > > > > > > *From:* Susan Palmer <suzanpal...@gmail.com> > > *Sent:* Monday, May 16, 2011 5:51 PM > > *Newsgroups:* public.remedy.arsystem.general > > *To:* arslist@ARSLIST.ORG > > *Subject:* Selection field enumId and value - where else can it be hidden? > > > > ** > > Hi everyone, > > > > I need some help. Originally on a form I had numerous values defined in > selection field ID 7 (status). Several years later we changed the value > and alias on 3 of those selections within that field. The actual > 'numbering' did not change. When you look on the form everything is fine > and has been for years. > > > > So now to the dilemma .... I have a new filter in which the Run If contains > a qualification using one of those 3 'changed' values. > > > > It doesn't matter if I use the value or the enumId, after I save it, and > reopen it, it gives me the OLD value. So really who cares, because I always > thought everything really worked off the enumId in the background. > > > > BUT, the filter does not understand what it is supposed to do with it. No > error on filter save. The filter runs when it's supposed to but fails > qualification when that particular item does not match the run if. > > > > I've checked the form definition, the field definition, the > field_enum_values data and it's all what it is supposed to be. Where is > this old info hiding out? The filter is newly created. These particular > field selection values have not been used in a run if before so never saw > the issue. > > > > Thanks for your help in advance! > > > > Susan > > > > Susan Palmer > > ShopperTrak > > 200 W Monroe St > > 11th Floor > > Chicago, IL 60606 > > 312-529-5325 > > spal...@shoppertrak.com > > > > > > > > > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
