API call stopped working

Officially Answered

New post

Niclas Werneborn

March 22, 2019 11:48

Hello,

We have a Power BI dashboard which is configured to pull data from the timetracker API. It has been working perfectly for months, but stopped working in the last week.

Can you please advise what has changed with the API and what we need to do to get it working again?

Below is the query script we use in Power BI reference. Let me know if you need further information for troubleshooting.

Thanks,

Niclas

let
Source = OData.Feed("https://<org>.timehub.7pace.com/api/odata", null, [Query=[#"api-version"="2.1"]]),
#"TimeExport_function (startDate as text, endDate as text, populateTopParentColumns as nullable logical, groupTimeByDateByUser as nullable logical, includeBillable as nullable logical) as table" = Source{[Name="TimeExport",Signature="function (startDate as text, endDate as text, populateTopParentColumns as nullable logical, groupTimeByDateByUser as nullable logical, includeBillable as nullable logical) as table"]}[Data],
#"Invoked FunctionTimeExport_function (startDate as text, endDate as text, populateTopParentColumns as nullable logical, groupTimeByDateByUser as nullable logical, includeBillable as nullable logical) as table1" = #"TimeExport_function (startDate as text, endDate as text, populateTopParentColumns as nullable logical, groupTimeByDateByUser as nullable logical, includeBillable as nullable logical) as table"("2018-08-01", "2030-12-31", null, null, null),
#"Renamed Columns" = Table.RenameColumns(#"Invoked FunctionTimeExport_function (startDate as text, endDate as text, populateTopParentColumns as nullable logical, groupTimeByDateByUser as nullable logical, includeBillable as nullable logical) as table1",{{"TimeTracked", "Actual Hours"}, {"Effort", "Estimated Hours"}})
in
#"Renamed Columns"

Comments

7 comments

7pace tech support

March 22, 2019 12:08
Hi Niclas!

Most probably your OData token has expired.
Could you please generate a new one (Time->Settings->API), apply it to you reporting query and check if it will help?

Kind regards,

Andarth
0

Comment actions Permalink
Niclas Werneborn

March 22, 2019 12:41
Hi Andarth,

Thanks for the quick response!

Actually, the token won't expire until November 2019. Nevertheless, I have tried to create a new one. Unfortunately the application won't let me, however, since I have now started to receive the authorization request message again and when trying to authorize I get the error message "Provided token is not working with current account".

I have tried authorizing using both Chrome and Edge but still receive the same message. Any ideas?
0

Comment actions Permalink
dev

March 22, 2019 13:34
Hello Niclas,

Could you please check this article describing how you could solve your token issue?

https://support.7pace.com/hc/en-us/articles/360024928432-When-authorizing-7pace-Timetracker-why-am-I-seeing-Provided-token-is-not-working-with-current-account-

Alexander
0

Comment actions Permalink
Niclas Werneborn

March 22, 2019 13:50
Hi Alexander,

I have followed the instructions in the link and found that the proper directory is selected.

I am remember having had a similar issue when we first installed timetracker, but then I was able to resolve it by using Edge instead of Chrome. That didn't work this time.
0

Comment actions Permalink
dev

March 22, 2019 13:55
That is weird. Could you please try to sign out on the Me page and sign in back then. Here is link to the Me page

https://aex.dev.azure.com/me

Alexander
0

Comment actions Permalink
Niclas Werneborn

March 22, 2019 13:59
Issue resolved.

The issue was indeed related to the directory selection somehow. I switched to my 2nd directory, and then back again to the correct one, and I was then able to authorize the application.

Using the new token the API connection started working again.

Thanks again for the quick responses, much appreciated!
0

Comment actions Permalink
7pace tech support

March 22, 2019 14:14
Thanks for your update!

Andarth
0

Comment actions Permalink

Please sign in to leave a comment.