Unfortunately, Doug, we do need to map the field, because the developer who built the custom app re-purposed the Short Description field to hold a foreign key, without which the whole interface is pretty much useless.
Yeah, I know... On Sat, Mar 15, 2014 at 6:15 AM, Blairing <d...@blairing.com> wrote: > Rick, > > I have run into something similar recently on a 7.5 system. Take a look at > the WSDL file and find a line for the Short Description field. If you > auto-generated the file on the target server at some point (while building > the web service you push to) you will probably find all the core fields > there with a minOccurs="1", which makes them required in WSDL-speak. Even > if that field is not included in the values you send or consume the > minOccurs means it has to be present. We set the field to the text "not > used" on the sending side but did not map it and that seems to work. > > Incidentally, we decided to use DSO to do something similar as that > protocol allows for re-tries and returns. There is always more than one way > to do it :-) > > Doug > > -- > Doug Blair > +1 224-558-5462 > > Sent from my iPad Air > Auto-corrected typos, misspellings and non-sequiturs are gratefully > attributed to Steve Jobs :-) > > > On Mar 14, 2014, at 9:45 AM, Rick Cook <remedyr...@gmail.com> wrote: > > > > I have two Remedy systems, a 7.6.04 ITSM box and a 7.1 custom one. I > have two web services that allow a custom bare bones ticketing system on > the custom server to interact with the ITSM server, so that a record > created under certain conditions on one box will create a corresponding > record on the other. > > > > There is a bit of custom code and configuration data in place to > facilitate all of that, and it seems fine. The WSDL in the web service > displays the XML fine, as does SoapUI. The problem is that when I attempt > to actually fire it, I get an error that the logs don't seem to capture at > a fine enough level of detail to help me find the root of. The error, > "Error encountered while executing a Web Service", is complaining that > Field ID 8 (Short Description) is NULL, and therefore the record can't be > saved (since it's a required field). That field has a default value in it > in every form we use in the process, and we even map that field between > forms to ensure that a value is being pushed, but the error continues. > > > > Has anyone had a problem like this before, or can someone point me to > the next thing to try? AR Error logs aren't showing anything, and the > Plug-in logs don't say anything useful either. > > > > Rick Cook > > > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > "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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
