New Power Query experience known limitations and workarounds

Use this reference to find known limitations in the new Power Query UI and available workarounds before troubleshooting an unfamiliar behavior. The entries cover Get Data and Power Query Editor and are organized by where the limitation appears. When the same limitation affects several connectors or controls, they're listed together.

The legacy experience, or legacy UI, is the original Power BI Desktop Get Data and query editor interface. The New Power Query experience preview setting enables the new interface in Desktop. Power BI web modeling uses Power Query Online. For an introduction, see Get data in Power BI Desktop and Edit semantic models in the Power BI service.

This article is a reference to known limitations, not a complete feature comparison or a list of issues that every Desktop workflow encounters. It includes missing UI capabilities and observed behavior; it doesn't classify every entry as a product defect. Limitations shared with the legacy experience are identified where known.

Note

Some workflows in Power BI Desktop start in the new Power Query UI and finish in the legacy UI, even when the preview feature is enabled. In those cases, the legacy UI provides functionality that isn't yet available in the new UI, so you can complete the workflow without exposing the new-UI limitation.

Power BI web modeling uses the new UI directly through Power Query Online and is subject to its limitations. Desktop uses the legacy experience where possible, so a listed limitation might not surface in the same way in Desktop.

Return to the legacy experience

If a listed limitation prevents you from completing your work in Power BI Desktop and no issue-specific workaround is provided, you can return to the legacy experience.

Go to File > Options and settings > Options > Preview features, and clear New Power Query experience. You don't need to restart Power BI Desktop.

This setting applies only to Power BI Desktop. It doesn't switch Power Query Online in Power BI web modeling to the legacy UI. A workaround that links to this section is a Desktop option, not a web-modeling workaround.

Returning to the legacy experience doesn't resolve limitations shared by both experiences. Individual entries explain when this applies.

Share feedback or report an unlisted limitation

Have feedback about the new Power Query experience, or encountered a limitation that isn't listed here? Share your feedback in the Power BI community discussion.

Describe where you encountered the behavior, what you expected, and what happened. The discussion is public, so don't include credentials, personal information, or confidential data.

Find a limitation by location

Choose the part of the interface where the limitation appears. Entries are listed alphabetically within each location.

Get Data and Navigator

Ribbon

Queries pane

Query settings and Applied steps

Data preview

Formula bar and Advanced Editor

Dialog boxes

Editor-wide behavior

Get Data and Navigator

These limitations affect connector selection, connection forms, Recent sources, OneLake catalog, and Navigator.

Analysis Services connections use the legacy experience

Selecting one of the following connectors in the new Desktop Get Data experience opens the legacy connection experience. The new interface doesn't provide choices for live, import, or DirectQuery connections for these connectors.

Affected connectors:

  • SQL Server Analysis Services.
  • Azure Analysis Services.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

AtScale Models live-connection choices are unavailable

The new Get Data experience in Power BI Desktop doesn't provide the AtScale Models choice between connecting live and importing data. This connection-mode selection gap is separate from the connector-availability limitation.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

Authentication choices can be incorrect for hidden connectors

Connectors you hide from the Get Data list can show incorrect authentication choices in later connection flows in the new Power Query UI. Hiding a connector from Get Data doesn't make its underlying functions unavailable in the formula bar.

Workaround (Power BI Desktop): Return to the legacy experience.

Back returns to the starting page instead of the full connector list

When you open the full connector list by selecting View more in the new Get Data experience, choose a connection type, and then select back, you might return to the starting page instead of the full list.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

Connection credentials appear for connectors that don't need them

The new Power Query connection form can display a Connection credentials section for a connector that handles authentication implicitly, even though the connector doesn't require credential entry.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Connector authentication.

Connector query inputs lack code formatting

The query input in the following new connection forms doesn't provide the multiline code-editing presentation available in the legacy experience.

Affected connectors:

Workaround (Power BI Desktop): Return to the legacy experience.

Connectors aren't available in the new Get Data experience

The following connectors aren't available in the new Get Data UI.

Affected connectors:

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

Credential scope selection is unavailable

The new Power Query connection form doesn't provide the legacy credential-scope selector for applying credentials to a broader or narrower level of a source path.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Connector authentication.

Custom connector dropdown descriptions are missing

The new Power Query connection form doesn't display descriptions or inline guidance for custom connector dropdown parameters. Guidance for free-text fields can still appear.

Workaround (Power BI Desktop): Return to the legacy experience.

Custom connector dropdowns select a value automatically

Custom connector dropdown parameters in the new Power Query UI can default to the first allowed value instead of the empty selection used by the legacy experience. An optional parameter can therefore have a value without an explicit selection.

Workaround (Power BI Desktop): Return to the legacy experience.

Custom connector list parameters don't show their allowed values

The new Power Query connection form doesn't display the allowed values for custom connector list parameters as selectable choices.

Workaround (Power BI Desktop): Return to the legacy experience.

Custom connector results open directly in the editor

A custom connector in the new Desktop Get Data experience opens Power Query Editor directly instead of displaying the legacy preview with separate Load and Transform data choices. This flow requires entering the editor even for a simple load.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Navigator and data preview.

File connectors replace a web URL with a local file path

Pasting a web URL into the file-selection dialog in the new Desktop experience downloads the file and references its local path instead of retaining the URL. The resulting source no longer points directly to that web location.

Workaround: Use the Web API connector for the URL instead of entering it in the file-selection dialog.

Learn more: Web connector.

Folder browsing uses a different dialog from file browsing

The Folder connector in Power BI Desktop uses the older folder-selection dialog rather than the modern file-browsing dialog. Folder and file selection therefore use different interfaces in the new experience.

Workaround (Power BI Desktop): You can return to the legacy experience, but the Folder connector also uses this folder-selection dialog in the legacy experience.

Learn more: Folder connector.

Live connections are missing from Recent sources

Live connections to Analysis Services or Power BI semantic models don't appear in the new Recent list in Power BI Desktop.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

Multipart URL and path controls aren't available

The following new connection forms don't provide the legacy control for composing a URL or path from multiple parts. For OData, long queries use the available URL input rather than the multipart control.

Affected connectors:

Workaround (Power BI Desktop): Return to the legacy experience.

Native query inputs for built-in connectors can't be resized

Native-query inputs for built-in connectors, including SQL Server and Oracle, don't provide a width-resizing gesture in the new connection forms. Extension-based connectors such as Amazon Redshift provide this resizing behavior.

Workaround (Power BI Desktop): Return to the legacy experience.

Native query results don't have a separate table preview

For connectors that accept native queries, the new Get Data flow in Power BI Desktop doesn't provide the legacy standalone table-preview stage. In the legacy experience, this stage allows you to inspect the query result and choose between canceling and transforming it before entering the editor.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Import data using a native database query.

The new Power Query Navigator uses a different layout for Cancel and the action buttons than the legacy dialog. The action button isn't necessarily immediately to the left of Cancel.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Navigator and data preview.

Reopen Navigator from a navigation step after viewing cached data can show Failed to evaluate the base result when credentials expire. The new UI doesn't prompt for the credentials needed to complete the evaluation or indicate that credentials are the cause.

Workaround (Power BI Desktop): Return to the legacy experience.

The new Power Query Navigator can show truncated navigation tables, leaving some source items unavailable in the tree. Custom connectors with nested navigation tables can show the same behavior.

Affected connectors and navigation tables include:

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Navigation tables.

When a custom connector exposes a function with parameters, the new Power Query Navigator doesn't provide the Apply button for submitting those parameters. Continuing from that function entry produces errors instead of a preview.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Navigator and data preview.

The new Power Query Navigator can display icons that don't match the source item type. For example, a table can appear with a folder icon. This display limitation is separate from incomplete navigation tables.

Affected connectors and navigation tables include:

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Navigation tables.

When Navigator is reopened in the new Power Query UI, a message bar can extend beyond the width of the source tree.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Navigator and data preview.

