Ask a Question

XPath Expression to RawRequests doesn't work after update to 1.8 version

microbBO
New Contributor

XPath Expression to RawRequests doesn't work after update to 1.8 version

Hi all, my early wrote XPath Expression based on Raw Requests return [], window with xml structure didn't open when I try create a new  one, in request set expression like a ${xxxx#RawRequest}  

Any ideas how I can fix it?

Note: I'm working with  SOAP 

19 REPLIES 19
TanyaYatskovska
Community Manager

Re: XPath Expression to RawRequests doesn't work after update to 1.8 version

Hi MicrobBO,

 

Sad to hear this. Could you please contact our Customer Care Team and send them your project (or at least an XPath expression you use)? They will investigate this behavior. You can reach out to them here:

http://support.smartbear.com/product-list/

 

---------
Tanya Yatskovskaya
SmartBear Community and Education Manager

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
joshcacho
Occasional Contributor

Re: XPath Expression to RawRequests doesn't work after update to 1.8 version

Hi All,

 

I have the same problem. Some of my input SOAP requests were input with RawRequest everywhere after updating to 1.8 and my Property Transfers which use Raw request as the "From" can't get transferred to the "To." Keep getting this dam Unexpected Element: CDATA. Everything was working before nicely but after I updated everything went to crap honestly.

 

Please fix this or let us know if we can roll back to a previous version. I tried rolling back to a previous version and it still didn't work.

 

Thanks,

 

Josh

 

 

joshcacho
Occasional Contributor

Re: XPath Expression to RawRequests doesn't work after update to 1.8 version

I have the same problem but also even more severe. Property Transfers not working for Raw requests anymore. So bad. Hoping for solution quickly. Being down or having no way to rollback to previous version is not working either.....

TanyaYatskovska
Community Manager

Re: XPath Expression to RawRequests doesn't work after update to 1.8 version

Hi All,

 

In Ready! API 1.8, we have improved the RawRequest property - now, it includes a request header. So, I suggest that you check XPath expressions you are using. As a new node for a header is added to a request, perhaps, your XPath became invalid. Please check this.

 

Refer to the following article to learn about the changes in Ready! API 1.8:

http://readyapi.smartbear.com/about/release_notes/latest/start

---------
Tanya Yatskovskaya
SmartBear Community and Education Manager

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
microbBO
New Contributor

Re: XPath Expression to RawRequests doesn't work after update to 1.8 version

Hi Tanya, in my case header doesn’t impact my request because I work with request body only. And this improvement doesn’t explain why when I try to create XPath expression through “Get Data” function by RawRequest property “Select Xpath Math” window didn’t open and expression like ${requestname#RawRequest} set

 

joshcacho
Occasional Contributor

Re: XPath Expression to RawRequests doesn't work after update to 1.8 version

I work the with body only also. I get a valid response from the request. However when I go to use the property transfer and select the raw request option then attempt to select the button on the right which allows me to choose the xpath for the node I want, I can't! It's greyed out. 

 

Only thing i can can see is even when the request is submitted and the response is received the indication of a success like other request is is not seen. I.e the test step is  not turning green like it used to. Again. I have not changed anything in my scripts as they were working. 

 

I entered a ticket but still no response. I'll try and send a screenshot later so you know what I mean. 

 

joshcacho
Occasional Contributor

Re: XPath Expression to RawRequests doesn't work after update to 1.8 version

Also. For both of us. Is their an example of this new raw request header. The documentation is very general. Screenshots would help

AntonE
Staff

Re: XPath Expression to RawRequests doesn't work after update to 1.8 version

Hi, microbBO and joshcacho

 

If you work only with bodies, you should use Request and Response properties instead of RawRequest and RawResponse. Raw versions contain the whole HTTP message, the way it is shown in Raw view of request and response editors, with HTTP status, headers etc. And Request and Response have only bodies.

 

Sorry for inconvenience. Before Request and RawRequest had the same values (without headers) by mistake and when we introduced RawResponse, we had to correct this, as some users wanted to check raw requests and responses as well.

 

As for examples - once a request is executed, values of all these properties are shown in Custom Properties tab under the Navigator.


Anton Egorov
ReadyAPI developer
lermimou
Occasional Contributor

Re: XPath Expression to RawRequests doesn't work after update to 1.8 version

Hi,

 

I my requests, i have thousands of parameters like

<urn:transactionId>${#Project#transactionId}</urn:transactionId>

So i can't use the request to retrieve the parameter.

I needed to use the rawRequest to have the parameter filled.

 

It's not possible to me to switch all parameters like

<urn:transactionId>${#Project#transactionId}</urn:transactionId> to a propertyTransfer in the request.

 

Please, how can I do?

cancel
Showing results for 
Search instead for 
Did you mean: