Message Error in POWERBI 'https://api.smartsheet.com/2.0/home' (500): Internal Server Error

Matias86BI

Hi everyone,

I use Smartsheet as database for mis PowerBI reportes.

The problem is, when i try load the data with Refresh in PowerBI, appears the following message:

'https://api.smartsheet.com/2.0/home' (500): Internal Server Error

I tried with another sources, and works fine, the problem is only with Smartsheet.

Any ideas?

Beforehand thank you very much for the aswers.

Additional data: this message appears to me in the power Query:

DataSource.Error: Web.Contents no pudo obtener el contenido de 'https://api.smartsheet.com/2.0/home' (500): Internal Server Error.
Detalles:
DataSourceKind=Smartsheet
DataSourcePath=Smartsheet
Url=https://api.smartsheet.com/2.0/home

Matías

amoncaleano

I'm experiencing the same issue, I noticed last week after the Microsoft update

amoncaleano

@Matias86BI any progress on this issue? any fixes you can share?

Matias86BI

Hi everyone,

I fixed the problem

https://community.smartsheet.com/discussion/comment/442366#Comment_442366

Same here, after the Microsoft update, PBI ask you to sign in again… in my case, i failed to attemp to insert the password and finally, the problem of this thread.

The solution? Sign in again through: Options → Datasource configuration —> smartsheet → edit permissions —> edit —> Sign in again (correctly)

Kind regards!

Robert Godkin

I am having the same problem as of the last 2 weeks, but the correction above does not do anything. Anyone have any other ideas?

Joao P

Hi everyone,

Did someone get a solution? I'm facing the same problem, and I tried the solution above, but it didn't work either.

Matias86BI

https://community.smartsheet.com/discussion/comment/467102#Comment_467102

https://community.smartsheet.com/discussion/comment/446324#Comment_446324

Sign in again through: Options → Datasource configuration —> smartsheet → edit permissions —> edit —> Sign in again (correctly)

Stephanie Stefanick

I'm running into this issue as well. Signed in again and that didn't work. Any other thoughts on resolving this?

Georgie

Hi @Stephanie Stefanick,

This issue has been confirmed as a bug and our Support team is actively working on an issue. They have, however, identified a temporary solution - please submit a Support ticket so the team can assist with this. Take a look at my comment on this related thread for more information.

Thanks,

Georgie