Power BI - Unable to Connect

[gokermu (Mucahit Bilal GOKER)]

Hi guys,

Getting this error while trying to connect to a Public stream. Link to that is below:

Speckle Stream

[AlanRynne]

Hey there @gokermu, I’m doing some powerBI improvements today so I’ll look into it in an hour or so!

Thanks for reporting this!

[AlanRynne]

Just as a follow up for future reference. This error will be solved in the next version of the connector (0.0.6) if my memory recalls correctly.

[gokermu (Mucahit Bilal GOKER)]

As a beginner in Power BI , above is a simple chart I created using Speckle.

[colin.magner]

I’ve installed version 0.0.7 of the Power BI connector, and I get this with my own streams, but can connect to a stream created by someone else.

I’ve tried creating two public streams, each from a separate (and very simple) Revit model. The streams looks OK in the browser. If I try to connect to them in Power BI I get “you are not authorized”.

Someone else in my organisation can connect to my stream using the same URL, and I can connect to their stream using their URL, I just can’t connect to my own streams!

An example stream that I’m unable to connect to is: Stream | Speckle (arup.com)

[AlanRynne]

Hi @colin.magner!

Welcome to the community! Feel free to Introduce yourself 🙆 if you haven’t already!

I tried reproducing the issue in my computer but everything seems to be working fine. I can:

• Fetch the example stream you provided with no issues (thx for sharing it)
• Fetch my own created streams anonymously and using a token
• Fetch streams that are public anonymously and using a token

It occurs to me that it may have something to do with your credential settings in PowerBI

Then clear any existing entries referring to Speckle from the window that will pop up.

This will force PowerBI to re-request your credential strategy the next time you fetch data. I suggest you try both:

• Accessing the data without providing a token (the Public Stream option).
• Accessing the data by providing a token (the Private Stream option).

Since auth tokens do expire (@dimitrie please correct me on this one?), make sure you create a new token when you try this.

Let us know how it goes!

[teocomi (Matteo Cominetti)]

Hey @colin.magner , since you’re on the Arup server it might be worth trying with ours as well to at least remove that variable: https://speckle.xyz/

[colin.magner]

Thanks for the suggestions Alan, Tecocomi.

Working on the Arup v2 server, after clearing the source settings:

• The public option still gives me “you are not authorised”. I tried applying at all three levels (I assume normally you’d do this at the specific stream level).
• The private option worked after generating a new personal token (set to “Streams:read”).

I created a new public stream with the same data on your server ( Stream | Speckle), and I can connect to this OK.

This is all very strange, as another colleague is able to connect to my stream with Power BI when it’s set to public, it’s just that I can’t! But I can connect to one of their public streams on our server.

[AlanRynne]

Hey @colin.magner, is the stream you provided still public? I can’t seem to access it anymore.

Not pointing any fingers here, but it seems like the problem may be on the Arup server?

Just for clarification, you can set your credentials at the server level instead of “per-stream” and any streams you fetch will use the same credentials. Given your server is kind of private… I would just default to fetching everything with your token (public or private). I find this handier than setting the credentials on a “per-stream” basis.

Fetching any stream with a token will also provide the server with information on who is receiving the data. If you fetch it without a token, your commit’s won’t be tagged as received.

So I’d recommend, in general, using “Private Stream” option with your token and set it to the server url level.

Anyway, do let me know if the stream remains set to public, since i’m now getting “Your are not authorised” messages too! There may be some lurking bug that we need to look into!

[colin.magner]

Thanks Alan. The stream is still private, so it’s not a problem at your end!

Takeaways from this:

• I’d prefer to use private streams rather than public, so using private and an access key by default sounds good.
• I’ll find out who our server admin is and let them know about this anyhow, in case there’s an underlying issue that’s causing this behavior
• You’ve also shown me how to reset the credentials for a Power BI source, so thanks for that!

Thanks again.

[Joe_Landers]

Hi,

Resurrecting an old thread, as I’ve found new issues with connector version 0.0.7 and 0.0.6.

I get the following errors for both private and public streams (all on Arup server):

and if I use a specific commit I get this error:

This all works fine on version 0.0.5.

[teocomi (Matteo Cominetti)]

Hi @Joe_Landers , before we dig into this, can you please tell us if you have the same issue on XYZ? Unfortunately, we cannot debug things on servers other than ours.

Thanks!

[colin.magner]

I just had a call with our internal Speckle team to discuss this, and prior to the meeting I got my streams loaded up and tested connecting them into Power BI… and they worked.

As far as we are all aware nothing has changed. We haven’t changed any Speckle server configuration (that those of us on the call are aware of), and I haven’t changed the Power BI connector (which is still 0.0.7) but I can now connect to both my public and private test streams.

[Joe_Landers]

Hi, managed to find some free time this evening to test this.

Yes, can confirm the same data on XYZ works and streams into PBI 0.0.5 and 0.0.7 connector (didn’t try 0.0.6).

But now 0.0.5 has stopped work on the Arup server. Very frustrating. @colin.magner did you have any more updates? I will make contact with our internal Speckle team to inquire.

[colin.magner]

Hi @Joe_Landers, I just tried and it’s still working. I honestly have no idea why it started working, and was unable to identify anything that changed in terms of software/configuration etc.

I’ve using the v0.0.7 connector, Power BI desktop 2.100.1182.0 64-bit (December 2021), and our v2 Speckle server.

[JdB (Jeroen de Bruijn)]

After Joe and I cleared our Speckle related data source settings, the PowerBI connector is able to receive again! I had the same issues as Joe. We are both using the James Bond (0.0.7) version.

Would it be an option to have the connector handle this automatically? Maybe first try to fetch the stream using any existing PowerBI data source settings and in a second attempt ignore any PowerBI data source settings?
(or maybe just a message in the “Unable to connect” pop up that the user could try to clear their data source settings via File > Options > Data source settings)

[oliwer]

Hi all! I’m trying to deal with with connecting data from speckle.xyz server to PowerBi using v0.0.7 connector. I think I’ve used all combinations listed above - the message remains - for commit and stream

Each time I remove Data source settings, but still with no luck

However, I haven’t tested the private link, because I don’t know from where should I get the activation token. Where shall I look for it?

[AlanRynne]

Hey @oliwer,

you can create new tokens from your profile page at the Speckle server (Speckle in this case). You can find out more about it here: Personal Access Tokens | Speckle Docs

We’ve recently changed the UI so the screenshots may be a little outdated, but its basically the same process. This is the section you’re looking for:

[oliwer]

It helped! Private stream does the trick. Thanks a million!

[BaudouinNP (de Montarnal)]

Hey all,
I am waking up this thread, cause this happened to me today, but not with every stream…

Here is the stream:

Speckle Stream

It works when I give the link of a commit… but not of the stream itself… Of course, I want my data to be updated every time a new commit is uploaded…

(Just as a temporary solution, how to switch the commit address to another one? To make a “manual” update of the data ?)

Thanks again for your great work Speckle Team !!!