Ad-hoc interface or query language for programmatically extracting data
- 4 years ago
I thought I responded to your question earlier about DAX. It seems like my message didn't go through. The short answer is no; nothing in the REST API allows you to pull data in an ad-hoc fashion. It is merely a replica of client API with the client.
For the long answer, you can use FDX API methods to extract data in an ad-hoc way. Write those in a dashboard data set rule and pull it using the DataProvider methods. There is one to run method queries, and users can use that to run the Dataset rules, which will give you a DataSet, and there will be only one table (depending on how you wrote the rule). You can use this now for the downstream.
FDX is discussed in detail in our book (shameless plug)
- 3 years ago
ckattookaran I want to circle back and thank you again for your pointer to "FDX". Those API methods are really fast and flexible, but they aren't highly exposed in the docs. (They should be)
Another forums user also helped me connect the dots (to DataSet BR's, Dashboard Data Adapters, etc). See:
https://community.onestreamsoftware.com/t5/Reporting/Is-there-a-REST-API-for-quickviews/td-p/4652
Once you have a cubeview defined, you can access it via REST using the "GetAdoDataSetForAdapter" endpoint. There are a few unintuitive hoops you need to jump thru to get to your cubeview.- REST calls Dataset Adapter
- Dataset Adapter calls Dataset BR
- Dataset BR calls FDX Execute (BRApi.Import.Data.FdxExecute...)
- FDX Execute runs your cubeview
... see that link above for more explanation.