I have a pbix that works perfectly fine with a table named " Measures", which is used to organize calculated measures in the data model.  I saved this preexisting pbix as a Power BI Project (preview feature), which creates a pbip file and several other files with the intent to check this into a version control system.  After saving as a Power BI Project, and attempting to open the pbip file (the project), I am presented an error that prevents me from openning the project:    Unsupported Table name " Measures" has been found in the data model schema.     The methodology of placing a leading space has been used by many to create and organize a list of measures to the top of the list of tables, and to bypass the requirement that something cannot be named "Measures", but can be named " Measures".     Feedback Type: Frown (Error) Timestamp: 2023-07-19T12:37:04.4961330Z Local Time: 2023-07-19T08:37:04.4961330-04:00 Session ID: 994b871a-a52b-44b0-8cb5-f09c3c47c3ff Release: July 2023 Product Version: 2.119.701.0 (23.07) (x64) Error Message: Unsupported Table name " Measures" has been found in data model schema. Stack Trace: at Microsoft.PowerBI.Client.Windows.ReportPreparer.EnsureValidObjectName(INamedMetadataObject obj) at Microsoft.PowerBI.Client.Windows.ReportPreparer.ValidateObjectNames(Report report) at Microsoft.PowerBI.Client.Windows.ReportPreparer.EnsureSupportedModelStructure(Report report, Boolean blockOnInvalidNames) at Microsoft.PowerBI.Client.Windows.ReportPreparer.<Prepare>d__9.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.Services.BiProjectOperationHandler.<LoadFromProject>d__18.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.Services.BiProjectOperationHandler.<LoadFromPbip>d__16.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.Services.BiProjectOperationHandler.<LoadPbiFile>d__13.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.Services.CurrentFileManager.<ExecuteAndHandleFileOpenErrors>d__35.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.Services.CurrentFileManager.<>c__DisplayClass23_0.<<OpenFileAndSetAsCurrent>b__1>d.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.Services.UIBlockingService.<>c__DisplayClass13_0`1.<<BlockUIAndRun>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.WaitOnUIThreadForTaskCompletion[T](Task`1 task) at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.BlockUIAndRun[T](Func`1 asyncMethod) at Microsoft.PowerBI.Client.Windows.Services.CurrentFileManager.OpenFileAndSetAsCurrent(IPowerBIWindowService windowService, IPowerBIFile fileToOpen, Nullable`1 entryPoint) at Microsoft.PowerBI.Client.Program.TryOpenOrCreateReport(IPowerBIWindowService windowService, ICurrentFileManager currentFileManager, IFileHistoryManager fileHistoryManager, CommandLine commandLine, FileType fileType, IFileInformationProtectionManager fileInformationProtectionManager, IPowerBITelemetryService telemetryService) at Microsoft.PowerBI.Client.Program.<>c__DisplayClass6_0.<RunApplication>b__0() at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass3_0.<HandleExceptionsWithNestedTasks>b__0() at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action) Stack Trace Message: Unsupported Table name <ccon>" Measures"</ccon> has been found in data model schema. Invocation Stack Trace: at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace() at Microsoft.Mashup.Client.UI.Shared.FeedbackErrorInfo..ctor(String message, Exception exception, Nullable`1 stackTraceInfo, String messageDetail) at Microsoft.PowerBI.Client.PowerBIUnexpectedExceptionHandler.HandleKnownExceptions(Exception e) at Microsoft.PowerBI.Client.PowerBIUnexpectedExceptionHandler.HandleException(Exception e) at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action) at Microsoft.PowerBI.Client.Program.RunApplication(String[] args) at Microsoft.PowerBI.Client.Program.Main(String[] args)   ... View more

I'm having a problem with a dataflow that seems to reoccur every morning after functioning correctly the previous afternoon. In the refresh history log it gives the following error:   Error: Encountered user gateway exception: '<ccon>The credentials provided for the PowerBI source are invalid. (Source at PowerBI.)</ccon> [DM_ErrorDetailNameCode_UnderlyingErrorCode]=-2147467259 [DM_ErrorDetailNameCode_UnderlyingErrorMessage]=<ccon>The credentials provided for the PowerBI source are invalid. (Source at PowerBI.)</ccon> [DM_ErrorDetailNameCode_UnderlyingHResult]=-2147467259 [Microsoft.Data.Mashup.CredentialError.DataSourceKind]=PowerBI [Microsoft.Data.Mashup.CredentialError.DataSourceOriginKind]=Web [Microsoft.Data.Mashup.CredentialError.DataSourceOriginPath]=https://api.powerbi.com/powerbi/globalservice/v201606/clusterdetails [Microsoft.Data.Mashup.CredentialError.DataSourcePath]=PowerBI [Microsoft.Data.Mashup.CredentialError.Reason]=AccessForbidden [Microsoft.Data.Mashup.MashupSecurityException.DataSources]=[{"kind":"PowerBI" "path":"PowerBI"}] [Microsoft.Data.Mashup.MashupSecurityException.Reason]=AccessForbidden [InnerType]=MashupCredentialException The credentials provided for the PowerBI source are invalid. (Source at PowerBI.) [GatewayPipelineErrorCode]=DM_GWPipeline_Gateway_InvalidConnectionCredentials [ErrorShortName]=GatewayClientErrorResponseException[GatewayId=830927]/MashupDataAccessCredentialException[ErrorCode=-2147467259 HResult=-2147467259]/Wrapped(MashupCredentialException)[ErrorCode=-2147467259 HResult=-2147467259] [ExceptionErrorShortName]=GatewayClientErrorResponseException[GatewayId=830927]'. RootActivityId = b7685438-32e7-4086-a129-0e9d5ec4ac91.Param1 = <ccon>The credentials provided for the PowerBI source are invalid. (Source at PowerBI.)</ccon> [DM_ErrorDetailNameCode_UnderlyingErrorCode]=-2147467259 [DM_ErrorDetailNameCode_UnderlyingErrorMessage]=<ccon>The credentials provided for the PowerBI source are invalid. (Source at PowerBI.)</ccon> [DM_ErrorDetailNameCode_UnderlyingHResult]=-2147467259 [Microsoft.Data.Mashup.CredentialError.DataSourceKind]=PowerBI [Microsoft.Data.Mashup.CredentialError.DataSourceOriginKind]=Web [Microsoft.Data.Mashup.CredentialError.DataSourceOriginPath]=https://api.powerbi.com/powerbi/globalservice/v201606/clusterdetails [Microsoft.Data.Mashup.CredentialError.DataSourcePath]=PowerBI [Microsoft.Data.Mashup.CredentialError.Reason]=AccessForbidden [Microsoft.Data.Mashup.MashupSecurityException.DataSources]=[{"kind":"PowerBI" "path":"PowerBI"}] [Microsoft.Data.Mashup.MashupSecurityException.Reason]=AccessForbidden [InnerType]=MashupCredentialException The credentials provided for the PowerBI source are invalid. (Source at PowerBI.) [GatewayPipelineErrorCode]=DM_GWPipeline_Gateway_InvalidConnectionCredentials [ErrorShortName]=GatewayClientErrorResponseException[GatewayId=830927]/MashupDataAccessCredentialException[ErrorCode=-2147467259 HResult=-2147467259]/Wrapped(MashupCredentialException)[ErrorCode=-2147467259 HResult=-2147467259] [ExceptionErrorShortName]=GatewayClientErrorResponseException[GatewayId=830927] Request ID: ad7bb2b3-f898-43f7-9788-7fab4416aa79.   I've checked all connections in 'Manage connections and gateways' and reauthenticated everything. I've also checked the dataset for this dataflow to make sure it is all set up correctly. It's becoming really frustrating as it seems to break overnight every day and I have to spend time every day trying different things to get it to work. ... View more

Version 2.825858.641 x64 (June 2020) "Store datasets using enhanced metadata format" IS enabled in Preview Features.   I have been running into issues when I attempt to use parameters in an M-query to retrieve and transform data from a Sharepoint site in custom M queries created from the "New Source" -> "Blank Query" function in the Query Editor's UI.   A collection of queries currently uses two different parameters, one for the URL to the Sharepoint Workspace and one for the URL to the desired file's directory on the SP site: Source = SharePoint.Files(PBISharepointBudgetWorkspaceURL), #"fp_SharepointArtifact" = Source{[Folder Path=PBISharepointBudgetWorkspaceDimensions, Name="ExpenseActuals.xlsx"]}[Content]   Despite the query editor successfully being able to ETL the desired files, upon selecting "Close and Apply", the changes appear to go into effect, but then the warning notification "There are pending changes in your queries that haven't been applied" appears at the top of the report canvas pane with the options to "Apply changes" or Discard changes":   Pending Changes Notification   Selecting "Apply changes" appears to apply a transformation to "Queries Metadata": Apply changes Query Metadata example   but as soon as its loaded the warning notifcation to apply or discard immediately appears again.   Selecting "Discard changes" indicates that I've changed something about the parameter: Apply changes Queries Metadata example Clicking "Discard" appears to have no effect whatsoever and the warning notification persists at the top of the report canvas pane. If I retroactively hardcode one of the parameters, replacing its occurrence in all instances but keeping the other parameter in each query where it's used as an argument, then the "Discard Changes" dialogue tells me that the change is then occurring with the other parameter.   I don't know if this is a function of the new enhanced metadata format or not. My theory is it has to do with the new data format and/or the latest version of PBI Desktop. Seems like other folks have had the same issue in the past under different versions of the desktop application and the only workaround was rolling back to a prior version.    Has anyone found a better way to resolve this issue?   ... View more

The Relationship Diagram is not showing the lines of the relationships in the Model view. All the relationships are fine, but not showing in this view. This is huge for me as we have many tables and some complex relationships.  It is not just one PBIX file but all of them.   ... View more

Since the August 2022 release, after pasting a long formula into the formula editor, it is not possible to scroll down to see the bottom of the formula. In the below screenshot, I have scrolled to the very bottom, and yet much of the formula cannot be seen. Please can this be looked at. Thanks.       ... View more

Yesterday my security was working.  But it stopped working once the December Power BI desktop update was pushed out.  I can no longer click on the Apply security filter in both directions checkbox any more.  I opened the pbix on a different system running the November release with and can click the checkbox with no issues.         ... View more

I've noticed that when I refresh my dataset, it clears out any descriptions that I have setup for my standard fields (non-measures). Can I get this issue corrected or can somebody help me figure out a way to retain those values regardless of the dataset being refreshed or not? I'm currently on this version of Power BI Desktop. ... View more

I have a PPU workspace and an ADO repo that I would like to sync. Yesterday I was able to sync them up fine, but today it was having errors so I was going to dissconnect and reconnect the repo. I am being prevented from reconnecting though by this error   I am not sure what it means by the technical details....   ... View more

After instalation of PBI Desktop update (March) I am not ableto open any PBI file (even new blank one). I tried to repair PBI desktop via Control PAnel, reinstall back to rpevious verison, change x64 bit to x32 bit version, but nothing worked.    Error messages varies based on PBI file that i am trying to open, below is one of the error logs that PBI shown me after PBI failed. Sometimes is error message only announcement that PBIDesktop is not able to load data modle and nothing else (what is kinda strange when this error message appear during opening of blank PBI file...   Feedback Type: Frown (Error) Timestamp: 2018-03-16T11:34:23.0617108Z Local Time: 2018-03-16T12:34:23.0617108+01:00 Session ID: a986f59a-fb3f-477b-852e-f5c8a5ebf5a6 Release: March 2018 Product Version: 2.56.5023.942 (PBIDesktop) (x64) Error Message: Couldn't load the model schema. OS Version: Microsoft Windows NT 10.0.16299.0 (x64 en-US) CLR Version: 4.7 or later [Release Number = 461308] Peak Virtual Memory: 35.5 GB Private Memory: 1.08 GB Peak Working Set: 1.06 GB IE Version: 11.309.16299.0 User ID: f140123a-0dfa-4434-8f7c-e25e9a0abb0a Workbook Package Info: 1* - en-US, Query Groups: 5, fastCombine: Enabled, runBackgroundAnalysis: True. Telemetry Enabled: True Model Default Mode: Import Snapshot Trace Logs: C:\Users\v-pavsch\AppData\Local\Microsoft\Power BI Desktop\FrownSnapShot360440546.zip Performance Trace Logs: C:\Users\v-pavsch\AppData\Local\Microsoft\Power BI Desktop\PerformanceTraces.zip Disabled Preview Features: PBI_shapeMapVisualEnabled PBI_EnableReportTheme PBI_numericSlicerEnabled PBI_SpanishLinguisticsEnabled CustomConnectors PBI_AdobeAnalytics PBI_qnaExplore PBI_variationUIChange PBI_customVisualsGallery PBI_canvasTooltips Disabled DirectQuery Options: PBI_DirectQuery_Unrestricted TreatHanaAsRelationalSource Cloud: GlobalCloud DPI Scale: 125% Supported Services: Power BI   ... View more

I seem to be having issues with the recent Power BI update (December 2017), whereby when invlaid relationships are trying to be established between two tables Power BI exits with no warning. ... View more

In the new update, WEEKNUM underlines the parameter. In the previous version, the parameter worked, but after the update, it is underlined.  The calculation still works, but the parameter is underlined and the error is shown - Parameter is not the correct type.  In new calculations, it is underlined as well and if I change it to standard 1 or 2 it still shows an error.    ... View more

Here is the link to the twitter thread discussing the issue: https://twitter.com/PBIQueryous/status/1600077293220945922?s=20&t=H8n2wFpJNzq2RzL1yvcSRg   Data View allows us the filter the table. Once a column is filtered, other columns can also be filtered showing the remaining available values.   However, when a combination of Filter and Sort (ascending/descending), it causes the other columns filter selection to corrupt, and instead of showing unique values in the filter selection, it shows multiple values. The issue is particularly apparent when using Date Filters (is on or before, is after, is between etc). ... View more

Why, oh why?? With the May 2020 release the SQL Statement box is squished down to 5 lines visible. It was fine before, this is terrible and very hard to use. I can't express how much this will make my job harder especially when I reviewing someone elses report and investigating their SQL code. Also when I try to make a minor change 35 lines down in a 200 line query. You know what I mean.   Will you revert back to the size it was since the beginning or better yet make it so we can expand the box to see more?   Thank you.   ... View more