Issues

timalbers · ‎02-19-2024

Good news first: It looks like with the February update, this issue was resolved: New card visual bug ... But sadly now there's a new issue with the visual, this time it's the custom formatting of the Reference Labels. Some operations are causing the whole visual to throw the above error "Repeated indices found in GroupBy or Projections". In my case it happens every time I am adding a custom format rule for Reference Label > Detail > Font Color / Color. This is only the case when the same field is used for the formatting rule like as for the data of the detail field itself.

adnyk · ‎11-23-2023

Hi, I posted about this in the forums and seems like more than me are seeing the same issu. The new button slicer keeps resetting to the left most button even though it is saved in another state. As an example I have a report with year filter (year from date table) and timeperiod filter (calculation group), I have it saved as 2023 and YTD but when closing and reopening the report it is set to 2022 and MTD. Same behavior in service. Br Adrian

sebadb9 · ‎05-12-2023

Publishing a power BI desktop file to power BI service, in an attempt to overwrite an existing dataset/report doesn't work whenever you might have switched on the toggle of OneDrive refresh. Turning of the toggle doesn't solve the issue. Reported issues, claimed to be resolved by the product team, continue to cause big issues: Cannot disable OneDrive refresh - Microsoft Power BI Community. This result in a status where it is impossible to adjust a dataset/report. (Even though Microsoft is pushing towards full parity of power BI desktop into the cloud, currently we can't fully work in the browser as not all functionality of power BI desktop has been added in the browser.) The only unacceptable workaround appears to delete your dataset/report in the service and publish a new one. Let me elaborate some of the consequences of deleting the dataset/report: need to re-pin visuals to dashboards RLS/OLS needs to be reconfigured related reports/datasets are broken (hybrid reports, reports on the same datasets, etc.) all reports directly or indirectly related to this dataset that are pinned in Microsoft Teams are broken Deep Links (with filters in the URL) to every report related directly/indirectly to this dataset are broken all people's bookmarks to related reports/datasets are broken integrations of power BI reports in PowerApps are broken integration in Excel Custom data types are broken (featured tables) integration of power BI in Power Automate are broken, automation of processes thus are broken all external systems sending API requests to that dataset are broken metrics are broken report usage metrics are gone power BI comments are gone integration with Synapse Analytics is broken e-mail subscriptions on the reports are broken alerts on Card/Gauge visual are broken everything else I forgot about is broken! Let it be very clear: the impact of deleting just a simple report/dataset can be huge. Huge work in fixing stuff, huge in disruption for the business with a many power BI users. Currently we're not updating our power BI reports and datasets, which also is impacting our business operations! All power BI users are facing this issue and many are complaining about it: https://community.powerbi.com/t5/Service/Couldn-t-publish-to-power-BI-already-exists-and-is-set-up-w... https://community.powerbi.com/t5/Developer/Publish-of-update-fails-with-error-about-cloud-refresh/m-... https://community.powerbi.com/t5/Service/Cannot-quot-overwrite-quot-You-already-have-a-dataset-named... https://community.powerbi.com/t5/Developer/Publish-of-update-fails-with-error-about-cloud-refresh/m-... The product team should fix this and have admins the possibility of disabling OneDrive refresh all together for the entire tenant. Simply moving one .pbix file in SharePoint (seeming unharmful) can trigger unrepairable/irreversible consequences. I have raised a support ticket for this issue, but power BI support has been unable to solve this open ticket for more than 5 days. Please vote, and raise awareness of this BUG. This must be fixed!

KTyler · ‎03-29-2024

We're on Pro licenses rn. The subscriptions are sending two emails: one with an error, and one with the correct report page, at the same time. The first has the error below: There was an error with your subscription "CORE Metrics by Program" but we still delivered it You are receiving this email because there was an error with a subscription to Power BI Report "CORE Metrics" created by you. EmailSubscriptionScreenshotVisualError Visual errors were encountered while rendering the artifact. This subscription was delivered to recipients, however one or more visuals may be missing. Can't display this visual. : This visual contains one or more filters with deleted columns, type mismatches, or other breaking modeling changes. You can check the latest state of the report by clicking in the button below. Your next subscription is scheduled for March 30, 2024 12:00 UTC. Technical Information Activity Id: 88af6852-0a6c-442d-906f-389e19eb2192 Request Id: 369b9ad9-3a38-4656-8836-af1e3f924b18 Cluster Name: WABI-US-NORTH-CENTRAL-redirect.analysis.windows.net Subscription Start Time: March 28, 2024 0:00 UTC Subscription End Time: March 28, 2025 0:00 UTC I'm a Power BI Admin, and it's doing it for me as well. I've tried multiple browsers, and from my test account, with the same result. The link in the error email hangs. The link in the correct email works fine. I literally changed nothing in the settings when I set up the subscription and that made no difference either.

D_M · ‎04-11-2024

Hello, Having upgraded to the latest release (version: 2.128.751.0 at the time of writing) it's been observed that, by default, the 'Detail' formatting options for the Data labels pane is currently missing 'Bold', 'Italic' and 'Underline' as options in PBI desktop, as shown below: Also, just to confirm from my testing, this is the case even if using a default Microsoft theme (as well as a standard custom theme). However, if a 'detailBold' option is invoked in a custom PBI theme file explicitly, this then works in the relevant PBI file in PBI desktop, and also displays in the visual, like so: Clearly, this is not expected behaviour, so would suggest these formatting options to be made available in the formatting pane as per other similar text outputs, thanks!

Greg_Deckler · ‎04-09-2024

Following instructions in this article: Build Scatter Plots in Power BI and Automatically Find Clusters (mssqltips.com) Can't find automatically find clusters in March 2024 version. Also April 2024 version. Also this: Why is "automatically find clusters" unavailable? ... - Microsoft Fabric Community

is001902 · ‎03-18-2024

I am accessing one SQL Server DB using direct query. This report works fine for varying lengths of time but then stops working with the error AN EXCEPTIONS OCCURRED DUE TO AN ON PREMISE SERVICE ISSUE. We checked if there was an SQL activity (backups etc.) going on to interrupt it but none. We run a subscription report to track when it fails and there is no consistency. When we refresh the report it usually starts working again, sometime we have to go and refresh the connections or on premise gateway. Any ideas?

VadimK · ‎04-04-2024

Cannot disable OneDrive refresh - Microsoft Fabric Community

N24PBI · ‎03-01-2024

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

agusmba · ‎11-16-2023

I started testing the new button slicer, and while it looks very promising, found some problems that prevent me from using it: [BUG/IMPROVEMENT?] Fill color and accent bar conditional rules do not get row context so they are unusable unless you want all buttons the same color. Note that font color does get row context and thus works on a per-button basis ✔. [BUG] Label font and size is fixed and the format options do not work [IMPROVEMENT] The 10 row limit. Why not allow us to set the button height instead? [BUG] Text wrap for the main text not working (at least on long words) [BUG] If I try to use gradient formatting rules, the slicer breaks and the formatting pane dissapears. Only workaround is CTRL+Z. Any hope of getting fixes at least for the two first items before next month? Thank you! (Edited to add BUG/IMPROVEMENT indicators to the original list of issues)

dharland · ‎01-26-2024

We are unable to add dynamic content to text boxes using the latest version of PBI Desktop (Version: 2.124.1805.0 64-bit (December 2023)). And for existing reports developed in the past that already have dynamic content in text boxes, developers are unable to edit/view the dynamic value being used in those reports as well.

JaneydeJong · ‎12-18-2023

Hi, I created a new card visual in the Power BI desktop report and then published the report to Power BI service. In Power BI service the card is showing differently (reference labels have more spacing in between) compared to in Power BI desktop. Is this a bug? New card visual in Power BI desktop: New card visual in Power BI service: Thanks in advance for any help!

Cristian_Alzate · ‎03-27-2024

I’ve created an account specifically to address an issue that, to my knowledge, has not yet been reported. The 2024 versions of Power BI Desktop have introduced a significant annoyance when working in Table View. My primary concern is the inability to horizontally scroll through columns using arrow keys once a DAX Calculated column is selected. Instead of scrolling, the interface randomly selects and enters the DAX formula bar, preventing further horizontal navigation. This issue also occurs when selecting a DAX Calculated column directly with the cursor, I also have some issues with the message errors telling me there is a duplicate column and the copying of a column Dax code in another Calculated column. Due to these problems, I’ve reverted to the latest 2023 version of Power BI Desktop, where this issue is absent. The ability to smoothly scroll through columns is crucial for verifying the correctness of DAX code in tables with numerous columns. Unfortunately, the 2024 versions have made it impossible to work efficiently due to this and other issues. I’m hoping there might be an overlooked option to restore the traditional arrow key scrolling functionality. If not, I hope the development team addresses this bug and reinstate the previous, user-friendly behavior. Thanks.

igorcastrp · ‎03-27-2024

Feedback Type: Frown (Error) Error Message: Container unexpectedly exited. Exit code: 0xC0000005. PID: 24336 Stack Trace: Microsoft.Mashup.Host.Document.SerializedException at Microsoft.Mashup.Host.Document.Analysis.PackageDocumentAnalysisInfo.PackagePartitionAnalysisInfo.SetPreviewValue(EvaluationResult2`1 result, Func`1 getStaleSince, Func`1 getSampled) Stack Trace Message: Container unexpectedly exited. Exit code: 0xC0000005. PID: 24336 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.Client.UI.Shared.UnexpectedExceptionHandler.HandleException(Exception e) at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action) 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 System.Windows.Forms.Form.ShowDialog(IWin32Window owner) at Microsoft.Mashup.Client.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction) 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) at Microsoft.PowerBI.Client.Program.RunApplication(String[] args) at Microsoft.PowerBI.Client.Program.Main(String[] args) PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.127.1080.0","ModuleName":"","Component":"Microsoft.Mashup.Host.Document.Analysis.PackageDocumentAnalysisInfo.PackagePartitionAnalysisInfo","Error":"Microsoft.Mashup.Host.Document.SerializedException - Microsoft.Mashup.Host.Document.Evaluation.ErrorEvaluationResult","MethodDef":"SetPreviewValue","ErrorOffset":"","ErrorCode":""} Snapshot Trace Logs: C:\Users\ibrambila\AppData\Local\Microsoft\Power BI Desktop\FrownSnapShot2171c073-d8bf-488e-ae27-066094683331.zip Model Default Mode: Import Model Version: PowerBI_V3 Performance Trace Logs: C:\Users\ibrambila\AppData\Local\Microsoft\Power BI Desktop\PerformanceTraces.zip Enabled Preview Features: PBI_sparklines PBI_scorecardVisual PBI_NlToDax PBI_fieldParametersSuperSwitch PBI_angularRls PBI_backstageUI PBI_setLabelOnExportPdf PBI_dynamicFormatString PBI_oneDriveSave PBI_oneDriveShare PBI_gitIntegration PBI_newCard PBI_buttonSlicerAuthoring PBI_mobileAutoReportLayout PBI_daxQueryView PBI_daxInlineCopilot PBI_aiNarrativesVisual PBI_generateMeasureDescriptionsButton Disabled Preview Features: PBI_shapeMapVisualEnabled PBI_SpanishLinguisticsEnabled PBI_qnaLiveConnect PBI_b2bExternalDatasetSharing PBI_enhancedTooltips PBI_onObject PBI_useModernPublishDialogs PBI_tmdlInDataset PBI_EimLessElevatedUser PBI_modelExplorer PBI_qnaImproveLsdlCopilot PBI_visualCalculationsAuthoring Disabled DirectQuery Options: TreatHanaAsRelationalSource Cloud: GlobalCloud PowerBINonFatalError_ErrorDescription: Microsoft.Mashup.Host.Document.Evaluation.ErrorEvaluationResult PowerBIUserFeedbackServices_IsReported: True Formulas: section Section1; shared solutions = let Source = Excel.Workbook(Web.Contents("https://spectronservices.sharepoint.com/sites/CounterpartyRiskAnnualReviews/Shared%20Documents/Solutions/Solutions%20Credit%20Facility%20Annual%20Reviews%20Mar24.xlsx"), null, true), solutions_Table = Source{[Item="solutions",Kind="Table"]}[Data], #"Changed Type" = Table.TransformColumnTypes(solutions_Table,{{"Days Overdue", Int64.Type}, {"Account No.", type text}, {"LE Name", type text}, {"Firm", type text}, {"Office", type text}, {"Sales Group", type text}, {"Sales Desk", type text}, {"Initial CL", Currency.Type}, {"Variation CL", Currency.Type}, {"Total CL", Currency.Type}, {"Last Review Date", type text}, {"Next Review Date", type text}, {"Column1", type date}, {"2023 Total Income", Currency.Type}, {"Return 2023", Percentage.Type}, {"2024 Total Income", Currency.Type}, {"Annualised Income 2024", Currency.Type}, {"Annualised Return 2024", Percentage.Type}, {"Analyst", type text}, {"Comment / Update", type any}, {"Financials Recived (Y/N)", type text}}), #"Renamed Columns" = Table.RenameColumns(#"Changed Type",{{"LE Name", "Client Name"}, {"Variation CL", "VM Line"}}) in #"Renamed Columns";

o59393 · ‎09-17-2023

Dear MSFT Recently I've noticed that calculated column and dax measures s are going blank or unchanged after writing code. Can you review this potential bug from September version? Thanks.

agusmba · ‎11-17-2023

I was testing the new Reference Labels for the new card visual, and while it looks great in general, I found a bothersome issue: Number formatting options (decimal places) on reference lavel values are ignored both from the metric itself and even if we try to force them in the formatting options of the reference label: In the same place, Display units for decimal values are also ignored (they seem to work with integer metrics) Thank you for the new improvements! Agustín

BRNS · ‎01-12-2023

Data source error: {"error":{"code":"Premium_ASWL_Error","pbi.error":{"code":"Premium_ASWL_Error","parameters":{},"details":[{"code":"Premium_ASWL_Error_Details_Label","detail":{"type":1,"value":"Refresh is not supported for datasets with a calculated table or calculated column that depends on a table which references Analysis Services using DirectQuery."}}],"exceptionCulprit":1}}} Cluster URI: WABI-SOUTH-CENTRAL-US-redirect.analysis.windows.net Activity ID: 954fd614-029c-451f-ab77-aac648a599e3 Request ID: 02fb20e5-43e4-376e-ccc8-b07440f335f0 Time: 2023-01-12 10:31:06Z

artur_nls · ‎02-16-2024

I have a template app workspace, that is being used to install app copies for my clients. For some time there is a possiblity to upgrade Temaplate App to new version (old one will be not supported from 1th of May). I have tried to use "Upgrade now" option for several times. And each time it results with "Upgrading" communicate that stays for long time. Finnaly the app will be never updated. The problem is that end clients are able to upgrade apps that has been installed based on my template app. And once they do this, it is not possible to install new version on app on their side.

cristianml · ‎08-11-2022

Hello, With August'22 version I have an issue when I try to apply changes or discard them. Seems not working neither:

Idrissshatila · ‎02-14-2024

Something has chnaged since yesterday. All was working well yesterday and no changes have been made to the file or data. We have an Azure reference layer on our maps as below, outline black This has been working fine, we have published to the Power BI service and the map can be used and seen by our end users, new users shown this yesterday and was working as expected. Today I have gone to look at this and the reference layer can not be seen on the Power BI service, as below I can see the layer is still in the visual under format on the service, I have checked the desktop PBIX file and the layer is there and is visible when looking at it in desktop, but as soon as it is published to the service the layer is no longer visible. Anyone know what is happening?

Share your ideas and vote for future features

New card visual: Ongoing issues (Repeated indices found in GroupBy or Projections)

Slicer (new) resetting default

Publishing power BI broken when OneDrive refresh is toggled on

Power BI Subscription sending two emails

100% stacked area chart - Detail label formatting options 'missing'

March 2024 Automatically Find Clusters unavailable?

powerbi an exception occurred due to an on premise service issue

Cannot disable OneDrive refresh

Formulas jumping to different calculated columns and tables

New button slicer issues

ISSUE: Unable to Add Dynamic Content to Text Boxes

New card visual not showing the same in Power BI service compared to Power BI desktop

Issues 2024 Power BI Desktop Versions - Table View Broken Horizontal Scroll with arrow keys

Container unexpectedly exited. Exit code: 0xC0000005. PID: 27240

Bug with September 2023 Version - DAX & CALCULATED COLUMNS NOT WORKING

New reference labels issues (november 2023)

SCHEDULED REFRESH ERROR WHEN USING DATASET CONNECTION

Issue with Template App Upgrade

Apply changes not working

Azure reference layer disappears when published to Power BI service?

Helpful resources

Multiple Refresh schedules in single report

R and Python - Standard Gateway

PowerBi consistently crashes when chosing Quick Me...

Bug in quick filter in PBI Desktop

Something went wrong endless loop