Issues - Page 97

Anonymous · ‎01-17-2022

When bringing in a new table, I am having trouble applying data to the file through direct query methods. I get an error message "Failed to save modifications to the server. Error returned: 'Unable to convert an M query in table 'PRTH' into a native source query.'." I have tried 2 ways of getting the table, with the recent data source tab in transform data, and getting the table , as well as source > settings > then inserting SQL. I have looked at other solutions that say to "simplify" the steps to bring the table in, and as you can see in one file I only have one step. When I load the needed table on a blank power BI file, it works fine. We have 7 tables, 4 through direct query and 3 through import including this table. Thanks.

npnigro · ‎01-14-2022

I can connect to the database just fine in Excel, Power BI Desktop, and SQL Server Management Studio. For Power BI dataflows (both dedicated and shared capacities), it's been hanging repeatedly for more than 2-3 hours.

paul_sanders · ‎01-14-2022

Created a new dataflow, and connected to Salesforce (Objects). It took 9.5 minutes to list the set of Salesforce objects. Then upon selecting an object, the preview of the data still hadnt appeared after 5 minutes. The same operation in the Power BI Desktop took about 2 seconds to show the list of tables, then another 2s to show the preview of the selected table.

alexgallegos · ‎01-13-2022

I have a few users who recently started with PowerBI Desktop (I am not a PowerBI user myself) who cannot get any data to load. I logged onto their machines myself and uninstalled the software and reinstalled it, making sure to install the latest version - 2.100.1182.0 64-bit (December 2021). Opening a new PowerBI session and trying to load even an extremely simple CSV file saved locally to the machine allows you to preview the records in the CSV without issue: After starting the load process, though, the program hangs. Over on the right in the area I highlighted, it appears that it's trying to identify the fields in the file, which seems strange to me since it did so successfully on the previous page in order to preview the data. This process never ever completes, even if left overnight. To allow users to run jobs without tying up their primary workstations this is installed on virtualized workstations. We have PowerBI running on other VMs successfully but these newest ones will not work. The VMs were all created from the same template and there are no functional differences between them apart from IP Address and Hostname. The VMs are running Server 2012 R2. I have already cleared the cache as well as uninstalling the software and installing the latest version. So far, I have not found any potential causes for this issue to try and would appreciate any feedback or advice.

Viacheslav · ‎01-12-2022

I've recently faced an issue of concurrent dataset refresh. The point is - according to the workspace settings there's no Scheduled refreshes set that time and there's no On-demand refreshes being run the same time. - Gateway service restart gave no results. - Same report works as expected on other spaces of deployment pipeline (QAS/PRD), dataset and report are the same. - Other reports on the same space are refreshed as expected both modes (on-demand/scheduled refresh) Error details: "Data source error: The operation was throttled by Power BI Premium because there were too many datasets being processed concurrently. Please try again later." Cluster URI: WABI-UK-SOUTH-B-PRIMARY-redirect.analysis.windows.net Activity ID: cc0b95a2-317f-4e00-9fb5-2d916edac0ce Request ID: 06248b6f-19c1-242d-115e-974263ae67e0 Time: 2022-01-13 05:45:26Z

fbottazzoli · ‎01-11-2022

Hi all, since some weeks (about a month) I'm experiencing an issue that I believe to be caused by Power BI desktop. During my workday, I always have Power BI Desktop opened in my PC since it is my main occupation. After some hours of work, Power BI Desktop loosed my authentication and, after a few minutes, even Teams, Office and Outlook stops work because they lost authentication. Today the same thing happened to my colleagues, who was not using Power BI Desktop since a while My installed version (updated today): 2.100.1182.0 64-bit (December 2021). We have Power BI Premium licenses, and I have a Power BI PRO license. Francesca

MonicaDizIBH · ‎01-07-2022