The new Power Query Navigator can show an older list of items without indicating that it's out of date. Newly created dataflows or other source objects can be missing even though they appear in the legacy experience.

Workaround: Open the navigation table in Power Query Editor, refresh its data preview, and then return to Navigator.

Learn more: Navigator and data preview.

The Transform option in the new Get Data Navigator's context menu is available only for specific nodes. Unlike the legacy Navigator, the new UI doesn't offer this action for every node you select.

Workaround (Power BI Desktop): Return to the legacy experience.

OData Include open type columns option is missing

The legacy Include open type columns checkbox isn't available in the new OData connection form.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: OData Feed connector.

ODBC connection fields and DSN selection are incomplete

The new ODBC connection form doesn't provide all of the legacy connection fields or the data source name (DSN) dropdown. This connection-form gap is separate from the connector-availability limitation.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: ODBC connector.

ODBC row reduction detection is unavailable

The new ODBC connection form doesn't support automatic detection through the Detect control for the Supported row reduction clause advanced option.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: ODBC connector.

OneLake catalog closes when you go back from a lakehouse connection

Going back after selecting a lakehouse in the new OneLake catalog can close Get Data instead of returning to the previous page in the connection flow.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

OneLake catalog doesn't show external-tenant items

The new OneLake catalog in Power BI Desktop doesn't provide the legacy external-items tab for finding Fabric and Power BI items shared from another organization.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

OneLake catalog lakehouse selection leaves the editor

Selecting a lakehouse from the new OneLake catalog can cause the connection flow to leave Power Query Editor rather than continue within it.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

OneLake catalog parent and child items aren't linked

The new OneLake catalog in Power BI Desktop doesn't consistently nest related items under their parent, such as a SQL analytics endpoint under its lakehouse.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

OneLake catalog scrollbars don't match the theme

Scrollbars in the new OneLake catalog section on Home and in the dedicated catalog page can retain colors that don't match the active theme, even when surrounding controls use that theme.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

OneLake catalog takes a long time to load

The new OneLake catalog in Power BI Desktop can load slowly both on the Get Data Home page and when opened as its own page, delaying browsing and item selection.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

Parquet authentication choices are missing

The new Parquet connection form doesn't provide the authentication and connection-setting choices available in the legacy experience.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Parquet connector.

Query parameter selectors aren't available in every input

The new connection forms don't consistently provide query parameter selectors across all input fields. An input that accepts a parameter in the legacy experience might not offer that choice in the new form.

Affected connectors:

Workaround (Power BI Desktop): Return to the legacy experience.

Recent sources differ between the legacy and new entry points

The legacy and new Recent sources experiences keep separate lists. Entries aren't shared between the two lists.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

Recent sources entry point can open the legacy list

The legacy Recent sources entry point in Power BI Desktop opens the legacy list rather than the new Get Data experience.

Workaround (Power BI Desktop): Return to the legacy experience.

SAS key authentication doesn't complete

The following connection forms list SAS Key as an authentication option, but selecting it doesn't allow creation or use of the required credential. The connection can't be completed with this option.

Affected connectors:

Workaround (Power BI Desktop): Return to the legacy experience.

Server and database connections use the same icon

The new connection list in Power BI Desktop can use the same icon for a server-level SQL Server connection and a connection to a specific database.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

Snowflake key-pair authentication isn't available

The new Snowflake connection form doesn't provide key-pair authentication.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Snowflake connector.

SQL Server paths retain trailing spaces

The new connection experience doesn't remove trailing spaces from SQL Server paths as the legacy experience does. The two experiences can therefore retain different paths.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Connector authentication.

Supermetrics functions appear as cubes in Navigator

The new Power Query Navigator shows Supermetrics function entries with cube icons instead of function controls. These entries don't provide the parameter inputs available in the legacy Navigator.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Navigator and data preview.

Teradata LDAP authentication is unavailable

The new Teradata connection form doesn't provide the LDAP authentication choice.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Teradata connector.

The link in the 3rd Party information popup can fail to open in the new Get Data experience in Power BI Desktop.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

