odata

[mceldon]

Hi I'm consuming data via a single OData web service which is driving a number of (3) queries where grouping or specific filitering is required e.g.;

Query 1 = "GetAllProducts"

[Duplicate Q1] Query 2 = "ProductsGroupedByCreatedDate"

[Duplicate Q1] Query 3 = "ProductsGroupedByPriority"

= 3 x Calls to Web service

This all works fine but the client seems to be downloading a dataset for each query, when a single refresh would suffice, given that all of the other queries are sub sets of the the single "GetAllFoos" query. is this by design or is there a more efficient way of structuring individaul queries ?

Thanks,

MM

[mceldon · Accepted solution]

I think I just found my own answer; I believe that is what the 'Right Click a Query > Reference' option is for.

Thanks

[saunders]

Hey, just wanted to say thanks for posting this, I'm facing the same issue.  My solution has to make simultaneous multiple calls to the same table via odata because I'm breaking up a large table into several smaller tables.  Data refresh is currently failing due to load on the server due to these simultaneous calls.  I had assumed that we would need to restructure the odata or switch to ETL into a data mart but will try this solution first.  Thanks again.