Error message pops up when writing Korean letter within Formula bar in Power Query Editor

[ken]

Hi, recently I have been experiencing an error message popping up when I try to write any Korean inside Power Query Editor Formula Bar.

Below is the error message I captured. 

Currently only the workaround is to write Korean text outside Power Query and paste it back into Power Query formula bar, which is an absolute non-sense and hassle.

Please investigate them immediately because my Korean clients are experiencing the same issue.

Guess it is a bug after some recent updates.

[Anonymous]

Hi @ken 

I tested it in Desktop , there was nothing reported as an error . My test version is 2.112.603.0 64-bit (December 2022) .

Best Regards,
Community Support Team _ Ailsa Tao

[ken]

Hello,  Ailsa Tao

Thanks for your reply.

I tried reinstalling my Power BI Desktop(v. Dec.22) and the issue is still with me.

I was wondering if Excel Power Query might show the same issue so I tried, and I found the same issue occurs in Excel PQ as well.

Therefore, I guess this may not be solely related to Power BI but related to Power Query functionality which might be conflicting with some kind of language setting across my computer/Window.

I have been using Power BI for years now as BI consultant/trainer and there was no issue like this until recently.  If the same issue doesn't show up on your side, please let me know what I can do to solve this issue.

Again, below is the full message with screenshot when I try to type/change any Korean character(e.g., name of columns) inside the formula bar for any data source.

FYI,

-The same issue occurs inside Advanced Editor as well.

-If I write Korean outside and paste it in, then it has no issue.

Please provide some suggestions I can investigate and try.

-------------------------------------------

Feedback Type:
Frown (Error)

Error Message:
Unable to get property 'setWidth' of undefined or null reference

TypeError: Unable to get property 'setWidth' of undefined or null reference
at Anonymous function (ms-pbi://pbi.microsoft.com/ts/MonacoEditor/editor.bundle.js:3:720247)
at e.prototype.fire (ms-pbi://pbi.microsoft.com/ts/MonacoEditor/editor.bundle.js:3:29233)
at Anonymous function (ms-pbi://pbi.microsoft.com/ts/MonacoEditor/editor.bundle.js:3:1011603)

Stack Trace:
Microsoft.Mashup.Host.Document.JavaScriptException
at Anonymous function (ms-pbi://pbi.microsoft.com/ts/MonacoEditor/editor.bundle.js:3:103829)

Stack Trace Message:
Unable to get property 'setWidth' of undefined or null reference

TypeError: Unable to get property 'setWidth' of undefined or null reference
at Anonymous function (ms-pbi://pbi.microsoft.com/ts/MonacoEditor/editor.bundle.js:3:720247)
at e.prototype.fire (ms-pbi://pbi.microsoft.com/ts/MonacoEditor/editor.bundle.js:3:29233)
at Anonymous function (ms-pbi://pbi.microsoft.com/ts/MonacoEditor/editor.bundle.js:3:1011603)

Invocation Stack Trace:
위치: Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
위치: Microsoft.Mashup.Client.UI.Shared.StackTraceInfo..ctor(String exceptionStackTrace, String invocationStackTrace, String exceptionMessage)
위치: Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.GetStackTraceInfo(Exception e)
위치: Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.ReportException(IWindowHandle activeWindow, IUIHost uiHost, FeedbackPackageInfo feedbackPackageInfo, Exception e, Boolean useGDICapture)
위치: Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.<>c__DisplayClass14_0.<HandleException>b__0()
위치: Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.HandleException(Exception e)
위치: System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
위치: System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
위치: System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
위치: Microsoft.Mashup.Client.UI.Shared.JsExportWrapper.<>c__DisplayClass13_0.<InvokeMember>b__0()
위치: Microsoft.Mashup.Client.UI.Windows.JsErrorHandler.WrapInvokeHost(Func`1 invokeHost)
위치: System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
위치: System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
위치: System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
위치: System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
위치: System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
위치: System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
위치: Microsoft.Mashup.Client.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction)
위치: Microsoft.PowerBI.Client.Program.<>c__DisplayClass4_1.<Main>b__3()
위치: Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass3_0.<HandleExceptionsWithNestedTasks>b__0()
위치: Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
위치: Microsoft.PowerBI.Client.Program.Main(String[] args)

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.112.603.0","ModuleName":"ms-pbi://pbi.microsoft.com/ts/MonacoEditor/editor.bundle.js","Component":"","Error":"Error","MethodDef":"Anonymous function","ErrorOffset":"3:103829"}

Snapshot Trace Logs:
C:\Users\havef\Microsoft\Power BI Desktop Store App\FrownSnapShot50f0acf5-d3ad-4ede-8612-3d06847f4307.zip

Model Default Mode:
Empty

Model Version:
PowerBI_V1

Performance Trace Logs:
C:\Users\havef\Microsoft\Power BI Desktop Store App\PerformanceTraces.zip

Enabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_azureMapVisual
PBI_compositeModelsOverAS
PBI_b2bExternalDatasetSharing
PBI_enhancedTooltips
PBI_enableWebView2
PQ_WebView2Connector
PBI_sparklines
PBI_scorecardVisual
PBI_NlToDax
PBI_fieldParametersSuperSwitch
PBI_horizontalFusion
PBI_optimizeTabRibbon
PBI_relationshipEditPane

Disabled Preview Features:
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

PowerBIUserFeedbackServices_IsReported:
True

Formulas:

section Section1;

shared Sheet1 = let
원본 = Excel.Workbook(File.Contents("C:\ONIONBI\02 Training\01 Personal\02 Offline\01 Group\01_기본반\02 수업자료_v3.0\03_샘플데이터_2015년도 제품별 판매금액.xlsx"), null, true),
Sheet1_Sheet = 원본{[Item="Sheet1",Kind="Sheet"]}[Data],
#"승격된 헤더" = Table.PromoteHeaders(Sheet1_Sheet, [PromoteAllScalars=true]),
#"변경된 유형" = Table.TransformColumnTypes(#"승격된 헤더",{{" 2015년도 제품별 판매금ㅇ ", type text}, {"Column2", type text}, {"Column3", type any}, {"Column4", type any}, {"Column5", type any}, {"Column6", type any}, {"Column7", type any}, {"Column8", type any}, {"Column9", type any}, {"Column10", type any}, {"Column11", type any}, {"Column12", type any}, {"Column13", type any}, {"Column14", type any}, {"Column15", type any}, {"Column16", type any}, {"Column17", type any}, {"Column18", type any}, {"Column19", type any}, {"Column20", type any}})
in
#"변경된 유형";

[ken]

Dear Team,

While experiencing the same issue, I tried disabling the M intellisense function as below screenshot, and I no longer get the error. I suspect that the error has something to do with some conflict between Korean character construction process and M intellisence function.

The problem is that I can't use the M intellisense capability without the error, which is quite frustrating. 

I still have no idea what causes this conflict on my side so if this post reaches you by any chance, please investigate the potential conflict issue between M intellisence function and Korean letter construction.

p.s. It only happens when constructing a Korean word inside Formular bar, Advanced Editor and Custom Column dialog box.

Thanks.

[MaybeiAmGhost]

Same error is happening for me.

OS: Windows 11 Enterprise

Version: Power BI Desktop  2.116.966.0 64-bit(Installed from Microsoft Store)

Here's Video for reproducing this error:

https://1drv.ms/v/s!AnG3Z334R_5pmlmXTkEsJpPG8i_b?e=ygHrvq