topic Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API in Developer

Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

Amruta2001 — Thu, 01 Jan 2026 05:14:19 GMT

Hi everyone,

I’m facing some unexpected behavior with report name assignment when uploading a report to power bi service using the REST API PostImportWithFileAsyncInGroup endpoint. I’d like to understand whether this is expected behavior, a limitation, or a bug.

Scenario

When I upload a report using the REST API and assign a name to the report, the name gets modified automatically in certain cases.

Issue 1: Report name with double quotes

If I assign a report name that contains double quotes, for example: "Sales Report"
After the upload, the report name is changed to “No File Model” instead of keeping the original name.
This happens even though the API call itself succeeds.

Issue 2: Report name with date format

If I assign a name like: 23/12/2025
After the upload, the report name is automatically converted to: 2025.

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

lbendlin — Thu, 01 Jan 2026 16:04:02 GMT

In both cases you will likely have to escape those special characters. You can also experiment with explicitly setting the DisplayName value

Imports - Post Import In Group - REST API (Power BI Power BI REST APIs) | Microsoft Learn

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

AshokKunwar — Thu, 01 Jan 2026 16:40:33 GMT

Re: Report Name Conversion Issues (PostImportFile REST API) – Explanation and Workaround

Hello! These issues are likely caused by how the PostImport endpoint handles character encoding and "auto-typing" during the initial file upload process.

Issue 1: Double Quotes and "No File Model"

The "No File Model" error is a generic fallback name the Service uses when the metadata portion of the multipart request is corrupted or fails validation. When you include unescaped double quotes in the displayName, it often breaks the JSON boundary or is rejected by the API's security sanitization layer to prevent injection.

Issue 2: Date Formats (23/12/2025) converting to 2025

The Import API's parsing engine sometimes attempts to interpret strings that look like mathematical expressions. In some legacy versions of the import logic, a string with forward slashes is treated as a division operation, or it defaults to the last numerical segment if it fails to validate as a standard string.

The Recommended "Pro" Workaround

To avoid these limitations, the most robust architecture used by developers is the Two-Step Deployment Pattern:

Step 1 (Upload): Import the file using a "Safe Name" (alphanumeric only, no special characters or slashes). This ensures the file is accepted and the model is created without metadata corruption.
Step 2 (Rename): Immediately follow up with the Reports - Update Report In Group API.

The Update Report API is designed specifically for metadata and is much more resilient. It handles escaped double quotes and date strings correctly because it is a simple JSON PATCH request rather than a complex multipart file upload.

// Example Step 2: PATCH https://api.powerbi.com/v1.0/myorg/groups/{groupId}/reports/{reportId}

{

"name": "23/12/2025 - \"Sales Report\""

}

I hope this helps you stabilize your automation! If this architectural workaround resolves your issue, please mark this as an "Accepted Solution" to help others in the community.

Best regards,

Vishwanath

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

cengizhanarslan — Sun, 04 Jan 2026 16:29:01 GMT

This is expected behavior (unfortunately) and comes from Power BI Service sanitizing the import “name”.

1) Double quotes
The import name is treated like a filename/title and Power BI strips/normalizes invalid characters. A plain " can cause the service to fail the “rename” step internally, and it falls back to a default name (what you’re seeing as “No File Model”).
Fix: don’t send quotes. Replace with safe characters, e.g.:

Sales Report
Sales Report - "Q4" → Sales Report - Q4 or Sales Report - Q4 (quoted)

2) Date-like names (23/12/2025)
/ is also not a safe character for names (it’s a path separator), so the service normalizes it. In some cases it also tries to interpret date-like strings and ends up shortening/transforming the title (your 2025 result).
Fix: use a safe date format in the name, e.g.:

2025-12-23
20251223
23-Dec-2025

Recommended approach
Always generate a “safe” import name before calling the API:

allow letters, numbers, spaces, - _ ( )
remove: " / \ : * ? < > |
use ISO date format YYYY-MM-DD

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

v-csrikanth — Mon, 05 Jan 2026 08:50:43 GMT

Hi @Amruta2001
Thank you @lbendlin @AshokKunwar @cengizhanarslan for your response.

I just wanted to follow up and check whether you have had a chance to verify the solutions mentioned above. Please let me know if you need any additional clarification from our end.

Thanks,
Cheri Srikanth
CST Team

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

v-csrikanth — Thu, 08 Jan 2026 06:22:17 GMT

Hi @Amruta2001

Could you let us know if the suggested solutions have resolved your issue? This information can assist other members facing similar challenges.

Thank you for being part of the Microsoft Fabric Community.

Thanks,
Cheri Srikanth
CST Team

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

AshokKunwar — Wed, 21 Jan 2026 05:44:42 GMT

Hii @Amruta2001

I hope this helps you stabilize your automation! If this architectural workaround resolves your issue, please mark this as an "Accepted Solution" to help others in the community.

topic Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API in Developer

Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

Scenario

Issue 1: Report name with double quotes

Issue 2: Report name with date format

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

​The Recommended "Pro" Workaround

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

Re: Issues with Report Name Conversion When Uploading Reports Using PostImportFile REST API

The Recommended "Pro" Workaround