I have found that the "Recent sources" menu in Power BI Desktop is not working (at least not as I expected), steps to replicate the issue: Open Power BI Desktop Click on "Get Data" Get data from any data source (In my example a Snowflake connection) and load it into Power BI Desktop Click on “Recent sources” in the “Home” section of the ribbon. The “Most recent” displays the Snowflake connection as expected. Click on “More…” The “Recent Sources” modal dialog is displayed showing the new connection. Save the .pbix file. Close Power BI Desktop Open Power BI Desktop & load the previous pbix file Click on “Recent Sources”. PBI Desktop displays a the “Recent Sources” modal MINUS the new connection... Version: 2.144.1155.0 64-bit (June 2025) ... View more

Since today we can't connect to our Azure Databricks instances through PBI Desktop. It seems like there is an issue with the ODBC driver.   Error message: "DataSource.MissingClientLibrary: The 'Driver' property with the value '{Simba Spark ODBC Driver}' does not match an installed ODBC driver."   Is this a Power BI issue? Maybe an issue in the latest PBI update? PBI Desktop version 2.132.1053.0 ... View more

Has anyone else noticed any bugs with the new card visual since the March 25 update?  I had some cards with the values switched off that are now suddenly showing.  Although they are switched off in the desktop app build they inadvertently get switched back on in the service after publishing and my existing reports all have values now on where they should be off.   I have had to edit directly in the service to get this sorted which is a real pain to do. ... View more

