PowerBI-Post-Import-In-Group API cuts off the name when creating the dataset

[rayishome]

Using the following API call and uploading a PBIX file the dataset the service creates removes some of the string values.  

url https://api.powerbi.com/v1.0/myorg/groups/[worksapce]/imports?datasetDisplayName=Test%209%2F5%2F2022.2.3.4.5.5.6.6.%23..P.pbix&nameConflict=Abort&skipReport=true

Results in the following status:

res {
'@odata.context': 'http://wabi-us-east2-redirect.analysis.windows.net/v1.0/myorg/groups/[workspace]/$metadata#imports/$...',
id: 'id value removed',
importState: 'Succeeded',
createdDateTime: '2022-06-17T19:53:46.733Z',
updatedDateTime: '2022-06-17T19:53:46.733Z',
name: 'Test 9/5/2022.2.3.4.5.5.6.6.#..P.pbix',
connectionType: 'import',
source: 'Upload',
datasets: [
{
id: 'id removed',
name: '2022.2.3.4.5.5.6.6.#..P',
webUrl: 'https://app.powerbi.com/groups/[workspace]/datasets/[new dataset id removed]',
targetStorageMode: 'Unknown',
upstreamDatasets: [],
users: []
}
],
reports: [],
dataflows: []
}

[lbendlin]

Forward slashes / are reserved characters and cannot be used in file names.

[rayishome]

Thanks for the reply.  I'm not sure that's the issue, but it would make sense if the API developer built that validation into the process.  The service allows the "/" when a dataset is renamed which would make this api validation inconsistant with user experience.  

[v-yiruan-msft]

Hi @rayishome ,

Could you please try to rename the pbix file without the special characters "/" and recall that REST API Imports - Post Import In Group? Later check if it can create the content in the specific workspace successfully...

Best Regards

[rayishome]

I'm not sure I fully understand the steps:  

1) Rename the dataset (using the UI) that currently contains the special "/" (renamed using the UI) removing the "/" then use the Post to Group api to post a new file with the "/' included?

2) or, use the API to post the same file without the "/" to see if it posts correctly?

#1, I'm not sure what we will occomplish, the new post will work since it doesn't include the "/"

#2, works!  

The issue I'm having is our users expect the use of the "/" using the API via our app since the Service's UI supports the "/".  

[lbendlin]

"since the Service's UI supports the "/"

That is a bug in the service. It should not accept that character. You can raise an issue at https://issues.powerbi.com . If you have a Pro license you can consider raising a Pro ticket at https://powerbi.microsoft.com/en-us/support/pro/