Good day,   My organization is currently facing an issue with the latest April Update.   The report is located in my workspace and shared with users who are all Premium per user. The users can access the report fine when using the web browser. The only fix I have found so far is to roll back to a previous version of desktop. Unforunately, this prevents the users from making full use of the latest feautres of the software.   Has any one else encountered this issue?   I've tried logging a support ticket with Microsoft but I get this error message when I visit the URL: Power Platform admin center (microsoft.com)   The version of Power BI in use is Version: 2.128.1177.0 64-bit (April 2024) The only fix that has worked thus far was to roll back to a previous version for another user (I will have to get that version number later).   All reports are stored in my workspace on the Power BI service and users have read, build and share permissions. Older versions of PBI and the web service can access the reports fine, the error message only comes up with the April 2024 version.   As mentioned before I do have a Power BI Premium per user license, but am unable to create a support ticket due to the error that I receive above. ... View more

This has now happened with two different reports, completely different data sources. I have a column with date, and use Power Query to add a Month Name and Month (number) column. Then, I try to sort the month name by the number, but I receive this error message:  I tried so many potential solutions, including checking my data over and over and using a custom or conditional column instead of extracting the month. but saving the report and restarting PBI desktop has been the only functioning solution.  ... View more

Following update to "Version: 2.126.927.0 64-bit (February 2024)" I can now nolonger connect to a particular slq server.   Microsoft SQL: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)   This is not my server and it does not support encryption.  Until now I have been able to turn off encryption and have not had any SQL Certificate Chain errors.   I can still connect with the same settings via SSMS.  I don't think I can try things like trustcertificate in the connection string with PowerBI.   Has anyone a solution to this or any reports that this is a bug to be addressed would be much appreciated.   Thanks   Craig     ... View more

Hi,   I have one calendar table (french). 12 month : Janvier, Février... Décembre  An integer column [1..12] : 12 values janvier = 1 février = 2... etc. All was working fine and I never had any "duplicate value ..." error message when trying to Sort a column by another one. Version :  2.128.952.0 64-bit (avril 2024)   Regards, Denis ... View more

It is Wed 21 Feb 2024, I am struggling to open and create Data Pipeline or open and create Notebook in a Fabric Trial Capacity and our P1 Capacity.  Is this a known issue?   ... View more

Hi,   I've noticed a very odd thing whilst refreshing my data in Power BI Desktop. Some background info: - We have a connection to our data platform, a Databricks SQL data warehouse and are using import mode for our semantic model. - The tables in Databricks consists of fact and dimensions, all tables have business keys (text values) and ids (integers) - The ids might change in the facts and dimensions, this is because of how we process the data. The business keys will stay the same. But of course, if the ids change, they are changed both in the fact and dim so the corresponding records can still be linked to each other. - We use the ids to create relationships as these ids take up less space than the bks.   We noticed the following: - We refresh the data in the data platform (and therefore the ids change and the bks stay the same) - We hit the refresh button in Power BI Desktop - All data gets refreshed succesfully (it says..) - We notice that the ids in the fact table do NOT correspond with the ids in the dimension table, whilst the data in the platform shows the correct matching ids for both dims and facts. - We refresh the specific fact table with the wrong id again in Power BI Desktop, and now it shows the correct id.... so it seems like the full refresh isn't doing what it should be doing?   What's going on here? 😅   ... View more

We are using GIT integration TMDL files in Power BI Service. This week our semantic models started to receive changes in Service. When change is committed two files are changed, model.tmdl and culture/en-US.tmdl. culture en-US text changes to cultureInfo en-US. Problem with this is that latest version on Power BI Desktop (2.128.1177.0 (24.04) (x64)) does not recognize this new metadata change.   Here is the error we receive when we try to open .pbip file with Power BI Desktop: TMDL Format Error: Parsing error type - UnsupportedObjectType Detailed error - Unsupported object type - cultureInfo is not a supported property in the current context! Document - './model' Line Number - 36 Line - 'ref cultureInfo en-US'   We can undo changes in Power BI Service or modify cultureInfo -> culture to go around this issue. ... View more

