When I try to update a content pack, (in app.powerbi.com, cog -> View Content Pack -> Edit (an existing content pack) -> click UPDATE button), I see an error message that begins "The following groups have failed validation..." This happens with all of my content packs, even when there are only 5 members of the workspace that the content pack is publishing to, and all members are definitely still current staff members. Any ideas?
I have developed some reports in Power BI Desktop which include the martix visual. All visuals are displaying correctly when viewing the reports in Power BI Desktop, but when I publish and try to view report in the Server, the Matrix is not displaying any information. All other visuals seem to be working fine in the server, just not the matrix.
Estou com uma situação posterior :
Tenho uma fonte de dados ODBC do banco Firebird, quando requisito uma atualização dos dados no Power BI desktop, o mesmo roda perfeitamente, inclusive consigo efetuar uma publicação de relatório, no entanto, criar uma fonte de dados (servidor de relatório) dentro do meu gateway resultados nesse erro:
Consigo a ajuda de vocês?
I have a set of reports that use an MDX SSAS cube data source with defined hierarchies. The reports include multiple matrix visuals, some table visuals and a few other visuals. The reports function correctly in Power BI Desktop; however, when the report is published to the service the matrix visuals fail to render. The visual can be switched to a table and it will display results.
Could not find any previous posted issue for this but in the forum multiple people have reported this issue and I'm also one of those that rely on this feature. link to community
Please take a look at this!
I want to use the Selection pane to manage my visuals on a page. However, I use a lot of visuals (especially text boxes), and some of them at the bottom are not accessible via the Selection pane as there is no way to scroll down.
Can you please fix this?
I've changed some calculated fields in my model, so some of my tiles broke with Error:
"Unrecognized fields in this visual". But that's ok, I was expecting this.
I want to replace them with new tiles from the report.
But now I CANOT DELETE those tiles!!! No option for delete.
Just "Go to report" or "Export".
Please Help, my dashboard is full of these!
The stacked column charts stopped working in existing dashboards and reports. all other reports, grids etc seem to be working fine. Datasource is SSAS MD cube. I have confirmed that there is data at the intersection in the cube that is included in the reports. Report was created from dataset online and not from desktop power bi.
The Attribute Slicers works fine in PowerBI Desktop, no warnings, published w/o issue, but the Attribute Slicers do NOT function in the published reports. The slicers worked fine w/previous publications.
I am having issues installing the Power BI Gateway (powerbigatewayinstaller.exe). It seems the installer doesn't initiate/run.
I think there might be an issue with the application itself, since I am having the same issues on three different computers.
I have tried:
- Run as administrator
- Start the installer from Run
- Check the Task Manager if the process is actually running, with no trace of the gateway.
So I figured I check the Event viewer, and found a .net runtime error with event id 1026. There's also an application error, but I presume this is down to the .net runtime error. The information from the event viewer is as follows:
Tillämpningsprogram: PowerBIGatewayInstaller.exe Framework-version: v4.0.30319 Beskrivning: Processen avslutades på grund av ett ohanterat undantag. Undantagsinformation: System.IO.FileNotFoundException vid Microsoft.DataProxy.PowerBIInstallDownloader.LandingPageViewModel..ctor(Microsoft.DataProxy.PowerBIInstallDownloader.MainViewModel) vid Microsoft.DataProxy.PowerBIInstallDownloader.MainViewModel..ctor() vid Microsoft.DataProxy.PowerBIInstallDownloader.MainWindow..ctor() Undantagsinformation: System.Windows.Markup.XamlParseException vid System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri) vid System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri) vid System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri) vid System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean) vid System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext) vid System.Windows.Application.DoStartup() vid System.Windows.Application.<.ctor>b__1_0(System.Object) vid System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) vid System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) vid System.Windows.Threading.DispatcherOperation.InvokeImpl() vid System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) vid System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) vid System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) vid MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) vid System.Windows.Threading.DispatcherOperation.Invoke() vid System.Windows.Threading.Dispatcher.ProcessQueue() vid System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) vid MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) vid MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) vid System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) vid System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) vid System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) vid MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) vid MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) vid System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) vid System.Windows.Application.RunDispatcher(System.Object) vid System.Windows.Application.RunInternal(System.Windows.Window) vid Microsoft.DataProxy.PowerBIInstallDownloader.App.Main()
We have a report in PBI service containing lots of matrixes. The report uses SSAS live connection as a source
They have fields in the rows, no fields in the colums and ofcourse some values.
If I download the report and open it in PBI desktop (Version: 2.51.4885.701 64-bit (October 2017)) the report works fine.
They worked fine last thursday. Today I get a complaint of the enduser that the report doesn't show data anymore!
I only get the matrix working if I add a field of the columns.
Has there been an update on the matrix visual? Please fix!
we defined a report with Power BI Desktop with a Live connection toa tabular model (SSAS 2016).
When we move it from development to pre-production we usually change the SSAS tabular connection using edit queries.
We try to do this with the latest version of Power BI Desktop (Nov 17)Â but all the visuals used appear signed with an X (no object found).Â The same works fine with the previous versions.
We suppose this is a bug.
Bug in PowerBI Desktop Version: 2.51.4885.701 64-bit (October 2017)
When you single click a query in the "Queries" selector on the left hand side, it thinks you want to move the query up or down to re-order.
This did not happen in the previous version.
In new release verson of Power BI desltop Version: 2.51.4885.543 64-bit (October 2017). There is no Line style (a Shape feature) of Line chart which is added in Aug 2017 release. Could you please kindly check it?
This issue has been occuring for the past week, only for one specific report. Publishing from the desktop client still works normally and is being used as a manual refresh.
Details Type Start End Status Message
|On demand||21/09/2017 4:40:43 PM||21/09/2017 4:40:48 PM||Failed||The gateway operation has been cancelled explicitly by the user or from a timeout.|
When I use a filter by selecting a group in a visual (e.g. a funnel chart) and then select an element from a connected table the funnel selection ist lost. This just happens when the table with the filter results has more rows than the visual can show (scroll bar appears). We could not determine how long the table must be.
I can provide a sample to simulate the issue.
Help/bug fix is highly appreciated because of customer awareness.
I'm getting the following error when using a variable and logical operator in a column (using direct query).
"An unexpected error occurred (file 'tmmdmodeltm.cpp', line 5980, function 'MDModelTM::GenBaseTableQuery')."
createdChanged = var x = DATEDIFF(xxxxxx[createdDate];xxxxxx[changedDate];DAY) return if(x>1000;0;x)
This formula works fine in Import mode. Tried several scenarios, but it seems the error is thrown when the variable is used as part of the logical test (e.g. this works: createdChanged = var x = DATEDIFF(xxxxxx[createdDate];xxxxxx[changedDate];DAY) return if(1=1;x;1)
I have added text into the tooltip section on charts I've created to act as commentary for each chart. The text appears as expected when viewing the reports on the Desktop app. When viewing the published report online, the text seems to have a line break every other line. Screenshots attached. Has anyone else experienced this issue?
Word wrap is no longer working as intended in tooltips.
For longer strings, a line gets wrapped twice, first at the correct location and then at location that's far too early to be of any use. This results in a staggered texts as in the screen shot below.
This is issues is present in both PBI Desktop and the PBI Service. It affects both build-in visualizations and custom visualizations.