Personally, I think it is the same sort of API changes that are preventing me from getting any entries at all out of ITSM 7 on ARS 7.1 with ARSPerl 190_701, even if I use the actual column ids, or even tell it to return ALL of the records in the form. One good look at HPD:Help Desk and you will realize that two teams of developers independently named all of the fields - one group created the labels, and another created the database names. Escalated? must have been an accident.
Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Wednesday, February 27, 2008 11:52 PM To: arslist@ARSLIST.ORG Subject: Re: 7.1 Server with 7.0 API - Qualification Error ** 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___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