Transform data is inside the Load dropdown

The new Power Query Navigator places Transform data inside the Load split-button dropdown instead of showing it as a separate button. Load is the visible default action.

Workaround: Open the dropdown next to Load, and select Transform data.

Learn more: Navigator and data preview.

Web API command timeout input is missing

The new Web API connection form doesn't provide the legacy advanced input for configuring command timeout.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Web connector.

Web API key authentication is unavailable

The new Web API connection form doesn't support API key authentication.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Web connector.

Web API request header inputs are missing

The new Web API connection form doesn't provide the legacy advanced inputs for configuring HTTP request headers.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Web connector.

Web page wait time input is missing

The new Web Page connection form doesn't provide the advanced Wait time input.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Web connector.

Web preview is unavailable in Navigator

The new Power Query Navigator doesn't provide the legacy Web view preview for inspecting a web page while choosing its data.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Web connector.

Ribbon

These limitations affect commands and controls on the Power Query ribbon.

Binary Tools and Open As are missing

The new editor in Power BI Desktop doesn't provide the legacy Binary Tools contextual tab and Open As command for choosing how to interpret binary results.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Data source settings shortcut is missing

The new editor ribbon in Power BI Desktop doesn't provide the Data source settings command for opening the legacy settings dialog.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Connector authentication.

Quick Access Toolbar is missing

The new Power Query Editor in Power BI Desktop doesn't include the Quick Access Toolbar that's available in the legacy editor.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Replace Errors is missing for list results

The new Power Query ribbon doesn't provide Replace Errors when a query returns a list. The table-column command doesn't provide the equivalent action for an entire list.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Dealing with errors.

Replace Values is missing for list results

The new Power Query ribbon doesn't provide Replace Values when a query returns a list. This limitation also exists in the legacy ribbon; it isn't exclusive to the new experience.

Workaround (Power BI Desktop): You can return to the legacy experience, but doing so doesn't add this missing list command.

Learn more: Replace values.

Ribbon mode isn't remembered

A ribbon collapsed to a single line in the new Power Query UI returns to its expanded mode after the editor is closed and reopened. The collapsed layout isn't preserved.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Standard calculations are disabled for three or more columns

When you select three or more numeric columns in the new Power Query UI, the Standard command on the Add column tab is disabled. This behavior prevents you from performing multicolumn calculations through that ribbon control.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Queries pane

These limitations affect query naming, selection, and layout in the Queries pane.

Adding a blank query leaves an existing query selected

When you add a blank query through Get Data in the new Power Query editor, the editor might keep an existing query selected if multiple queries already exist. The editor doesn't automatically display the newly created blank query.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Queries pane.

Can't paste queries through a context menu

To paste queries into the new Power Query UI, use Ctrl+V. There's no context menu action for pasting queries.

Workaround: Press Ctrl+V to paste queries.

New query names use different numbering patterns

To avoid name collisions, the new Power Query UI assigns query names that follow different patterns, such as Query2 and Query1 (2). Blank-query creation and other creation or duplication flows don't use a consistent numbering pattern. For blank queries, the new Desktop flow can use the parenthesized pattern while Power Query Online uses incrementing numbers.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Queries pane.

Query group arrows don't follow right-to-left layout

Query-group expand and collapse arrows in the new Queries pane don't follow the expected right-to-left direction.

Workaround (Power BI Desktop): Return to the legacy experience.

Query icons and labels have incorrect spacing in right-to-left layout

Query nodes in the new Queries pane use incorrect spacing between icons and labels in right-to-left layout.

Workaround (Power BI Desktop): Return to the legacy experience.

Query name validation doesn't fully cover calculated-table conflicts

The new editor doesn't fully apply Power BI Desktop's calculated-table name validation when you name queries. A conflicting name might not receive the same validation feedback as in the legacy experience.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Queries pane.

Right-clicking a query selects it and evaluates its preview

Right-clicking a query in the new Queries pane selects that query and triggers its data preview evaluation, even when you only want to use a context-menu command such as Advanced Editor. Right-clicking doesn't trigger query selection in the legacy pane.

