Forum Discussion

gaccardo's avatar
gaccardo
Advocate II
8 years ago

VSTS odata refresh issue

We are reading data from the VSTS odata source.  Because the queries return too much data, we create a table of date values, then use these date values to limit the scope of the query.  Everything w...
Need Help
gaccardo's avatar
gaccardo
Advocate II
8 years ago

One bit of information that I find interesting is that if I change VSTS.Feed([URL]) to VSTS.Contents([URL]), the dataset will refresh

with no issues.  However, the values returned by VSTS.Feed() are binary and much more difficult to transform into useful rows and

columns.

arsaveli's avatar
arsaveli
Helper I
8 years ago

Hi,

Looks like you are trying to view work item snapshots monthly. Have you tried new Analytics views? It has a feature to return history (which is what workitemsnapshot is) at monthly intervals.

  • gaccardo's avatar
    gaccardo
    Advocate II
    8 years ago

    The data sources shown are from the analytics view feature.  We are accessing it via the odata feed using the VSTS.Feed() method to get complete work item histories over a 6 month period.  The reason for multiple queries is because a single query with 6 months of data returns >300K rows.  

     

    As best I can tell, the problem seems to be an issue in the VSTS.Feed() method itself. 

    • A single call to VSTS.Feed() in a query works properly in apps.powerbi.com.
    • Multiple, sequential calls to VSTS.Feed() in a query work
    • Multiple calls to VSTS.Feed() in an each loop cannot be refreshed in apps.powerbi.com.  They fail as shown
      in the original message.
    • Using VSTS.Contents() in an each loop refreshs without issue.  However, this method is deprecated, doesn't return
      all of the data (it provides a continuation token), and also returns a binary object which is harder to process.
    • Using VSTS.AccountContents()--which replaces VSTS.Contents()--fails the same way that VSTS.Feed() does.
    • Using OData.Feed()--which was replaced by VSTS.Feed()--fails the same way that VSTS.Feed() does.  It also
      doesn't return all of the data, but instead returns a continuation token.

    Given the number of options provided to run a query, it would be nice if one of them worked.