https://www.infopathdev.com:443/blogs/hilary/archive/2011/12/28/sharepoint-odata-and-infopath.aspxIf you are using SharePoint and InfoPath 2010, you may already have SharePoint&#39;s OData services at your disposal. And while with 2010 we now have query fields for list and library data connections, you can go far beyond basic equivalency in your queriesenCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/blogs/hilary/archive/2011/12/28/sharepoint-odata-and-infopath.aspx#76486Thu, 15 Mar 2012 00:41:20 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:76486Hilary Stoupa<p>Sorry you found it misleading! That certainly wasn't the intent.</p> <img src="https://www.infopathdev.com:443/aggbug.aspx?PostID=76486" width="1" height="1">https://www.infopathdev.com:443/blogs/hilary/archive/2011/12/28/sharepoint-odata-and-infopath.aspx#75860Wed, 29 Feb 2012 17:54:20 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:75860Amir Tei<p>Hillary, Thank you for putting together and sharing the video. It is helpful asset.</p> <p>However, I found it misleading for the case that the REST Web Service data connection access does not work browser-enabled InfoPath forms published to standard (multi-tenant) Office 365 SharePoint Online sites because of Loopback Checking in enabled by default.</p> <p>I watched the video where you start off by referring to ODATA.org and finish off by publishing the form to a sharepointonline site. However, in between to jump to Tasks list on your local server and describe how to use REST to access filtered list data.</p> <p>Although, you didn't explicitly publish the form containing REST data connection to local Tasks list to sharepointonline, however, it gives the sense to the viewer that it will work as well as REST connection to ODATA.org which isn't the case.</p> <p>Please share your comment on my notes.</p> <p>Thanks,</p> <p>Amir</p> <img src="https://www.infopathdev.com:443/aggbug.aspx?PostID=75860" width="1" height="1">