En un dataset cambio el origen de datos de una de las tablas y el comportamiento no es el esperado. Los pasos son los siguientes: Inicialmente tengo un dataset donde la tabla de centros tiene las columnas ID_CENTER y DS_CODE_CENTER ocultas. En la pestaña Informe no aparecen y en las pestañas Datos y Modelo aparecen marcadas como ocultas. El origen de datos de Centros es: Tenemos 236 filas: Y vemos, por ejemplo, que en ID_MANAGER y DS_MANAGER hay datos: Cambiamos el origen de datos de Centros: De nuestro nuevo origen de Centros sabemos que hay más filas (312) y que desaparecen algunas columnas, por ejemplo: ID_MANAGER, DS_MANAGER. Tras el cambio podemos comprobar que el número de filas es el esperado: 1) Vemos que las columnas que ya no existen en el nuevo origen no se eliminan del dataset (siguen apareciendo pero sin datos): ¿Por qué siguen apareciendo unas columnas que ya no existen? ¿Hay forma de forzar que estas columnas se eliminen del dataset? ¿Habría que quitarlas de forma manual? Si las quito de forma manual, guardo los cambios y vuelvo a abrir la ventana para elegir columnas, estas dos columnas me siguen apareciendo para poder volver a seleccionarlas: Si, sin haber quitado estas columnas explícitamente, es decir, solo habiendo hecho el cambio de origen de datos, aplicamos cambios y cerramos, como es de esperar, estas columnas me siguen apareciendo en el modelo. Éste no es el comportamiento que esperábamos. ¿Hay forma automática de hacer que si quitamos columnas en origen se quiten de PBI?. 2) Por otra parte, en este Dataset, una vez realizado el cambio de origen, en las pestañas Datos y Modelo me siguen apareciendo las columnas ID_CENTER y DS_CODE_CENTER como no visibles. Sin embargo, si hacemos el mismo cambio de origen de datos de Centros en otro DataSet las columnas ocultas, dejan de ser ocultas. Antes del cambio de origen: Después del cambio de origen: La pregunta es, ¿por qué el comportamiento es distinto con respecto al otro dataset? @nicovillarroel

MonicaDizIBH · ‎01-07-2022

Desde hace un tiempo, en Power BI Services, al hacer clic sobre un dataset no me aparece el listado de informes relacionados a ese dataset. @nicovillarroel

darrenfishell · ‎01-07-2022

I am getting incorrect totals for a calculated column because row-level security filtering is happening after a CALCULATE() expression. I have read it's not ideal design to have RLS applied to the fact table, but I have an OR condition from two different dimensions that need to be applied. From my fact table of transactions, I have foreign keys to both a manager and partner dimension. My RLS rule is roughly: RELATED(MANAGER[Email]) = USERPRINCIPALNAME() || RELATED(PARTNER[Email]) = USERPRINCIPALNAME() I have a third dimension table, Client. I want to aggregate a total realization % for the Current Year only in the client table. I then want to bring this summary calculation into a column in the Client table so that I can create a dimension that can be used in a visual to segment overperforming/underperforming clients. To start, I built a calculation to return the appropriate sums only for the current year, of the form: CALCULATE(SUM(FACT_TABLE[Amount]), DATE_TABLE[YEAR] = DATE_TABLE[CURRENT_YEAR]). But when I bring this calculation into a calculated column in the Client table, it ignores the Row-Level security filters, showing me the total for that client across all Managers and Partners. This is not the case when I create a new calculated column in the Fact table that only includes current year values. If I create this column, the RLS rules are properly applied. This column is of the form: IF(RELATED(DATE_TABLE[YEAR]) = DATE_TABLE[CURRENT_YEAR], AMOUNT, 0). Perhaps it's a Tableau background, but this order of operations is a little confusing to me, that RLS rules are applied after a calculated column is computed. I would expect that RLS rules are applied to all tables first. I would also expect that my filtering within CALCULATE() would essentially operate over a column of values equivalent to IF(RELATED(DATE_TABLE[YEAR]) = DATE_TABLE[CURRENT_YEAR], AMOUNT, 0). In either case, I think the expectation is that Row-Level Security truly means that any rows not meeting the RLS criteria are not available in any way to calculations, whether columns or measures. Perhaps this isn't a bug, but I think the community would really benefit from a clear description of this filtering "order of operations" as Tableau has available. This behavior was entirely not clear to me until I did more extensive testing and it seems quite counter-intuitive to me.

kojeyovuru · ‎01-05-2022

hello, the format #’##0.00 in power data model doesnt work as in Excel. It works only for 6 digits for example: 123'456.00 but for numbers with 7 digits an more it does not work. it formats numbers like this 9123'456.00 but it must be like this 9'123'456.00

shingo_suzuki · ‎01-03-2022

BIを更新すること、10回に1回測定の測定で、循環参照のエラーが発生します。 ODBCを定義してファイアバードからデータを取得します。できは、「循環参照されました」です。何でですか？

divyansh95 · ‎12-28-2021

My reports are using Odata and were working till last week and now this error comes up OLE DB or ODBC error: [DataSource.Error] OData: Request failed: The remote server returned an error: (500) Internal Server Error..

henripe · ‎12-26-2021

For Tabular models in Analysis Services "Sort by column" not working for all visuals when "Keep Unique Rows" is set as True. For table, matrix and waterfall chart visuals sort by column works, but for example bar charts, Power BI does not retain the sorting. This happens when "Keep Unique Rows" is set as True in Tabular Editor for the field that needs to be sorted.

