topic Re: Error when publishing report from PBI Report Builder to PBI Cloud in Report Server

Error when publishing report from PBI Report Builder to PBI Cloud

DirkVr — Mon, 13 Jun 2022 14:45:33 GMT

When publishing a very very simple report to PowerBI Cloud, I get the following error message :

Operation returned an invalid status code 'BadRequest'
ErrorCode: NotCreatedByFormattedTableReport
Details: An unknown error was encountered. Please try again.

ResponseId: 021d9f1b-155f-4286-ba22-ac5847316bd7
ActivityId: 30160ac0-2368-4905-bbf5-2809f99f378b
RequestId: 399d825b-0f06-44b0-a06b-4b50db7807ec
Timestamp: 13/06/2022 16:39:57 +02:00

Re: Error when publishing report from PBI Report Builder to PBI Cloud

Hariharan_R — Wed, 15 Jun 2022 14:05:17 GMT

Hi,

As per your error message "NotCreatedByFormattedTableReport". You are doing the changes on the formatted table report which you created in Power BI service and downloaded to local and doing some changes and upload it again. This is not supported yet.

I have mentioned this in my video - https://www.youtube.com/watch?v=X1z67FwOSp0

Thanks

Hari

Did I answer your question? Then please mark my post as the solution.
If I helped you, click on the Thumbs Up to give Kudos.

My Blog :: YouTube Channel :: My Linkedin

Re: Error when publishing report from PBI Report Builder to PBI Cloud

Anonymous — Wed, 15 Jun 2022 14:16:44 GMT

I'm getting exactly the same error on a brand new report as well:

Re: Error when publishing report from PBI Report Builder to PBI Cloud

AnonymousPerson — Wed, 29 Jun 2022 17:17:35 GMT

Looks like this error is also behaving as a catch-all at the moment (June 2022), which makes me assume the PBI Report Builder app hasn't been updated for the existence of the Formatted Tables feature.

For example, a colleague tried to deploy a paginated report created locally to a non-premium workspace, and got the error referenced above.

Re: Error when publishing report from PBI Report Builder to PBI Cloud

Anonymous — Wed, 06 Jul 2022 13:45:01 GMT

In my case, that's not what happened at all - the table was not created in Power BI service - it only existed in the desktop version.

Re: Error when publishing report from PBI Report Builder to PBI Cloud

fergrro — Thu, 21 Jul 2022 23:13:37 GMT

Yup, same error here 😞

Operation returned an invalid status code 'BadRequest' ErrorCode: NotCreatedByFormattedTableReport Details: An unknown error was encountered. Please try again. ResponseId: b77dd97b-6294-45a8-8a21-20eeffec5711 ActivityId: 00590946-6381-4720-99b6-c2e14ad25915 RequestId: 8391cac3-c00f-493d-bdc7-6205767a0b99 Timestamp: 7/21/2022 6:09:34 PM -05:00

I started creating a very simple new report locally and got the error when I tried to publish it...

Re: Error when publishing report from PBI Report Builder to PBI Cloud

fpaim — Fri, 22 Jul 2022 11:33:36 GMT

Does anyone discovered how to handle this error? We're in July/22 and still having the same error even creating brand new reports...

Re: Error when publishing report from PBI Report Builder to PBI Cloud

Anonymous — Thu, 04 Aug 2022 17:35:44 GMT

I was having the same problem, and was able to fix it by following this simple step on the microsoft site bellow:

https://docs.microsoft.com/en-us/power-bi/paginated-reports/paginated-reports-save-to-power-bi-service

Re: Error when publishing report from PBI Report Builder to PBI Cloud

akee — Mon, 07 Nov 2022 03:25:25 GMT

This does not solve the problem, it states the problem.

Re: Error when publishing report from PBI Report Builder to PBI Cloud

Anonymous — Wed, 16 Nov 2022 10:30:00 GMT

Created a new report on local but getting the same error when trying to publish. Can some one guide what is causing this error?

Re: Error when publishing report from PBI Report Builder to PBI Cloud

akee — Wed, 16 Nov 2022 12:40:12 GMT

Greetings. I'm fairly certain that you get that error if you are not posting the report to a premium workspace. However, to have a premium workspace, one must pay $20/month. That is not in my company's budget, so I created the reports in MS Access instead.