Workaround (Power BI Desktop): Return to the legacy experience.

Query settings and Applied steps

These limitations affect query settings and reopening transformation steps.

Cube Add Items steps can't be reopened for editing

The Cube Add Items step doesn't support reopening from Applied steps for editing in the new Power Query experience in Power BI Desktop.

Workaround (Power BI Desktop): Return to the legacy experience.

Query settings visibility doesn't follow the editor option consistently

The new editor in Power BI Desktop doesn't consistently apply the configured visibility preference for the Query settings pane.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Applied steps.

You can't reopen XML parsing steps for editing

You can't reopen XML parsing step settings in the new Power Query UI to change the parsing operation. In the legacy editor, you can reopen these settings.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Parse text as JSON or XML.

Data preview

These limitations affect the values, errors, and function results displayed in the editor.

Column from examples selects all columns from a column context menu

Opening Column from examples from a column's context menu in the new data preview selects all columns as context for the operation. The legacy experience selects only the column you right-clicked.

Workaround (Power BI Desktop): Return to the legacy experience.

Column widths resize automatically with no off setting

The new data preview automatically resizes column widths based on their values. A setting to turn off this automatic resizing isn't available.

Workaround (Power BI Desktop): Return to the legacy experience.

Extract Values is missing from list-column expansion

When you expand a column that contains lists in the new Power Query editor, you expand values to new rows without the option to Extract values. The dropdown doesn't provide the option to concatenate each list into a single value with a chosen delimiter.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Fixed-width preview font preference isn't consistently applied

The new data preview doesn't consistently apply the fixed-width font preference from Power BI Desktop options.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Function result previews omit detailed descriptions

When a query returns a function, its preview in the new Power Query UI omits the full description, expanded parameter explanations, and details of nested options available in the legacy experience.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Using custom functions.

Function result previews omit worked examples

When a query returns a function, its preview in the new Power Query UI omits the worked examples, usage code, and expected outputs available in the legacy experience.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Using custom functions.

Go to Error is missing

An error shown in the new data preview in Power BI Desktop doesn't provide the legacy Go to Error button for navigating directly to the step where the error originated.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Dealing with errors.

Preview results can be delayed by other query work

The new editor in Power BI Desktop can delay a data preview while processing other query work, including work that doesn't produce a visible result.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Value distribution labels are misaligned in right-to-left layout

Value distribution labels in the new Power Query data preview are misaligned in right-to-left layout.

Workaround (Power BI Desktop): Return to the legacy experience.

Whitespace display preference isn't consistently applied

The new data preview in Power BI Desktop doesn't consistently apply the option to show spaces and other whitespace.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Formula bar and Advanced Editor

These limitations affect M authoring and the controls around the formula bar and Advanced Editor.

Advanced Editor has no Maximize control

The new Advanced Editor doesn't provide the legacy Maximize control for enlarging the editor when working with a long M script.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

The new Advanced Editor doesn't provide the help or more-information link available in the legacy editor.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query M reference.

Advanced Editor script validation differs

The new Advanced Editor doesn't provide the same script-validation controls and feedback as the legacy editor.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Formula bar has no option to require an explicit equals sign

The new formula bar doesn't provide an option to require an explicit equals sign for step-level formulas. This setting is specific to step formulas, not other M-editing surfaces.

Workaround (Power BI Desktop): Return to the legacy experience.

Formula bar visibility doesn't follow the editor option consistently

The new editor in Power BI Desktop doesn't consistently apply the configured visibility preference for the formula bar.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

M editor display options aren't available consistently

The new Power Query M-editing surfaces, including the formula bar and Advanced Editor, don't consistently provide the following legacy display options.

Affected options:

  • Line numbers.
  • Script minimap.
  • Whitespace characters in M code.
  • Word wrap for long lines.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

M editor matching-bracket highlighting is missing

The new M-editing surfaces don't highlight matching opening and closing parentheses or brackets when the cursor is positioned at the corresponding expression. The legacy editor provides this highlighting, including for the square brackets around a record.

