Pretty self explanatory - would be great to be able to stream a dataset, or grab a specified number of rows. This would also require the ability to query the # of rows, size of dataset etc, column types etc. somewhat related to this feature request: https://support.powerbi.com/forums/265200-power-bi/suggestions/7059563-create-a-part-download-of-datasets
31 Comments
- This is required as we want to pull data from a custom registered client application.
- '+1
- when trying to GET Tables of DataSet which created in power API Desktop. The API return 404 with error: "Dataset {dataset_id} is not Push API dataset." I have posted this issue which marked as "Delivered" http://community.powerbi.com/t5/Issues/Can-t-reach-Tables-Columns-Relationships-of-a-DataSet/idc-p/190127#M8804
- We really need this. The company is moving to some cloud products where the only way to get data is via REST APIS. It is increasing my dependency on Development.
- Gareta summed up the need for this perfectly below. We are doing a lot of transformation of data in Power BI which is then needed for other applications without having to duplicate these transformations again.
- Not sure why you would even build the ability to write rows to a dataset table but not build the ability to read rows from it!?!? Strange. Also there is no ability to get a user's "Favorites" or get access to a users recent reports or get access to the filters that a user has applied to a particular report. I wanted to access a users "Favorite" reports so that I can allow them to click them from our custom app. The data is not available so I thought I would allow users to build their own favorites from my app by sticking their selected values in a dataset table (do not want database attached to this app) and the use that for these records. Not available. It seems like every time I try to build something out using the APIs, I always run into some road block. API is to young for production I am afraid.
- What happened to my earlier comments?! I had said something along the lines of, since we use pbi to elegantly query multiple sources and combine to produce new tables, it is crazy to repeat these same transformations in other tools against the same sources to find the same results. This will lead enterprise users to skip powerbi and instead only use those other tools, perhaps using powerbi later as a viewer but we'll definitely avoiding 'creating' any irretrievable value in powerbi. API access to read datasets is a no brainer and enables our data to become programmatically accessible and actionable rather than just shiny visuals. If necessary limit the API in terms of rows or frequency of queries. Our data wants to be free! Our actions want to be automatic! Our humans don't want to be obligated to micromanage all actions that can be influenced by the data we've fed powerbi. Similarly we would like to read dashboard tiles/kpi values. If that were available we could ensure each actionable scenario was captured on a pinned kpi for 'alerts's or complex flow actions.
