Everyone, I have had a review and testing done to confirm that there is no requirement for a Field 8 (the Short Description field) to be present on a form for Web Services to work. The team did tests using a view form without this field defined and there were no issues.
Tests were run on 7.6.04 and 8.1 just to be sure. Now, the question is whether the Web Service WSDL definition tries to reference a field 8 (maybe things were created when the form had a field 8 and it was removed or maybe someone copied from another form that had a field 8?) and the error is because it says to do something to field 8 but it doesn't exist on the form so the system is confused. Or, is the work getting to the server and workflow is seeing the error (logging on will show you this). I don't think this is the case from the style of the error returned. There can always be an issue of course, but fundamentally, there is no issue with Web Services and a field 8 requirement. Doug Mueller From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Tuesday, February 11, 2014 12:28 PM To: arslist@ARSLIST.ORG Subject: Re: View forms and Web Service ARERR 9130 ** it may be possible they 'fixed' this in later versions....it's been quite some time since I have challenged this 'knowledge' on newer versions of Remedy. On Tue, Feb 11, 2014 at 1:25 PM, Grooms, Frederick W <frederick.w.gro...@xo.com<mailto:frederick.w.gro...@xo.com>> wrote: LJ, I'm on 7.6.04 SP3 (Linux) and consume web services from several Display Only forms without this error (and those forms do not have Field 8) Display Only form has a button that does a Service Action to the same Display Only form. A service filter does a Web Service Set Fields action to consume a service from another app and return the data back to the user. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of LJ LongWing Sent: Tuesday, February 11, 2014 1:27 PM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: View forms and Web Service ARERR 9130 ** Web service plugin uses field 8, any form that consumes a web service must have a field 8 :) -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Grooms, Frederick W Sent: Tuesday, February 11, 2014 1:18 PM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: View forms and Web Service ARERR 9130 Check your mapping and workflow. We use web services against View and Join forms without this issue. What is your web service doing? If it is doing a Push fields to another form that may be where the issue is actually occurring. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Mac McMillan Sent: Tuesday, February 11, 2014 12:05 PM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: View forms and Web Service ARERR 9130 We use view forms in our application. Hence, not all the core fields are present. When executing a web service (probably on mid-tier also), an ARERR 9130 occurs and report "???: <8> Field does not exist ..." and a http 500 error is returned (Internal Server Error). I haven't touched a remedy web service since, well, it's been a while. Any ideas on a work around? TIA, ==Mac _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> "Where the Answers Are, and have been for 20 years" _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"
