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

Not showing up as a custom connector #1

Closed
ruthpozuelo opened this issue Apr 23, 2018 · 14 comments
Closed

Not showing up as a custom connector #1

ruthpozuelo opened this issue Apr 23, 2018 · 14 comments
Assignees

Comments

@ruthpozuelo
Copy link

Hi Miguel,
I tried today your .mez file ( thinking to do a video on it), but it didnt work for me. Is it still working for you?
Your work is awesome by the way!
/Ruth

@migueesc123
Copy link
Owner

Hey Ruth!

Thanks for the kind words! Did you check if your Azure App is running? the .mez does require some configuration. The step by step configuration can be found here

I believe the *.mez that I uploaded either has my own App (which can only authenticate myself) or it has a fictional app ID.

@ruthpozuelo
Copy link
Author

ruthpozuelo commented Apr 23, 2018 via email

@migueesc123
Copy link
Owner

oh wait! Did you mean showing up as a custom connector in your Power BI Desktop? or in the Data Gateway?
If it is not showing up in your Power BI Desktop then perhaps the Custom Connectors are not enabled in there. If they are enabled and you don't see it, then perhaps you might need to check your Folder to see if its written in the right way that the Power BI Desktop is expecting.

To check your app you can go directly to https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps

and it should give you a list of all of your RegisteredApps.

@ruthpozuelo
Copy link
Author

ruthpozuelo commented Apr 23, 2018 via email

@migueesc123
Copy link
Owner

it should show up. What if you just place the .mez in your folder after downloading it? maybe zipping the files back is what's causing issues? Here's a video that showcases how to modify the contents of the mez file and then putting it all back.

It was recorded using another .mez file, but it's the same process for all.

@ruthpozuelo
Copy link
Author

ruthpozuelo commented Apr 23, 2018 via email

@migueesc123
Copy link
Owner

the mez should load even if the AppId is incorrect. The only issue with an incorrect AppID is that the whole authentication process will fail, but it'll show you the functions of that custom connector and the icons and all that. Would you mind trying with another one of my connectors? the WooCommerce one has a test environment free of charge that you can use.

@ruthpozuelo
Copy link
Author

ruthpozuelo commented Apr 23, 2018 via email

@ruthpozuelo
Copy link
Author

ruthpozuelo commented Apr 24, 2018 via email

@migueesc123
Copy link
Owner

It does. All of the connectors that I've published on Github have been tested in multiple computers (3 of mine and 1 Azure VM at least for each), so I can guarantee that they'll work. It's pretty odd that it doesn't work for you - have you tried installing it in a different computer? or perhaps just enabling just that connector to see if it gets picked up? The connector might have some shared variables that conflict with one of the custom connectors that you also have in the folder and that might be causing one of them to just not load (that's my best guess at this point)

@migueesc123
Copy link
Owner

I just set up a new Azure VM, installed the latest Power BI Desktop and I did find something new. When Power BI Desktop is installed, it created its own folder in the "Documents" folder and within that folder it created its own "Custom Connectors" folder. I went the old way of creating a "Microsoft Power BI Desktop" folder in the "documents" folder but that didn't load any of custom connectors. I had to place all of my custom connectors in the folder that was initially created by Power BI Desktop and in the end it looked like this:
image

@ruthpozuelo
Copy link
Author

ruthpozuelo commented Apr 24, 2018 via email

@jorgehsaavedra
Copy link

Hi rut,

I had the same issue, but I solved doing the following:

  1. Unhide extension file the sistem
  2. Changue extension file from .mez to .zip
  3. Double click the file inside the unzipped folder with the name AppID.txt
  4. Once open the winzip, Open the file with the name AppID.txt and replace the value found inside with the Client ID.
  5. Save and upgrade the unzipp folder.
  6. Changue extension file from zip to .mez
  7. Open Power BI Desktop and, in the Get Data window, search for the new Custom Connector.

@ruthpozuelo
Copy link
Author

ruthpozuelo commented Apr 29, 2018 via email

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

No branches or pull requests

3 participants