Hello    After the March 2024 update a Circular Dependency Detected error began to appear in a relationship that seemed to be fine since forever. In fact, the Fabric Service does not issue this error. What's worse, any changes I try to make to the dataset regardless of where the changes are made; this error pops up and completely ignores applying the changes I want to make. Is there a "bug" in the latest Desktop update? Why did this error not exist prior to this? I need help, I can't seem to shake off this issue and I have several updates I need to make to this dataset which cannot be made in the Fabric service. ... View more

I am having an issue where if I have a calculated table (first 5 columns calculated table) and then calculated columns added to the end (last 4 columns of the table) when I left click from a calculated column back to the calculated table in data view the system buffers and it overwrites the formula bar with the calculated column formula and creates a new table with the formula that was in the calc column feild. I am not sure why it is doing this because I am just clicking to navigate.    I have a video of this issue I could not upload but is a new issue.     ... View more

All the relationship lines are missing from the model view.  All graphical manipulation of the model fails.  Adding new tables/datasources fail.  A new version needs to be released immediately.  It appears that version 2.119.666.0 doesn't have that problem.  These versions are so new that they're not even documented on the Microsoft site.  😞   ... View more

Hello, Since the february release we have multiple users complaining about a datasource error, screenshot below.  Is this a know issue?   ... View more

Hi, I've encountered a bug that whenever I switch between calculated columns (by pressing their name in table view) it completely overwrites the DAX of the column selected with whatever column I was looking at before. A workaround is to switch between columns my selecting them on the data tab (on the right side) instead. I am unable to record this because of controls on my device.   Thanks, Jerzy ... View more

I am currently having this issue.  Does anyone get this error?     ... View more

Unable to create new dataflows in GCC tenant. When you click to Add table then choose any connector, I instantly get the following message.  ... View more

I receive a renaming request every time a calculated column is edited in the Table view. The message indicated that the name is already in use and another name is required:   Ignoring the request does not break the reports, but it is just annoying to see it repeatedly. ... View more

Dear all,   I have suddenly experienced an issue where whenever i clicked on one of 'Calculated Column A' in Table View , and then click another 'Any Column B', my Table will be randomly renamed into the name of Column B and mess up all my data.    If the column name is already used, it prompts an error message prevent my table to be renamed into the column name.    Please find below sample for the error reproduced.    Would appreciate for help as it keeps messing up all data and unable to undo without restarting Power BI Desktop, this issue is really troublesome as you cannot undo the action and all your data will be error even you rename back to correct column.   Thanks in advance!     ... View more

I am reporting another serious bug with March release:  - under "Table view" > right-click > copy table function no longer works, it doesn't copy anything   This is the 2nd bug I found with March release within 1 day, what's QA?  ------------------ Version: 2.127.1080.0 64-bit (March 2024)   ... View more

https://community.fabric.microsoft.com/t5/Service/Power-BI-Service-Dataset-Refresh-Error-Expression-Error-The/m-p/3378733   There is already an ongoing thread in the Community PBI Service forum but I thought it could do with being here too for visibility.   Symptoms:  SharePoint Online lists meeting certain criteria fail to refresh with error Expression.Error: The column '<ccon>ID' of the table wasn't found.. ID. </ccon>. The exception was raised by the IDbCommand interface. Table: [Table Name]   Refresh in Power BI service was working fine for these reports across multiple tenants until reports running from 9/8/2023 midnight UTC onwards.   Some possible trigger conditions noted in above thread:   V2 connector and empty SharePoint list created before a certain date on SharePoint Teamsite (classic w/o Team)  V2 connector and ID column for the list isn't being imported to the data model (i.e. query filters it out)   I found in the second circumstance as long as the list has data in it you can get it to refresh by including the ID column in Power Query instead of removing it, but empty lists just fail completely.   @sulleyinoz mentioned there is a ticket open with MS about their issues with blank lists, is there any acknowledgement this is a wider issue and is being worked on?   Thanks   Mark   ... View more

