SharePoint Document Issues

Fix SharePoint List Metadata Missing in Power BI Connection

Olivia Miller Oct 12, 2026 868 views

Question details

The user is trying to restore the Power BI connection to a SharePoint list after encountering missing metadata and Number columns absent from the rowset.

Fix SharePoint List Metadata Missing in Power BI Connection

Product: SharePoint / Power BI
Device & OS: not provided
Scenario: Connecting or refreshing a Power BI dataset linked to a SharePoint list.
Observed behavior: Power BI reports that a SharePoint Number column is missing from the rowset, and certain columns disappear from the list overview even though the item data remains available in the background.

Before you start

Verify that you have site owner or edit permissions for the affected SharePoint list and temporarily pause any automated Power BI refresh schedules while troubleshooting.

Solution 1Recommended

Restore the Expected SharePoint View Name

Power BI often relies on specific SharePoint view names to fetch schema data. Reverting a renamed view back to its original name typically restores the connection and missing metadata.

When Power BI connects to a SharePoint list, it may bind to the specific list view used during the initial data fetch. If site members rename this view (for example, renaming 'num' to 'All Items'), Power BI cannot locate the expected metadata columns, leading to refresh failures.

Access the SharePoint View Menu

Navigate to the affected SharePoint list in your web browser. Click on the view selector drop-down menu located in the top-right corner of the list header.

Edit the Current View

Select 'Edit current view' to open the view settings page, where you can verify the current view name and structure.

Rename the View

Change the 'View Name' field back to the exact name that Power BI expects (e.g., 'num' instead of 'All Items') and click 'OK' to save.

Refresh Power BI

Open your Power BI dataset and initiate a manual refresh to verify that the missing columns are restored to the rowset.

Restore the Expected SharePoint View Name

Automatic Recovery: Once the view name is restored, the connection should automatically succeed during the next scheduled Power BI refresh without needing dataset edits.

Solution 2

Verify and Adjust SharePoint Column Settings

Altered column display settings or formatting changes, particularly on Number columns, can cause them to be dropped from the expected list overview and Power BI rowset.

Solution 3

Request Tenant Diagnostics via Microsoft 365 Support

If view adjustments and column formatting checks do not resolve the missing metadata, tenant-level diagnostic logs are required to investigate deeper list corruption.

Free Microsoft Office alternative

Need a Lightweight Suite for Daily Office Tasks? Try WPS Office

While complex Power BI integrations and SharePoint list modeling require Microsoft's dedicated environment, you don't need heavy or expensive software for your everyday document, spreadsheet, and presentation tasks. WPS Office provides a lightweight, highly compatible alternative for individuals and teams.

1. Download the Installer: Visit the official WPS Office website to download the free installation package for your operating system.
2. Install and Set Defaults: Run the installer and opt to associate WPS Office with standard Microsoft Office file formats like .xlsx and .docx.
3. Open Your Files Seamlessly: Double-click your existing documents or spreadsheets to instantly open and edit them without layout distortion.

Seamlessly compatible with Microsoft Excel (.xlsx), Word (.docx), and PowerPoint (.pptx) formats.Free to use with a familiar, ribbon-based interface that requires zero learning curve.Lightweight design ensures fast launch speeds and smooth performance on older devices.Includes a powerful built-in PDF toolkit for converting, editing, and managing documents in one place.

microsoft office alternative - wps office

Frequently Asked Questions

Why does renaming a SharePoint view break my Power BI connection?

When Power BI imports data from SharePoint, the underlying query is often bound to a specific view name to filter data efficiently. If the view is renamed, the Power Query engine cannot locate it during refresh, causing metadata mismatches and connection failures.

Can changing a SharePoint column from Number to Text cause missing metadata errors?

Yes. Power BI caches the data types from its initial connection. Changing a column type (e.g., from Number to Text, or modifying percentage formats) in SharePoint without updating the Power BI dataset query can result in type mismatch errors and dropped columns.

How can I force Power BI to recognize the newly restored SharePoint view name?

After restoring the correct view name in your SharePoint list, open the associated file in Power BI Desktop, navigate to the Home ribbon, and click 'Refresh'. If your dataset is hosted on the Power BI Service, trigger a manual refresh from the dataset settings.

Are there alternative ways to connect Power BI to SharePoint to avoid view dependency?

Yes. When connecting via Power BI Desktop, you can use the 'SharePoint Online list' connector and select 'Implementation 2.0'. This method typically connects to the core list schema rather than relying on custom view names, reducing the risk of broken queries due to list modifications.

Document & File Issues