Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

XML Document returns no matches

I'm using CRS 3.5 (Queue Manager IP IVR) and in a few scripts I'm reading an XML document to get some data.

What can I do when I don't get any data back?

Is there an exception I can capture?

thanks

1 ACCEPTED SOLUTION

Accepted Solutions
VIP Super Bronze

Re: XML Document returns no matches

If you debug the script, and a match was not found, what does the HMO_TFN variable have for a value immediately after the Extract XML Doc Data step?

Please remember to rate helpful responses and identify helpful or
4 REPLIES
VIP Super Bronze

Re: XML Document returns no matches

There are a few document exceptions which you can use. They typically catch when there is a syntax error in the XML for example. If a specific value had nothing in it, the variable should be null. You can use a simple If statement at that point.

Please remember to rate helpful responses and identify helpful or
New Member

Re: XML Document returns no matches

Thanks for the reply, I used an If statement but it still doesn't work.

I'm using an "Extract XML Doc Data" step with xpath "//SSC/DNIS[ENTITY=" + Entity_ID + "]/TFN".

If there's a match it copies the result into a variable called HMO_TFN which I then pass through a number of variables using the java substring(x,x) class; but if it doesn't find a match it fails... but it fails at the first instance of the substring(x,x) though and not really after the extract xml object.

VIP Super Bronze

Re: XML Document returns no matches

If you debug the script, and a match was not found, what does the HMO_TFN variable have for a value immediately after the Extract XML Doc Data step?

Please remember to rate helpful responses and identify helpful or
New Member

Re: XML Document returns no matches

I ended up using a DocumentException and that did it.

thanks for your help

198
Views
0
Helpful
4
Replies