I'd like to report an issue or bug I'm having with Power BI Desktop. For about a month now, calculated columns come back with the error "there is already a column with the name xzy". That was not actually the case, but I thought nothing of it because I could continue working.   Today though, a column formula moved or 'jumped' to another calculated column, replacing its formula. This is on a calculated table. Then, when selecting another calculated table, the formula moved / jumped to that table.   I'm needing to close without saving, which is frustrating.  Please help to get this resolved.   I copied the details of the error, below.   Feedback Type: Frown (Error) Timestamp: 2024-03-01T10:01:27.8685454Z Local Time: 2024-03-01T12:01:27.8685454+02:00 Session ID: 599bee6b-7568-4353-bd93-9adb4ec641e7 Release: February 2024 Product Version: 2.126.927.0 (24.02) (x64) Stack Trace: Microsoft.PowerBI.Modeler.ModelerException at Microsoft.PowerBI.Modeling.Engine.DataModel.Utilities.DataModelExtensions.ThrowIfNotFound[T](T foundItem, String name, String parentName, String grandparentName) at Microsoft.PowerBI.Modeling.Engine.DataModel.Utilities.DataModelExtensions.GetExpected[T](INamedMetadataObjectCollection`1 list, String name, String schemaName, String parentName, String grandparentName) at Microsoft.PowerBI.Modeling.Engine.DataModel.Utilities.DataModelExtensions.FindModelItem(IDataModel model, ObjectType objectType, String schemaName, String tableName, String itemName, String hierarchyLevelName, Boolean expected) at Microsoft.PowerBI.Modeling.Engine.SchemaChangeRoutingVisitor.Visit(DeleteItemSchemaChange schemaChange) at System.Collections.Generic.List`1.ForEach(Action`1 action) at Microsoft.PowerBI.Modeling.Engine.SchemaChangeRoutingVisitor.Route(ModelChange modelChange) at Microsoft.PowerBI.Modeling.Engine.ModelingEngine.<RouteModelChangeAsync>d__15.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.Modeling.Hosting.DesktopModelingHost.<>c__DisplayClass37_0.<<RouteToLocalModel>b__0>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.Report.<>c__DisplayClass74_0.<<SynchronizeLooselyWithQueriesAsync>b__0>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.Report.<SynchronizeLooselyWithQueriesAsync>d__73`1.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.Modeling.Hosting.DesktopModelingHost.<RouteToLocalModel>d__37.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.Modeling.ModelAuthoringRoutingService.<>c__DisplayClass19_0.<<RouteToLocalModel>b__0>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.Modeling.ModelAuthoringRoutingService.<RouteToLocalModel>d__19.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.IntellisenseHostService.<>c__DisplayClass66_0.<<ApplyModelChangeCore>b__0>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.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__1.MoveNext() PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.126.927.0","ModuleName":"Microsoft.PowerBI.Modeling.Engine.dll","Component":"Microsoft.PowerBI.Modeling.Engine.DataModel.Utilities.DataModelExtensions","Error":"Microsoft.PowerBI.Modeler.ModelerException - ColumnDoesntExistInModel","MethodDef":"ThrowIfNotFound","ErrorOffset":"443","ErrorCode":""} OS Version: Microsoft Windows NT 10.0.22631.0 (x64 en-GB) CLR Version: 4.8 or later [Release Number = 533320] Peak Virtual Memory: 71.4 GB Private Memory: 966 MB Peak Working Set: 1.15 GB IE Version: 11.1.22621.0 User ID: 231f20b9-bdb3-43f4-ad76-101e851a4e8a Workbook Package Info: 1* - en-GB, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False. Telemetry Enabled: True Model Default Mode: Import Model Version: PowerBI_V3 Enabled Preview Features: PBI_sparklines PBI_scorecardVisual PBI_NlToDax PBI_fieldParametersSuperSwitch PBI_backstageUI PBI_setLabelOnExportPdf PBI_dynamicFormatString PBI_oneDriveSave PBI_oneDriveShare PBI_newCard PBI_buttonSlicerAuthoring PBI_generateMeasureDescriptionsButton Disabled Preview Features: PBI_shapeMapVisualEnabled PBI_SpanishLinguisticsEnabled PBI_qnaLiveConnect PBI_b2bExternalDatasetSharing PBI_enhancedTooltips PBI_angularRls PBI_onObject PBI_useModernPublishDialogs PBI_gitIntegration PBI_tmdlInDataset PBI_EimLessElevatedUser PBI_modelExplorer PBI_daxQueryView PBI_aiNarrativesVisual PBI_qnaImproveLsdlCopilot PBI_visualCalculationsAuthoring Disabled DirectQuery Options: TreatHanaAsRelationalSource Cloud: GlobalCloud DPI Scale: 100% Supported Services: Power BI ... View more