In a office 365-hosted sharepoint subsite, called bi, we store an excel file in the documents folder.
The pwdoc resource is simply an excel file, uploaded.
The sharepoint infrastructure has a nice feature – that any “table” within an uploaded excel file becomes an odata feed:
Our first table, with columns mlsid and payment, is known as PW and becomes the “PW” feed
The second table is known as NRDS:
we can use Excel’s power query tool chain to visit the
Comments on the RESO spec, at http://members.reso.org/display/API/2.3.2+URI+Stem, has an example
In the example, an optional convention for addressing service documents by URI is, for our domain name, https://netmagic.sharepoint.com/RESO/OData/ .
In fiddler, the client’s proxy, we add a rule:
urlreplace /RESO/OData/ /bi/_vti_bin/ExcelRest.aspx/Shared%20Documents/pwdoc.xlsx/OData
note how the address bar no longer matches with the xml base.
Another solution is to do a formal redirect, so that the atom document has a base that aligns with the browser:
using a redirect (in fiddler, rather than a true load balancer setup)