Workaround (Power BI Desktop): Return to the legacy experience.

M editor new-line indentation differs from the legacy experience

New lines in the new M-editing surfaces don't preserve the indentation of the parent function or keyword in the same way as the legacy editor. For example, pressing Enter after a function's opening parenthesis doesn't use the legacy alignment with the parent expression.

Workaround (Power BI Desktop): Return to the legacy experience.

M editor text isn't visible in right-to-left layout

Text isn't visible in the following new M-editing surfaces when using right-to-left layout.

Affected surfaces:

  • Formula bar.
  • Advanced Editor.

Workaround (Power BI Desktop): Return to the legacy experience.

Dialog boxes

These limitations affect the named dialogs for editing connections, parameters, and transformations.

Advanced source settings stay collapsed when reopening a source

Reopening a Source step through its settings icon doesn't automatically expand the connection dialog's advanced section when one of its fields already has a value. Existing settings, such as a native query, remain inside the collapsed section.

Workaround (Power BI Desktop): Return to the legacy experience.

Change source is unavailable in modern Data source settings

Modern Data source settings doesn't provide the legacy Change source action for editing a connection's source arguments, including for extension-based connectors.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Connector authentication.

Changing a live connection uses the legacy dialog

Changing the source of an existing live connection in Power BI Desktop opens the legacy connection-setting flow rather than the new Get Data experience.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Connector authentication.

CSV and text file settings lack Open file as

The new CSV/text settings dialog doesn't provide the separate Open file as control for choosing how to parse the file, including fixed-width parsing. A new-source flow can show --None-- in the delimiter dropdown instead of a separate lines-of-text choice.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Text/CSV connector.

Custom column text editing doesn't work in right-to-left layout

The text editor in the new Custom column dialog doesn't work in right-to-left layout.

Workaround (Power BI Desktop): Return to the legacy experience.

Date inputs lack date pickers

Date inputs in the following new dialogs don't consistently provide a date picker.

Affected dialogs and inputs:

  • Conditional column: date inputs.
  • Row filters, including Equals, Before, After, and Between: date values.
  • Function invocation, including user-defined functions: date parameters.
  • Parameter-management and parameter-editing dialogs: date values.

Workaround (Power BI Desktop): Return to the legacy experience.

Deleting a connection is unavailable in Manage connections

The new Manage connections experience in Power BI Desktop doesn't provide a functional delete action for Desktop connections.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Connector authentication.

Edit credentials doesn't show the stored sign-in details

The new Edit credentials experience in Power BI Desktop doesn't show the stored username and masked-password indication in the same way as the legacy dialog.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Connector authentication.

Enter Data has no Load button

The new Enter Data dialog in Power BI Desktop doesn't provide a Load button for loading the data entered in the dialog.

Workaround (Power BI Desktop): Return to the legacy experience.

Function browser descriptions make the entire dialog scroll

A long description in the new Power Query function browser can make the entire dialog scroll instead of scrolling independently from the parameter inputs. Reaching the inputs can require scrolling past the description.

Workaround (Power BI Desktop): Return to the legacy experience.

Group by arrow doesn't follow right-to-left layout

The expand and collapse arrow in the new Group by dialog doesn't follow the expected right-to-left direction.

Workaround (Power BI Desktop): Return to the legacy experience.

Modern Data source settings isn't fully available

The modern Data source settings experience isn't fully integrated into Power BI Desktop. Not all settings entry points provide the new experience.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Connector authentication.

Native Database Query permission dialog is missing

Continuing from a native-query warning in the new Power Query UI doesn't open the legacy Native Database Query dialog for reviewing the query text and its permission information before proceeding.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Import data using a native database query.

Navigator re-entry shows only the first 100 items

When you reopen Navigator from the Applied steps pane, it shows only the first 100 items if a navigation table contains hundreds of items. The dialog doesn't let you load the remaining items. This item limit is separate from the connector-specific incomplete navigation tables described under Get Data and Navigator.

