Excel displays the COM Add-Ins dialog box that. One thing I wanted to understand is whether this issue of it thinking it was a string data type was due to the DataFeedClient, or something Power Pivot was doing after the data was pulled in. Like some sort of post import processing to determine data types. Using ( conn = new DataFeedConnection(connBuilder.ConnectionString)) So, I spun up some code to use it and see what the schema looked like coming back from the DataFeedClient. So, this was definitely something that the DataFeedClient was using. The problem here is that DataFeedClient doesn’t currently use the schema described by an OData Service. Instead, it sniffs the first n rows of a data set. In our case, the values of the first 31 rows for ProjCost2 and ProjCost3 were blank. If that is the case, DataFeedClient will just default to a string data type. There is a connection string property for DataFeedClient called “Schema Sample Size”. Well, we saw that we didn’t have a value until row 32, so that is a problem. Here is what it looks like when I set Schema Sample Size to 50 using the same test code that I wrote. #Microsoft office 2013 pro powerpivot power query code Within Power Pivot, we want to click on Advanced on the Table Import Wizard, after we fill in our Data Feed URL.įrom there you can adjust the Schema Sample Size to a value that fits your needs. Then just continue with the import.įor the Excel Data Tab, it isn’t as obvious. You want to get the Data Connection Wizard up by doing to the Data Tab, From Other Sources and From OData Data Feed. Select the table that you want and click Next. On the Save Data Connection File and Finish, you want to hit Finish. Then on the Import Data Dialog, you want to click on Properties. This will bring up the Connection Properties. You can then add Schema Sample Size to the connection string.
0 kommentar(er)
