Joe, There is nothing wrong with the qualification I am using. Like I said, the same qualification works on the same form in ARS 6.0, 6.3, and 7.0. Since this call is made through the API we have to use the field name, not the field label, so the last item on the list you provided isn't valid for this situation.
I have tried all of the following: 'Status' = "New" 'Status*' = "New" '7' = "New" The only one that worked is the last one, which uses the field ID. This is less than ideal because it is unreadable by anyone other than a Remedy admin. Obviously this simple query isn't too hard, but using a combination of multiple fields will get unreadable quickly. Jack On 2/27/08, Joe D'Souza <[EMAIL PROTECTED]> wrote: > > ** Jack, > > According to the Error message description for this error this error > occurs when: > > The field referenced in the search line is not a recognized field on the > current form. This error often has one of the following causes: > > * Omitting the single quotation marks around a field reference that > contains spaces or other special characters > > * Using single quotation marks around a value when double quotation marks > must be used > > * Omitting double quotation marks from around a value > > * Specifying an invalid field label > > Fix the format of the line, and perform the search again. > > Check all these and if you still have a problem write back.. > > Joe > > -----Original Message----- > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] Behalf Of *Jack Boespflug > *Sent:* Wednesday, February 27, 2008 10:34 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: 7.1 Server with 7.0 API - Qualification Error > > ** Correction, the ARERR is 1587. > > On 2/27/08, Jack Boespflug <[EMAIL PROTECTED]> wrote: > > > > We are using the 7.0 API with a 7.1 AR Server, and are having problems > > with > > qualifications. > > > > If a qualification used with the API accesses a field where the field > > label > > is the same as the field name, there is no problem. Qualifications work > > just fine. If a qualification used with the API accesses a field where > > the > > field label and name differ, we are getting an ARERR 1589 error. > > > > So if a form has a status field with label 'Status' and field name > > 'Status', > > a qualification of 'Status' = "New" will work just fine with the 7.0 API > > and > > 7.1 server. > > > > If the form has a status field with label 'Status*', and field name > > 'Status', a qualification of 'Status' = "New" will not work. This same > > query does work with a 7.0 server however. > > > > We cannot use the 7.1 API yet, as our codebase is still using the old > > API > > classes. > > > > Does anybody have any knowledge regarding this issue? > > > > > > -- > Jack Boespflug > Kinetic Data, Inc. > 235 E. 6th Street, Suite 400B > St. Paul, MN 55101 > 651-556-0928 > [EMAIL PROTECTED] > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ -- Jack Boespflug Kinetic Data, Inc. 235 E. 6th Street, Suite 400B St. Paul, MN 55101 651-556-0928 [EMAIL PROTECTED] _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