I have been troubleshooting this for a week now.  When launching BI either by running the BI Desktop application or by trying to open an existing datamodel I get the following error.   Prior to the error BI hard locked and could not recover. Waited for 45 minutes and had to kill the process to get it to shutdown. Afterwards this started to happen.    AS Process PID=XXXXXX Has exited with ExitCode = 0   This dialog appears twice in succession then kills the app.       NOTE: This has also happened on one of our IT administrators sytems where BI had NOT had the proccess killed, just tried to launch the application and seeing the same issue. This is not enterprise wide, and has only happened a few machines, and does not appear to be related to current local user profile.     Troubleshooting performed: Uninstalled and reinstalled BI Two versions (the last version and the one released 06-05-2025) hard restart between uninstall and reinstall Uninstalled and reinstalled the .net framework hard restart between uninstall and reinstall Verified all Windows updates are current Deleted all folders and files I could find related to the BI isntall Deleted all registry keys related to BI Install Created a new user profile and installed to the new profile, same issue created a MS Sandbox and installed there, different issue (Faield to authenticate). Yes the sandbox had internet access and firewall disabled.  Checked System Event logs: no info Ran DISM & SFC check and no issues found. I look forward to hearing your suggestions, I would prefer to not have to wipe my machine and start over.  Kind regards, Jason crash log from BI below. Feedback Type: Frown (Error) Timestamp: 2025-06-06T16:03:18.9533269Z Local Time: 2025-06-06T11:03:18.9533269-05:00 Session ID: decce8dd-d3a4-4f89-8acf-1c6f7bcbcf3e Release: May 2025 Product Version: 2.143.1378.0 (25.05)+4e1de9c957866bc5336e0d250838314aa54ff3a8 (x64) Error Message: AS Process PID=14788 has exited with ExitCode=0, ExitTime=2025-06-06T10:50:02.6540925-05:00 Stack Trace: Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcessUnexpectedExitException at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcess.AcquireServerDynamicPortInfo() at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcess.EnsureServiceIsReady() at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcess.Start() at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesService.<StartProcess>d__30.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.PowerBI.Client.Windows.Utilities.AggregateExceptionHandlingExtensions.WaitAndUnpackException(Task task) at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesService.CreateEmptyDatabase(DatabaseDocuments initialDocuments) at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesService.<StartProcess>d__30.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__1.MoveNext() Stack Trace Message: AS Process PID=14788 has exited with ExitCode=0, ExitTime=2025-06-06T10:50:02.6540925-05:00 Invocation Stack Trace: at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace() at Microsoft.Mashup.Client.UI.Shared.StackTraceInfo..ctor(String exceptionStackTrace, String invocationStackTrace, String exceptionMessage) at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.GetStackTraceInfo(Exception e) at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.ReportException(IWindowHandle activeWindow, IUIHost uiHost, FeedbackPackageInfo feedbackPackageInfo, Exception e, Boolean useGDICapture) at Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.<>c__DisplayClass14_0.<HandleException>b__0() at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.<>c__DisplayClass2_0.<SendAndMarshalExceptions>b__0(Object null) at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Delegate.DynamicInvokeImpl(Object[] args) at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbacks() at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous) at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args) at System.Windows.Forms.WindowsFormsSynchronizationContext.Send(SendOrPostCallback d, Object state) at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.SendAndMarshalExceptions(SynchronizationContext context, Action callback) at Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.HandleException(Exception e) at Microsoft.PowerBI.Client.PowerBIUnexpectedExceptionHandler.HandleException(Exception e) at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__1.MoveNext() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run() at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Delegate.DynamicInvokeImpl(Object[] args) at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbacks() at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous) at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args) at System.Windows.Forms.WindowsFormsSynchronizationContext.Send(SendOrPostCallback d, Object state) at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.SendAndMarshalExceptions(SynchronizationContext context, Action callback) at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.OnScopesChanged(Scope before, Scope after) at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.<>c__DisplayClass2_0.<SendAndMarshalExceptions>b__0(Object null) at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Delegate.DynamicInvokeImpl(Object[] args) at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbacks() at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.WaitOnUIThreadForTaskCompletion[T](Task`1 task) at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.BlockUIAndRun[T](Func`1 asyncMethod, PowerBIProgress progress) at Microsoft.PowerBI.Client.Windows.Services.CurrentArtifactManager.OpenArtifactAndSetAsCurrent(IPowerBIWindowService windowService, IPowerBIArtifact artifactToOpen, IExceptionHandler exceptionHandler, Nullable`1 entryPoint) at Microsoft.PowerBI.Client.CommandLineFileService.TryOpenOrCreateReport(IPowerBIWindowService windowService, IExceptionHandler exceptionHandler, Boolean forceCreate) at Microsoft.PowerBI.Client.Program.<>c__DisplayClass7_1.<RunApplicationLegacy>b__1() at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass3_0.<HandleExceptionsWithNestedTasks>b__0() at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action) at Microsoft.PowerBI.Client.Program.RunApplicationLegacy(String[] args, IPowerBIRootTrace trace) at Microsoft.PowerBI.Client.Program.Main(String[] args) PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.143.1378.0","ModuleName":"Microsoft.PowerBI.Client.Windows.dll","Component":"Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcess","Error":"Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcessUnexpectedExitException","MethodDef":"AcquireServerDynamicPortInfo","ErrorOffset":"110","ErrorCode":""} OS Version: Microsoft Windows NT 10.0.19045.0 (x64 en-US) CLR Version: 4.8 or later [Release Number = 528372] Peak Virtual Memory: 70 GB Private Memory: 380 MB Peak Working Set: 466 MB IE Version: 11.3636.19041.0 User ID: 93f51f9a-7231-4850-95c1-9049ecebcb14 Workbook Package Info: None Telemetry Enabled: True PowerBIUserFeedbackServices_IsReported: True DPI Scale: 100% Supported Services: Power BI ... View more

Refreshes are suddenly failing where they've been set up by users through a gateway, with the following error appearing: ServerError_DMTS_MonikerDatasourcesNotFoundErrorCode And going into the gateway to reset them, the users are getting the following message. Users do have access and permission to the gateways, but only Admins seem to be able to reset the gateways now. This is resulting in numerous refresh failures, and started happening either late yesterday or early today. ... View more

Here is the bug report Super User Idrissshatila wanted me to post in this channel:   MAJOR bug as reported in thread: https://community.fabric.microsoft.com/t5/Service/RLS-and-USERELATIONSHIP-problem/m-p/4367418 RLS and USERELATIONSHIP / CROFFILTER problem. Crucial reports all over the continent are bugging out. According to user, 11 pm Swedish CET+1, everything worked fine, but suddenly this error occurs: Error message example: "The UseRelationship() and CrossFilter() functions may not be used when querying ‘TableA’ because it is constrained by row-level security defined on ‘TableA’ or related tables" Another bug report for same issue: https://community.fabric.microsoft.com/t5/Service/Sudden-RLS-and-USERELATIONSHIP-problem/m-p/4367400#M261685 ... View more

Hi everyone,   We're currently running the latest version of Power BI (x64) on Windows 11 ARM, using Parallels 20 on an Apple M4 Pro Mac. I was recently assigned to work on a Power BI dashboard that works flawlessly (10/10 times) on my colleague's standard Windows machine. The data loads fine and refreshes without any errors on both systems.   However, we noticed a critical issue: Any visual that includes a Date field filter fails to load on my ARM-based setup. No meaningful error message is shown upon clicking the detailed error (empty line, char indicator) — the visual simply doesn't render, but does upon removing the date releated filter.   We attempted to: Recreated the visuals and relationships Adjusted regional and locale settings Confirmed the dataset integrity and formatting Tested across different Date fields and visuals We're now suspecting that this issue is related to ARM architecture compatibility, possibly with how Power BI handles datetime rendering or underlying libraries.   Has anyone else experienced this issue on Apple Silicon M4 with Parallels or any other ARM-based setup? Any suggestions or insights would be greatly appreciated!   Thanks in advance. ... View more

Since the May release, any native query using a Snowflake Connector v2.0 connection experiences boolean type conversion errors on refresh.    let Source = Snowflake.Databases("<snowflake account url>","<warehouse name>",[Implementation="2.0"]), data = Value.NativeQuery( Source{[Name = "<database name>",Kind="Database"]}[Data], "select false as v union all select true as v" , null , [EnableFolding = true] ) in data   The preview in Power Query is fine, but the error is presented when dataset is refreshed.      Additionally, converting the datatype in power query doesn't work.      I suspect a workaround will be to convert the data to 1,0 values either in the snowflake query or via a text step in powerquery   This seems to be, though, to be an unintended and relatively serious breaking change.          ... View more

Hello Team,   I noticed many users faced this error "Unsupported Table name " Measures" has been found in model schema" after   the Power BI February update, it has some new validation that will prevent opening your pbix files if you've previously created a table named " Measures" with the space in front (using [ Measures]=  )     one current solution found by Stephanie Bruno is that: To solve this, you'll have to download an older version of desktop (I used November), open your pbix file and rename the table, and save. Then you'll be able to open it in the latest version again. You can get older versions here: https://lnkd.in/enrn8cQZ    link to Her post on linkedin: https://www.linkedin.com/posts/brunostephanie_previous-monthly-updates-to-power-bi-desktop-activity-7299801245962194945-Li_n?utm_source=share&utm_medium=member_desktop&rcm=ACoAAB6cItsB17Ovl3CRReulA7ZfV6CaNMQQzR4    ... View more

Hi,  I encounter a bug in PBI Desktop in custom settings for the new 'Button Slicer' visual. In Format visual - Buttons - Border it is impossible to change the color for any other than default gray. This issue affects the 'Hover' and 'Press' setting.  ... View more

Per the following thread: Re: DAX Info Functions Against Published Datasets - Microsoft Fabric Community   It seems that we're unable to execute any of the INFO() DAX functions when using the ExecuteQueries REST API on a published semantic model. I have a few pipelines that require extracting metadata from the semantic model, and everything was working fine until this morning when I started getting an Analysis Services error code of "3239575574" (below is the full JSON of the error message).     { "error": { "code": "DatasetExecuteQueriesError", "pbi.error": { "code": "DatasetExecuteQueriesError", "parameters": {}, "details": [ { "code": "DetailsMessage", "detail": { "type": 1, "value": "Failed to execute the DAX query." } }, { "code": "AnalysisServicesErrorCode", "detail": { "type": 1, "value": "3239575574" } } ] } } } ... View more

Hello, Refresh of individual tables does not seem to work in the latest June 2024 version of Power BI desktop. It was fine with the May 2024 version. I even tried re-installing Power BI. However, nothing seems to work.  ... View more

In the Card (New) Visual, when I turn off the Callout Values in Power BI Desktop, so they shouldn't be displayed on the report page, they turn off in Power BI Desktop but still display in Power BI Service.     ... View more

Hello,   I posted this in the help section of the community, but I believe it is a bug with the most recent update (October 2023).   I routinely export desktop PBI reports to PDF for sharing in newsletters. Today, for some reason, when I exported to PDF, only about the top left quarter of each page is exported instead of the full page.    I have attempted exporting multiple different reports, closing and re-opening Power BI, and restarting my computer to no avail. Nothing in my report has changed other than refreshing the data. Each page is the default 16:9 720x1280 size.   I was able to successfully export from a report published to the online workspace, but not desktop. A coworker was also able to successfully export from desktop with the August 2023 update.    Link to help thread with numerous others with the same issue   Any help in getting this resolved would be appreciated! ... View more

Since February 26, 2025, the traffic light colors in my published Power BI report are no longer displayed. The traffic lights appear black, whereas they show correctly in Power BI Desktop. These KPIs have remained unchanged for the past three years and were added via Tabular Editor 2 as 'Traffic Light - Single' status graphics.   It seems that the recent update to the Power BI Service Gateway (February 2025) may be affecting the display of the KPIs in the published report. I’m wondering if anyone else has experienced the same issue after this update, and if there is a solution. For more details on the update, see: https://powerbi.microsoft.com/en-us/blog/on-premises-data-gateway-february-2025-release/   Thanks in advance for your help! ... View more

Please be aware that I have identified a bug or compability issue with Power BI Desktop (versions starting with March 2025 and after) that present as very odd behavior when run under the latest version Parallel's Desktop Pro Edition v20.3.0 (55895) virtual machine (Windows 11 Pro v24H2, build 26100.3915, 16 GB RAM) on a MacBook Pro (M4 Pro Apple Silicon chip).   I have created a simplified test PBIX file with one static date table that displays a broken visual in the newer PBI versions when one uses the Advanced Filter option under the filter pane.  If one replaces the Advanced filter with a Basic filter option to filter the same visual, the visual displays fine.  When one clicks the See details from the broken visual they get the following dialog.   Broken visual details dialog   This buggy behavior is not present in the February 2025 released version of the PBI app (run under Parallels Desktop virtual machine) or in more recent versions that are run on a physical PC. This is a copy of the issue I raised int Forums yesterday. Power BI Desktop issues starting March 2025 releas... - Microsoft Fabric Community ... View more

I noticed that couple of users have posted about having the values in filter pane on service showing in black when using a dark theme, this is preventing from the ability to see the values to be selected.   ... View more

Content managers/Custom Roles are now unable to see the "Scheduled Refresh" menu under Manage for reports. As an admin i can see the button and see the schedules as normal but the AD group covering all my "Standard Users" which fixed the issue in Jan version doesnt work at all now in May 2. The only thing thats changed is updating versions, no backend role changes etc as i've double checked the values for "manage model" etc are all ticked as they were previously.   Forum discussion : Re: Scheduled Refresh Button Hidden - May 2025 - Microsoft Fabric Community ... View more