Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Power BI Clockify Connector: Unable to Refresh Data in Power BI Service #17

Closed
safer-lgtm opened this issue Jun 26, 2024 · 6 comments

Comments

@safer-lgtm
Copy link

I have successfully used the Power BI Clockify connector to load data into Power BI Desktop, and it refreshes without any issues locally. However, I am encountering a problem when trying to refresh the data in Power BI Service.

Error Details

When attempting to refresh the data in Power BI Service, I receive the following error:

Failed to update data source credentials: Web.Contents failed to get contents from 'https://reports.api.clockify.me/v1' (404): Not Found

repprt api false without detail

I have ensured that the connector is located where the gateway can access it. Despite this, the error persists, indicating that the data source is inaccessible, a connection timeout occurred, or the data source credentials are invalid.

grafik
grafik

Additionally, I've tried to bypass the test connection for reports.api.clockify.me, but this only leads to another error stating that the data cannot be validated because it was done via a gateway. However, the primary source api.clockify.me can be updated without any issues from both the server and desktop.
grafik

Request for Support

I am seeking assistance to resolve this issue. Is there something I am missing in the configuration for the Power BI Service? Any guidance or troubleshooting steps would be greatly appreciated.

Thank you for your support!

@TinaCastillo09
Copy link

Hi,

Did you manage to work this one out? I am getting the same error.

@safer-lgtm
Copy link
Author

Try using the absolute path instead of the relative path and skip connection for the data source reports.api.clockify.me/v1 in PBI Service.

@OscarValerock
Copy link
Owner

Guys, @TinaCastillo09 @safer-lgtm , I feel you are mixing connection possibilities. The repository gives two options: through a custom connector and with a PBIT (Template) file; as you are referring to the error coming from "https://reports.api.clockify.me/v1" I believe you are using the PBIT template file and not the custom MEZ connector.

  • Custom connector (MEZ): Requires gateway, when setting the gateway connection skip the connection test.
  • PBIT: Does not require a gateway, but when configuring data sources in the desktop and the service, set both connections to "organizational" and skip the connection test in the service

I only tested both, and they work fine when refreshing from the service:

image

@OscarValerock
Copy link
Owner

Hi all, @safer-lgtm @TinaCastillo09 Please let me know if this video clarifies the issue.

[

ClockifyPowerBIConnector.mp4

](url)

@safer-lgtm
Copy link
Author

safer-lgtm commented Jul 6, 2024

Thank you @OscarValerock, for your support and especially the video.

I can now refresh the dataset in Power BI Service in 1-2 minutes! Amazing! In my own solution, it used to take 5-10 minutes to refresh the dataset. By using the absolute path and skipping the connection test, I noticed that the privacy levels in Power BI Service are different from those in Power BI Desktop, which were set up to organizational. I'm using PBIT (Template) file.

I created a small report considering Billable Hours, but after the refresh, although it was set to TRUE in Power BI Desktop, I get -1 and 0 instead after the refresh in Power BI Service. Any idea why this might be happening?

grafik

Thank you again for your feedback; I really appreciate it.

@OscarValerock
Copy link
Owner

@safer-lgtm, glad it worked. I do not know what causes your issue with the billable "TRUE/FALSE" state but I think it is beyond the scope of this issue. Feel free to open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants