Are you able to share the ODATA link with us?

 

 

---

Sure, It's a link behind our firewall though. Here it is

http://avid/odata/V4/fleet/vehicle_master_by_user_org?$format=json

---

Sure, It's a link behind our firewall though. Here it is

http://avid/odata/V4/fleet/vehicle_master_by_user_org?$format=json

Can you try removing the "vehicle_master_by_user_org?$format=json" part from the URL then click the "..." button on Feed list when in the Paramaters?

 

Does that give you a list of layers? including "vehicle_master_by_user_org" to choose from?

 

 

---

Good morning Matt, thanks for helping me look into this.

 

I tried

 

http://avid/odata/V4/fleet/

 

and

 

http://avid/odata/V4/fleet

 

I still just get a spinning bar when I click on "Field List" ...

 

 

Should "Field List" contain "vehicle_master_by_user_org?$format=json" ?

 

 

Thanks,

 

Fernando

 

 

---

Hi @fizquierdo - Here's the documentation on our Odata reader: http://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/odata/odata_reader.htm?

 

Please read the requirements carefully. In addition you will find an example Odata link which you can test out to make sure that FME is working correctly on your machine. If that Link isn't working then it might be specific to your machine.

 

 

I'm not overly familiar with the OData side of things, but the "$format=json" part isn't needed here. I was expecting the "vehicle_master_by_user_org" to be in the feed list but it's seems like it's not quite working as I would expect. 

From our documentation we say that 

The dataset can be one of the following: an OData service, represented by a service root URI, or an OData feed, represented by a service root URI plus a specific resource path.

Something which might give you some more information as to what's going wrong it to turn on Debug logging (Tools>FME Options>Translation>check the Log Debug box). You can then try re-adding the Odata reader and clicking the feed list button and see if there is any other information.

---

Hi @fizquierdo - Here's the documentation on our Odata reader: http://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/odata/odata_reader.htm?

 

Please read the requirements carefully. In addition you will find an example Odata link which you can test out to make sure that FME is working correctly on your machine. If that Link isn't working then it might be specific to your machine.

 

 

I'm not overly familiar with the OData side of things, but the "$format=json" part isn't needed here. I was expecting the "vehicle_master_by_user_org" to be in the feed list but it's seems like it's not quite working as I would expect. 

From our documentation we say that 

The dataset can be one of the following: an OData service, represented by a service root URI, or an OData feed, represented by a service root URI plus a specific resource path.

Something which might give you some more information as to what's going wrong it to turn on Debug logging (Tools>FME Options>Translation>check the Log Debug box). You can then try re-adding the Odata reader and clicking the feed list button and see if there is any other information.

Thanks for the help Matt, I appreciate you looking into this. Is it possible to escalate this question? I Have tried several combinations and can get the feed to work with HTTP caller. Is it possibly a bug with this reader?

 

 

---

I think I got it working Matt.

 

Authentication must be set to basic which had. I set it up exactly like my httpreader. Also, I forced Feed List to use vehicle_master_by_user_org. it failed on creation with this setup several times and then decided to work. not sure why but it is reading and returning the data I am expecting.

 

 

---

Hi @fizquierdo - Here's the documentation on our Odata reader: http://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/odata/odata_reader.htm?

 

Please read the requirements carefully. In addition you will find an example Odata link which you can test out to make sure that FME is working correctly on your machine. If that Link isn't working then it might be specific to your machine.

 

 

I'm not overly familiar with the OData side of things, but the "$format=json" part isn't needed here. I was expecting the "vehicle_master_by_user_org" to be in the feed list but it's seems like it's not quite working as I would expect. 

From our documentation we say that 

The dataset can be one of the following: an OData service, represented by a service root URI, or an OData feed, represented by a service root URI plus a specific resource path.

Something which might give you some more information as to what's going wrong it to turn on Debug logging (Tools>FME Options>Translation>check the Log Debug box). You can then try re-adding the Odata reader and clicking the feed list button and see if there is any other information.

I think I got it working Matt.

 

Authentication must be set to basic which had. I set it up exactly like my httpreader. Also, I forced Feed List to use vehicle_master_by_user_org. it failed on creation with this setup several times and then decided to work. :) not sure why but it is reading and returning the data I am expecting.

 

 

---

I think I got it working Matt.

 

Authentication must be set to basic which had. I set it up exactly like my httpreader. Also, I forced Feed List to use vehicle_master_by_user_org. it failed on creation with this setup several times and then decided to work. not sure why but it is reading and returning the data I am expecting.

 

 

Woo! Great to hear, sorry that it was so confusing!! I'm doing a little dance of joy in my office reading this. Best of luck with getting the data where it needs to go!

 

---