Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.

Reply
Anonymous
Not applicable

Import to group via API

I am working on a PowerShell function to import .pbix files via the API. The main functionality is taken from the oft referenced sample code here https://github.com/Azure-Samples/powerbi-powershell/blob/master/copyWorkspace.ps1.

 

The code works perfrectly when posting to My Workspace.

The initial Post gets a response with HTTP status code 202 Accepted, and an ID for the import.

When the import is queried via the API, the import details are returned.

In PBI, the new report and dataset are present.

 

But when I run it against a group, the import is posted successfully, but then disappears.

The initial Post gets a response with HTTP status code 202 Accepted, and an ID for the import.

When the import is queried via the API, a 404 Not Found error is returned.

When all imports are queried via the API, there are no new imports listed.

In PBI, the new report and dataset never show up.

 

Any idea why this might not be working?

 

As it works for My Workspace, and the post is accepted for a group, and there are no errors, and that chunk of code is the same as what works for everyone else, I'm thinking it's not my code, but something with PBI. Permissions issue? Group configuration issue? Bug? Any ideas?

 

Thanks,

Tim Curwick

1 ACCEPTED SOLUTION
Anonymous
Not applicable

I narrowed down the bug and found a workaround. (Or rather, I found the workaround, which informed the bug.)

 

The API is generally case insensitive. As a long time PowerShell guy, I default to initial caps in such circumstances, as that's what PowerShell people are used to. Turns out this bug only appears when /groups is not in all lowercase. /Imports can be in whatever case you want. /Groups can be whatever case you want in other API calls.

 

But when creating a new import job, this works:

https://api.powerbi.com/v1.0/myorg/groups/[guid]/ImPoRtS?datasetDisplayName=TestFile.pbix

And this leads to the bug:

https://api.powerbi.com/v1.0/myorg/Groups/[guid]/Imports?datasetDisplayName=TestFile.pbix

 

Thanks,

Tim Curwick.

View solution in original post

1 REPLY 1
Anonymous
Not applicable

I narrowed down the bug and found a workaround. (Or rather, I found the workaround, which informed the bug.)

 

The API is generally case insensitive. As a long time PowerShell guy, I default to initial caps in such circumstances, as that's what PowerShell people are used to. Turns out this bug only appears when /groups is not in all lowercase. /Imports can be in whatever case you want. /Groups can be whatever case you want in other API calls.

 

But when creating a new import job, this works:

https://api.powerbi.com/v1.0/myorg/groups/[guid]/ImPoRtS?datasetDisplayName=TestFile.pbix

And this leads to the bug:

https://api.powerbi.com/v1.0/myorg/Groups/[guid]/Imports?datasetDisplayName=TestFile.pbix

 

Thanks,

Tim Curwick.

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.