If you are using unsupported data types, you may want to consider creating views that do not contain these fields, and exposing those. A complete list of supported data types can be found here. In the above case, the DistrictMaps table contained a geography field, which is unsupported.
The table will appear as greyed out when the list of tables to use for OData is being configured. If your table or view uses any field that is an unsupported data source, the entire table will be unavailable to use in an OData feed. The Data Management Gateway, and therefore the Power BI service don’t support all of the data types supported by SQL Server, or Oracle. This means that the OData feed only works on the intranet – it can’t be shared publicly. The reason that this is important is that because the actual data connection does not go through the Power BI service, the client machine needs to be able to communicate directly with the machine hosting the Data Management Gateway. When this feed is used, a connection is made directly from the OData client to the Power BI service, which then redirects communication to the Data Management Gateway. When a data source is registered, an “enable OData feed” option is made available which when checked, creates an OData feed URL. The OData feed feature works through the Data Management Gateway, which is normally used to keep data models stored in the cloud updated regularly with new on-premises data. There are however a few limitations to what you are able to do that you should be aware of before you head down this path.
Complete instructions on setting this up can be found here.
This is a very simple and quick way to get your existing data available through OData, as it involves a simple check box selection.
One of the features available in Power BI is the ability to take any defined data source and expose it as an OData feed.
0 kommentar(er)
