[Res] DataSoruce with mandatory and non mandatory fields

Hello,

There is an option called "include optional" under Files>Preferences>WSDL Settings, which includes optional elements on the request. Check that and let me know if it helps.

Regards,
Temil

Hi

Thank you for your response.

This option was already selected.

Regards,
UnitTesters

In SoapUI Pro, if you click on your Soap Test step, you should see the "TestRequest Properties" right below the Navigator window. For your request change "Remove Empty Content" property to "true".

This way your optional empty fields should not even generate an XML tag. Hopefully that helps.

Thanks,
Michael Giller
SmartBear Software

Thanks Michael

I will try this option and let you know if it resolves the problem

Thanks Michael,

This has resolved the issue

Hi Support Team,

I am trying to do something similar as mentioned in the initial comment.
Let me brief the issue one more time.
" I am reading data for my xml from an excel spreadsheet. Not all the xml elements have data all the time. So consider a case, when there is no data for some of the xml elements. For these kind of cases, I want to filter out the empty elements from the request xml, before it being submitted."

I am testing a REST service.

I tried changing the property, "Remove Empty Content" property to "true". But this did not help. Even after setting it to true, the empty tags in my xml are not being removed from the submitted request.

I confirmed this by seeing the request in the HTTP logs.

Any help is appreciated.

Thanks

Hi,

Unfortunately "Remove Empty Content" property applies to SOAP requests only. With REST requests we can't be sure whether the payload is XML, JSON, any text, etc. So there's no applied logic to remove XML.

For a workaround I would suggest using an event filter: http://www.soapui.org/Scripting-Propert ... dlers.html

So I have the following code that works in my instance but it is just a suggestion and requires full blown testing. This is not part of core SoapUI Pro offering and we can't provide support for it if there are edge cases where it fails.

You can create "RequestFilter.filterRequest" (http://www.soapui.org/Scripting-Propert ... dlers.html) and paste in the following code:

def groovyUtils = new com.eviware.soapui.support.GroovyUtils( context )
def stepName = context.getCurrentStep().getLabel()
def holder = groovyUtils.getXmlHolder( stepName + "#Request" )
// set default value here
def defaultVal = ""
for( item in holder.getDomNodes( "//*[. = '']" )){
     holder.removeDomNodes("//"+item.nodeName)
}
// update request 
holder.updateProperty()
// write updated request back to teststep
context.requestContent = holder.xml

**UPDATE (1/17/2014)**
I have since seen an issue with the above code. It leaves property expansion without evaluating it. Also, it didn't take into an account whether the node removed was an endnode. The following improved workaround code takes care of those issues:

def groovyUtils = new com.eviware.soapui.support.GroovyUtils( context )
def holder = groovyUtils.getXmlHolder( context.requestContent )


// find end nodes that also only consist of whitespace
for( item in holder.getDomNodes( "//*[normalize-space(.) = '' and count(*) = 0]" )){
 item.removeXobj()
}
// update request and write updated request back to teststep
holder.updateProperty()
context.requestContent = holder.xml

Thanks,
Michael Giller
SmartBear Software

Hello Michael,

In your groovy snippet, I did not completely understand what the following parts do.

// set default value here
def defaultVal = ""

for( item in holder.getDomNodes( "//*[. = '']" )){
holder.removeDomNodes("//"+item.nodeName)
}


1) Where is the defaultVal used?
2) I understood that in the for loop, you are getting an array of nodes into the holder and you are trying to remove the nodes. But I am not clear about what the Xpath mentioned in the for loop ( "//*[. = '']" ) is and ("//"+item.nodeName)?

Hi,

so is the script working for you?

1. defaultVal is not used, but you can add that to XPATH lookup as e.g.:

for( item in holder.getDomNodes( "//*[. = '" + defaultVal  + "']" )){

2. item is the object for the node and item.nodeName is the name of the XML node element

Thanks,
Michael Giller
SmartBear Software

When I used the same script in Event Handler, it did not work for me.

So, I created a custom groovy script for my issue.