I am connecting a JIRA to Power BI so I can make my own reports.
To do this I use the JIRA web API. But the problem is that I am limited to a max row of 1000.
How can I do to retreive all rows into power BI. Should I do some kind of cycle with parameters? Should concatenate n queries in power query, but when comes new rows, how to deal with them.
Any one any idea?
thx
This is not a trivial task. Most REST APIs use pagination and limit the number of results per page. I would advise you to follow this article on how to do pagination in Power Query written by Mark Tiedemann. I successfully applied the pattern he describes to retrieve tens of thousands of Jira issues in Power BI.
Your idea of concatenation is almost correct. But instead of creating multiple queries (difficult to maintain), a single query is sufficient:
In this query, you retrieve the first page of results which contains the total number of results which you use to calculate the total number of pages. For each page, retrieve all issues (offset and limit). Finally, concatenate all pages into a single list or table.
I installed the Jira Connect application on Power BI. Just enter the URL for your Jira instance, and it will automatically use the Jira REST API.
Example: https://my.jira.app:2990 (note: no path to the REST API).
If Power BI doesn't ask for credentials (happens often), then change your credentials in the dataset web credentials (select Basic authentication).
Related
I am trying to retrieve all users from AD using Microsoft Graph APIs.
https://graph.microsoft.com/v1.0/users
But this is returning only some top n rows from the whole users list.
I guess its using some pagination there. But didn't find how to specify page number or those details as a parameter within the query.
https://learn.microsoft.com/en-us/graph/api/user-list?view=graph-rest-1.0&tabs=http
Ms Graph cant show all users in the same page as it may cause threshold issues if the user count is too high.
you need to use paging to achieve this i.e., to get all the users you can achieve it with the help of #odata.nextLink please refer Ms Document for more details.
I’m trying to forecast the value of various keywords using the google Adwords API, using the traffic estimator service. So far, the clicks, costs per click, and other metrics returned through the API don’t come anywhere close to those retrieved through the Keyword Planner console. There are several adjustable forecast parameters in the console such as language, location, and search network, and I tried to match these parameters in the API.
I'm wondering if there is some other element that needs to be adjusted that I'm missing. For example, the console gives you the option to "select an ad group" for the forecast, and I'm not sure how this would be applied within the API.
If you're interested in obtaining the results that the KW planner provides in the Ads web UI, you'd need to use the TargetingIdeaService instead of the TrafficEstimatorService.
There's also a reference document with some pointers explaining how to map the web settings with the TargetingIdeaSelector values available in the API.
Note that in my experience, you'll sometimes still find discrepancies between what's shown in the web UI and the stats provided by the API. This is also a recurring theme in the Ads API forum (just search for "TargetingIdeaService Difference" or similar).
I'm implementing a sorting algorithm and I want to query the Insights for Twitter API in order to find if a topic is trendy in comparison to another topic.
As far as I've investigated, there is a Count API Operation which will return the number of Tweets based on a given query. Therefore I could query how many Tweets have the particular "keyword" in their body and then compare it to other different keywords to establish an order.
Is there is a more direct query to know if a keyword is trendy?
Your approach using the /api/v1/messages/count endpoint looks like the right one when working with the Insights for Twitter API.
I guess you could also use the posted query parameter to build trending charts over time for your different keywords.
When querying the YouTube Analytics API for demographics for a channel for a 1 day range (metric:viewerPercentage, dimensions:ageGroup,gender) in some cases no rows are returned. The api IS returning views for that day however.
2 reasons for this come to mind:
1. The data is not available yet because it is still being processed.
2. There is no known demographics for that (i.e. the gender and age of the user are not known)?
Am I safe to assume it's not (1) in this case because a query for views did return results? If I can't assume on then is it true that there's no difference in the response/results between "not processed" and "processed but all users are of unknown demographics?"
In other words if, when (2) were the case, the API would return a row with all zero's 0 for each demographic, that would enable us to interpret things correctly (but I'm pretty sure that's not how API queries with a dimension work).
Thanks for any guidance!
I can't provide any hard-and-fast guidance about the YouTube Analytics data processing pipeline, i.e. whether the demographic data will always be available at exactly the same time that the view count data is available in a report.
To get a more authoritative answer about this sort of specific question, I'd recommend going to the YouTube Analytics web interface (http://youtube.com/analytics) and try running an identical report from there. The web interface normally gives you some warning if you're requesting a report that relies on data that isn't yet available.
I'm using YQL to retrieve site specific results (I don't need Google results for just my own site but for a variety of sites.
However, I'm getting inconsistent results. Using the YQL console for my query:
Executing a Test for the same query multiple times, sometimes returns result but quite often gives no result without producing an error.
When there are results, the number of results is often significantly less from manually executing a Google query on google.com
An example query that shows this behaviour is
select * from google.search where q = 'site:www.freelas.net'
Any suggestions on this?
Kind regards,
Marc
The older Google Search API that the google.search YQL table uses has been deprecated by Google. It's still running, but I think there is a 100 query/day limit. When you see no results in YQL console, it likely means that it's being rate-limited.
As an alternative you might try using the newer Google Custom Search API. Note that it's only free up to 100 queries/day, but they offer a paid plan above that.