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

Score big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount

Reply
Anonymous
Not applicable

Adding fields in Advanced Editor causing PBI Desktop to crash

I am using a Web Service connection to pull data from a program called Version One into my Power BI reports using the Power BI Desktop tool.  Every other time I add a new field into the web url to bring into my data, using the Advanced Editor, Power BI Desktop crashes and closes.

 

Attached is a snapshot of the Advanced Editor window where I make changes.  The last time Power BI Desktop closed, I had added in "BlockingIssues" into the Source line so I could bring in that field to report on.Advanced EditorAdvanced Editor

 

1) Can someone point me in the right direction of an error log where I can check what is causing the issue?

2) If not, does anyone know what might be causing this?

 

Thank you!

1 ACCEPTED SOLUTION
Anonymous
Not applicable

I had a similar issue when I was working in Advanced Query Editor. I raised a support ticket and the solution that PBI engeneer advised is:

Go to file -> options and settings -> options -> power query editor -> untick enable M intellisense

This solved my issue, hope it helps you as well

View solution in original post

5 REPLIES 5
v-juanli-msft
Community Support
Community Support

Hi @Anonymous 

1. What causes this?

What version of Power BI Desktop are you using? Does the report include custom visuals or preview features?

Please Update to the lastest version

 

Is it failing consistently? Can you reproduce it when connecting to an excel file?

 

I'm afraid it doesn't support to connect to Version One with Web.contents function.

You could use the VersionOne Data API to query data.

Sharing an example of pulling data from an API and getting it into Power BI

 

2. How to check error logs?

Are you seeing a “Send a frown” pop-up? 

If so, this is very helpful in that the diagnostics have been aggregated for quick inspection. 

 

In the Options menu under the Diagnostics pane, you can enable tracing. The log is quite verbose and helpful. The log is stored under %UserProfile%\Microsoft\Power BI Desktop Store App\Traces. Tracing has identified several issues for me where the other techniques did not reveal any hints.

 

Best Regards
Maggie

 

Community Support Team _ Maggie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Anonymous
Not applicable

Hi @v-juanli-msft ,

 

I am using the June 2019 Power BI Desktop version.  I have one custom visual downloaded and available for use, but it is not used in the report that keeps crashing.  It does fail consistently when I try to add a field right after creating or modifying an existing API connection.  The excel file I have connected to does not produce the issue.  I am using the VersionOne Data API to pull the data.  Thinking through this now, I think this may be caused when I try to change the  connection type and add a field at the same time.  I initially use a web service URL (the API url) to input as a new data source.  Then I convert that from an XML connection to a JSON by changing "xml.tables" to "json.document" in the Advanced Query.  After changing that, I add a new field at the end of the URL in the Advanced Query editor to bring in.  That is when the program crashes.

 

A black command window pops up for a brief second before all Power BI Desktop windows close when it crashes.  There is no "Send a frown" pop up before or after the crash.  I have enabled tracing now so I can pass on the information to you next time it happens.

 

- Jordan

Anonymous
Not applicable

Hi @v-juanli-msft ,

 

Sorry to bug you again, but do you know if there may be a work around for this?

Anonymous
Not applicable

Here is a snapshot of a window that pops up right before Power BI crashes

 

pbi error.png

 

Anonymous
Not applicable

I had a similar issue when I was working in Advanced Query Editor. I raised a support ticket and the solution that PBI engeneer advised is:

Go to file -> options and settings -> options -> power query editor -> untick enable M intellisense

This solved my issue, hope it helps you as well

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

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

August 2025 community update carousel

Fabric Community Update - August 2025

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