Skip to main content

We recently moved to an OData feed for one of our data sets, I am still fairly unfamiliar with this format. I am seeking to find out 1. if I am missing something in getting the Odata Reader to work 2. Failing that, what the recommended process would be to bring this data into FME.

 

The feed (https://itd-pr-test.infotechinc.com/AuthModelService.svc/), is behind our firewall so I copied the header and first item into odata_xml.txt. Using FME's Odata reader I used Basic authentication and the link above. When I try to access the Feeds parameter in the reader or enter one of the table names manually into this parameter, it generates the error found in log1.txt, the most usable part of the log states there is an issue with format.

 

After some research, I thought the Odata might be readable in a json format so I appended ?$format=json at the end of the feed to get the json version( first rows in format_json). This actually allows me to see the tables within the odata in the feeds parameter but when I run it leads to an error(log2.txt).

 

The main error here is:

OData Reader: The OData endpoint at 'https://itd-pr-test.infotechinc.com/AuthModelService.svc/?$format=json/$metadata' responded with XML when JSON was expected. It may be using a version of OData older than 2.0, which is unsupported by the FME OData plugin

 

The proper metadata link would be here: https://itd-pr-test.infotechinc.com/AuthModelService.svc/$metadata

followed by the ?$format=json command. The metadata Header found in metadata header.txt. I am wondering if there is a way to change this.

 

Happy to provide any more details, obviously some limits due to the inability to share the feed.

 

 

Hi @wthoman​ ,

 

Sorry to hear you are running into issues with this. Unfortunately this is going to be tough to troubleshoot since it's a private service.

 

If you are able to create a separate login and provide it to the support team they may be able to look into things and assist you further. I understand this might not be an option but if you are able to create a login for the support team, please feel free to send the details over to our support team via the submit a case portal and one of our experts would be happy to assist you with this!


log1 contains a HTTP error response:

The server encountered an error processing the request. The exception message is 'Access is denied.'. See server logs for more details.

So the problem appears to be an authorisation issue.


Reply