This is a behavioral change we're trying out for new connections in the June 2018 release. If you go to http://services.odata.org/TripPinRESTierService/ in your browser, you'll notice that the functions are not represented there either. Before the June release, we would try to infer the locations of functions, but the OData protocol does not actually guarantee we can do this if they are not represented in that top-level document. For June, we tried to go with the strictest possible interpretation, but there's definitely still some question on what the best behavior would be. Old connections are unaffected, and you can always revert to the pre-June version of the connector by going to the Advanced Editor and removing the option 'Implementation = "2.0"'.