POST /v1.0/myorg/groups/{groupId}/imports
Post Import In Group
Creates new content on the specified workspace from .pbix, .json, Excel, Rdl, or file path in OneDrive for Business.
Required scope: Dataset.ReadWrite.All
To set the permissions scope, see Register an app.
Notes
- To import a file, request Headers should include Content-Type: multipart/form-data with the file encoded as form data in the request body
- To import from OneDrive for Business, request Headers should include Content-Type: application/json with ImportInfo in the request body.
- To import large .pbix files between 1 GB and 10 GB see Create Temporary Upload Location In Group, supported only for workspaces on premium capacity.
- To create a dataflow from a model.json, specify the parameter datasetDisplayName as described below.
Servers
- https://api.powerbi.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
groupId |
String | Yes |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
datasetDisplayName |
String | No |
string The display name of the dataset should include file extension. Not supported when importing from OneDrive for Business. For importing or creating dataflows, this parameter should be hardcoded to model.json. |
skipReport |
String | No |
boolean (Optional) Determines whether to skip report import, if specified value must be 'true'. Only supported for PBIX files. |
nameConflict |
String | No |
ImportConflictHandlerMode (Optional) Determines what to do if a dataset with the same name already exists. Default value is 'Ignore'.Only Abort and Overwrite are supported with Rdl files.Only Abort and GenerateUniqueName are supported with dataflow model.json files. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.