Workaround (Power BI Desktop): Return to the legacy experience.

Parameterization preference isn't consistently applied

Parameter-entry behavior in the new Power Query experience doesn't consistently follow the Power BI Desktop option for allowing parameterization.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Text by example editing can overlap a column header

After the new text-by-example experience can't infer a table from an example, editing a cell and pressing Tab can display the editable cell over the next column's header instead of in the expected cell position.

Workaround (Power BI Desktop): Return to the legacy experience.

Text by example right arrow doesn't advance to the next column

The Right arrow key in the new text-by-example editable grid doesn't commit the entered value and move to the next column.

Workaround (Power BI Desktop): Return to the legacy experience.

Text by example suggestions stop after an unmatched example

The suggestion list in the new text-by-example experience can stop appearing during cell editing after a table can't be inferred from an example.

Workaround (Power BI Desktop): Return to the legacy experience.

Text by example Tab leaves the grid when a cell isn't being edited

The Tab key in the new text-by-example editable grid moves focus to a button outside the grid when a cell is selected but isn't being edited. It moves to the next cell only while a cell is being edited.

Workaround (Power BI Desktop): Return to the legacy experience.

Editor-wide behavior

These limitations affect the editor window or more than one editor surface.

Column-authoring keyboard shortcuts aren't available

The following legacy keyboard shortcuts don't open the corresponding command in the new Power Query Editor.

Affected shortcuts:

Workaround (Power BI Desktop): Return to the legacy experience.

Connector text can retain a previous application language

After you change Power BI Desktop's application language back to the system language, some connector text can remain in the previously selected language. Different connectors can therefore display different languages.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Get data in Power BI Desktop.

Diagram view can't hide steps to show query-only cards

The new Diagram view doesn't provide a way to hide all steps and show only query names and metadata, such as query groups. Its existing compact presentation doesn't provide the query-only view available in the legacy Query dependencies view.

Workaround (Power BI Desktop): Return to the legacy experience.

Diagram view has no separate data-source nodes

The new Diagram view doesn't display separate data-source nodes linked to the queries that directly use those sources. The legacy Query dependencies view includes these nodes and their relationships.

Workaround (Power BI Desktop): Return to the legacy experience.

Diagram view has no vertical layout

The new Diagram view uses a horizontal layout without an option to change the direction to vertical. The legacy Query dependencies view provides a layout-direction choice.

Workaround (Power BI Desktop): Return to the legacy experience.

Editor and Get Data windows lack the Fabric and Office-style title bar

The new Power Query Editor and Get Data windows don't provide the custom title bar styled to match Fabric and Office apps.

Workaround (Power BI Desktop): Return to the legacy experience.

Editor freezes while evaluating queries during initial load

Opening a project with multiple queries and a large mashup can freeze the new editor while queries are rendered and evaluated. Its controls aren't interactive during this initial load.

Workaround (Power BI Desktop): Return to the legacy experience.

Editor window title doesn't identify the report file

The new Power Query Editor window title doesn't include the report filename, so it doesn't identify the associated report when multiple Power BI Desktop files are open.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Right-to-left layout is incomplete

Collapsed pane titles in the new Power Query editor are misplaced in right-to-left layout. Related limitations affect query group arrows, query icon spacing, value distribution labels, M editor text, Custom column editing, and the Group by arrow.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Scrollbars in visual views don't match the theme

Scrollbars in diagram view, query plan, and chart visuals can stay light-colored when the new editor uses a dark theme.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

The editor has little spacing at the bottom edge

The new editor window in Power BI Desktop doesn't have the expected bottom padding, so there's little space between its content and the window edge.

Workaround (Power BI Desktop): Return to the legacy experience.

Learn more: Power Query Editor overview.

Zoom keyboard shortcut doesn't work

The legacy Ctrl+Shift+Plus zoom shortcut doesn't work in the new Power Query Editor.

Workaround: Hold Ctrl and scroll the mouse wheel to change the zoom level.

Related content

Learn more about connecting to data and editing queries in Power BI:

  • Last updated on