Forum Discussion

palamanb_Risk's avatar
palamanb_Risk
Helper I
4 months ago
Solved

Workspace, semantic model, report, users and dataset lifecycle management

I am a Power BI Admin within my organization (not a Global Tenant Admin). My primary responsibility is as a Capacity Admin, and I manage several workspaces, datasets, and capacities. We have recent...
Need Help
  • Lodha_Jaydeep's avatar
    Lodha_Jaydeep
    4 months ago

    palamanb_Risk appriciated to help you. Here are the outlined steps to do the same.

     

    1) Copy the attached .MEZ file on C:\Users\MagnusMinds\Documents\Power BI Desktop\Custom Connectors folder on your machine.

    2) Open power bi desktop and do this setting and restart the power bi. (This is a setting to use the custom connectors)

    3) Open power bi and clcik get data -> search for custom or any relevent text

     

    4) After click it ask you to allow third party connectors.

    5) It list the available API endpoint in a form of function you can use whatever you need

     

    6) Load data and build the dahboard/report as your own. Then below are the steps for the gateway setup and refresh same report on the service on schdule basis.

     

    Add the custom connector folder here in the connectors section.

    create the gateway on the service using this connector use it in the semantic model as well.

    I hope this helps! If this resolves your issue, please mark this as the Accepted Solution to help others.

     

    Note: Try to do in the hierarchy like (workspace\group -> Dataset -> Report etc....) As the respective function need the parent as a parameter.

Lodha_Jaydeep's avatar
Lodha_Jaydeep
Solution Sage
4 months ago

Hi palamanb_Risk,

 

Thank you for your kind words. It is unusual that the recommended method isn't working in your environment.

To help me troubleshoot further, could you provide a breakdown or screenshots / screen recording of the specific steps you are taking when using the connector?

 

It is great to hear that you've successfully retrieved the data via PowerShell. There are several robust ways to integrate that data into Power BI; here are the most effective methods:

  • Option 1: SQL Server Integration (Recommended): Use your PowerShell scripts to ingest the data into SQL Server tables. This is the most scalable approach, as it allows for seamless scheduled refreshes in the Power BI Service via an On-Premises Data Gateway.

  • Option 2: Flat File Staging: Export the data to a shared location, such as Azure Blob Storage or SharePoint etc..., as a CSV file and connect Power BI to that source.

I recommend the first approach for better performance and easier refresh management. Please let me know if you have any questions!

palamanb_Risk's avatar
palamanb_Risk
Helper I
4 months ago

 Let me share the steps that I have followed. 

Will get back to you on Monday.

Thanks

  • v-anbandari's avatar
    v-anbandari
    Community Support
    4 months ago

    Hi palamanb_Risk ,

    Could you please confirm  if the suggested approach helped resolve your issue. Your confirmation would also help others facing similar scenarios.

    Thank you.