I have managed to narrow down where the error is comming from.
It this code:
<api:set attr="Header:Name#" value="SOAPAction"/>TX is expecting XML but is getting ASMX
Edit: that getData.asmx should be the URI of the WDSL I believe.
@RLB
What if you use POST instead of GET? Looks like you are using POST in Postman.
moving futher
I have changed this:
<api:set attr="URI" value="https://your.soap.endpoint.com/getData.asmx" />to
<api:set attr="URI" value="https://your.soap.endpoint.com/getData.asmx?WDSL" />which returns an XML.
Now, i dont get the error above.
This is what i use in POSTMAN to get a response
I have refined the code in RSD-file to this
<api:script xmlns:api="http://apiscript.com/ns?v1" xmlns:xs="http://www.w3.org/2001/XMLSchema">I dont get any error in TX but when i preview the table its empty.
In WSDL, ListPublishedFiles that i am trying to reterive is this:
<s:element name="ListPublishedFiles">The only differnece i see now is that in the guide the code that replicates what i have in POSTMAN Body is this
<uen:Esws.getUsers soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">While i have copy-.pasted it as it from POSTMAN
<pub:ListPublishedFiles>Whats the difference ?
Hi @aftabp
You run the parts in a sort of wrong order.
Did you see this
I would think it should be structured like this.
<api:script xmlns:api="http://apiscript.com/ns?v1" xmlns:xs="http://www.w3.org/2001/XMLSchema">
@Thomas Lind
Hi @aftabp
<api:script xmlns:api="http://apiscript.com/ns?v1" xmlns:xs="http://www.w3.org/2001/XMLSchema">I think I found the issue. Also, turn on logging when you get errors, it will tell you more about what is going on
@Thomas Lind
In my SOAP endpoint, ListPublishedFiles is like this.
<s:element name="ListPublishedFiles">In POSTMAN, i write this in HEADER
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:pub="http://publicprocurement.com">
do i need to use the tags from SOAP endpoint?
The stuff you run in postman should be the closest, but you need to encode it as xml for it to run.
I do notice a difference between what you use in Postman and what you have in the RSD file.
<pub:ListPublishedFiles> in the Postman setup is <pub:ListPublishedFiles soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding"/> in the RSD.
Can you make these queries exactly the same in both and see what happens?
@Thomas Lind
The last code that you suggesed gives me an error.
<!-- The GET method corresponds to SELECT. Here you can override the default processing of the SELECT statement. The results of processing are pushed to the schema's output. See SELECT Execution for more information. -->
However when i use the following code without the lines below, i get an empty table
<api:script method="GET">Here is what i use
<?xml version="1.0" encoding="utf-8"?>
Hi @aftabp
Yes, it is not doing a post call anymore. Did you turn on logging, that will explain why it was seen as a bad request as it shows the code being executed.
2024-12-12T12:53:29.052+01:00 1 [4|Q-Id] [INFO|Connec] Opened REST connection. Version: 23.0.8685.0. Edition: [ADO.NET Provider .NET 4.0].
Finally managed to get a response.
Here is the code
<api:script xmlns:api="http://apiscript.com/ns?v1" xmlns:xs="http://www.w3.org/2001/XMLSchema">
Your Postman example uses Content-Type raw, your call from the CData provider uses both application/x-www-form-urlencoded and text/xml. Something to look into I guess.
Hi @aftabp
You were missing a content type header. I think that is one of those things that are easy to miss, but that is where logging really helps.
I checked if we had this in the other community post about soap and there we applied it like so
<api:set attr="Header:Name" value="Content-Type" />Your method is equally fine and I also find that for CData, this option needs to be stated without the dash so it is contenttype in one word.
He had that exact same content type header in his first example though.
One more question.
<contracts>I have manged to get the project details but struggling with:
origin tid referencenumber Here is what i am trying
<api:info title="contracts/contract" desc="Generated schema file." xmlns:other="http://apiscript.com/ns?v1">
Something like:
other:xPath="/Envelope/Body/ListShortContractsPublishedForExportXMLBusinessIntelligenceResponse/ListShortContractsPublishedForExportXMLBusinessIntelligenceResult/idbdata/contracts/contract@origin
Hi @RLB
He had that exact same content type header in his first example though.
It most likely did not work due to the dash between Content-Type, but would have if it didn’t have it. I do prefer the way used in the last method as it only takes up one row in the file.
Hi @aftabp
You may need multiple XPaths and the DataModel set to FLATTENDOCUMENT
Here is a RSD file based on a currency file.
<api:script xmlns:api="http://apiscript.com/ns?v1" xmlns:xs="http://www.w3.org/2001/XMLSchema">I use multiple XPaths to get both date and the values.
I do not use @ signs in the XPath, but there is in the connection to the value in the <info> area.