HughMcD · ‎12-22-2021

In PowerBI Desktop v2.100.684.0 64-bit (December 2021) when I select a custom date format for a date field in the Model view, I can't get the custom format to accept either "mmm yy" or "mmm-yy". After typing in "mmm-yy" a custom format string, it is automatically converted into "MMM-yy" and then a few seconds later resolves as "\M\M\M-yy". what I type: what happens a few seconds later: and then a few seconds after that: I have set up date fields successfully with this format a few months ago, so looks like whatever bug is causing this was introduced within the past few releases of PowerBI desktop. Please help!

Christophe93 · ‎12-22-2021

Hi For Desktop native connectors to Snowflake & Bigquery is it possible please Microsoft to replace current techno : ODBC SIMBA ? -ODBC has poor perfomances & gets lot of problems to mastering some editors APIs (Snowflake , Google <-- google storage API) - Implement a new middleware techno (2022 techno , ODBC too old) - Issues without any warnings most of the time Regards Christophe

ncxmsn1 · ‎12-21-2021

when I want to open a report in PowerBI Desktop I get this: Website could not be retrieved Unable to determine IP address for ms-pbi.pbi.microsoft.com This indicates that the proxy was not able to resolve the hostname presented in the URL. Check if the address is correct. The DNS server returned: Name Error: The domain name does not exist.

bdarcy · ‎12-20-2021

As of this morning, anything set with the aserteriks date/time format has started coming through as US format rather than UK. This hasn't been an issue until the December 2021 update.

bertalan_ronai · ‎12-17-2021

Hi! We are using a Premium Capacity. I have noticed two cases where I had to add new columns to an existing dataflow and there was a bug. I add the new column into the datasource in the database, the sources are usually stored procedures. I see the new column in the dataflow editor. - > I don't see the new column in the report after importing the dataflow. Solution 1 is that even if in the dataflow editor the type of the new column is correct, I add a step to change type to the same type. Sulution 2 is deleting the dataflow and creating a new one via pasting the code from the advanced editor. Bertalan Ronai @Bertie_from_bi

Wouter · ‎12-16-2021

Wauw, really need your help. Please see screenshots: Picture 1: Table, 4 columns: Oppertunityid is Unique Picture 2: Expanding column UG – Systemusers – Selecting one column “Fullname” Picture 3: Fullname gets displayed…. BUT.. columns Statecode_display an statuscode_display get NULLED ??? WHAT?.. Tried some ( al lot) things already This is not only in preview of the result in the query builder Tested it in BI dataflow en PowerBI Desktop Setting a filter to show only top 10 rows makes the problem disappear – but of course that’s not an option. Source is Dynamics 365 CE Messing around with the column order makes no difference. Number of columns that get expended makes no difference. Would be great if someone could help keeping me sane ?? Have a great day. Kr Wouter K

sequin222 · ‎12-15-2021

TECHNICAL DETAILS An unknown error occurred. If you continue to see this error, please provide the following information when requesting support. Date and Time: 2021-12-15 20:56:33Z Activity Id: 920575cf-d9f9-410a-a31b-dd5720a2598f

Share your ideas and vote for future features

Inserting a Directquery table

Cannot connect dataflow to Azure SQL Database

Dataflows ridiculously & unusably slow

Several Users Cannot Get Past Loading Data Step on PowerBI Desktop

"Too many datasets being processed concurrently" false error

PowerBI Desktop looses Microsoft Authentication and cause crash of all Office applications

Cambio origen datos: ¿cómo forzar a que solo aparezcan las columnas existentes en el nuevo origen?

Power BI Services: No aparecen informes relacionados a un dataset

CALCULATE() function oversteps Row-Level Security rules applied to fact table

Custom numeric format #’##0.00 doesnt work

Firebirdから取得したデータの更新で、10回に1回ほどの頻度で、循環参照のエラーが発生する

OLE DB or ODBC error: [DataSource.Error] OData: Request failed: The remote server returned an error:

Sort by column not working for all visuals when "Keep Unique Rows" is set as True

[BUG] Custom Format beginning with "mmm" automatically resolves the "mmm" into "\M\M\M"

Desktop native connectors to Snowflake & Bigquery - Improve/change current techno : ODBC SIMBA

open a report in PowerBI DesktopI shows Website could not be retrieved

Date/time settings don't match operating system in December 2021 update

Adding new columns to dataflows

BUG Merging and Expanded losing data in existing columns

Power BI Download for Analyze in Excel Link Broken

Helpful resources

Power BI Embedded with DirectLake Dataset Error

Small multiple Y axis values disappearing

Publish to web url not working

Slicer bug?

TypeConversionFailure when not trying to convert