When you say the the REST WSC has stopped returning data but the data can be seen in the logs, you can check:
1. If there are any errors after the data printed in the Verbose log.
2. You can verify if the structure of the response defined in the REST WSC is same as the actual structure of the response received.
Most probably, the response is not getting parsed into the correct ports.
Thank you for the response, and you got it! Yes, it was the structure of the response. The vendor had changed it and my schema didn't have three fields that were in the response. There were no errors after the data was printed in the Verbose log. I've tested the change and it was successful in my DEV/TEST environment, so it will run in the prod environment tonight.
The vendor was surprised that our tool could not return any data without all the response fields defined in our schema. This is expected behavior of the REST WSC, correct? Is there any other configuration in the schema I could have done to make it more flexible?
A screen print of the XSD schema file is below. The "recordsActive" and "CreatedDateString" elements were missing prior.
1 of 1 people found this helpful
Our tool could not return any data without all the response fields defined in our schema - this is generally true.
(There might be other scenarios like errors & partial data returned depending on the position and groups of the elements / ports that are missing.)
Akanksha, Thanks for the response. Yes, I figured that was the case. Thanks for your time.