Data Import & Export

Fix SharePoint Person Field Errors When Loading Data into Power BI

Steve KSteve K Nov 2, 2026 868 views

Question details

The user is experiencing HTTP 404 or 500 errors in Power Query when importing SharePoint lists containing Person fields into Power BI.

Fix SharePoint Person Field Errors When Loading Data into Power BI
Product
Power BI and SharePoint
Device & OS
not provided
Scenario
Importing data from a SharePoint list to Power BI using Power Query.
Observed behavior
Power Query returns HTTP 404 or 500 errors during data load, often triggered by specific rows or columns containing invalid user references, URIs, or permissions in the SharePoint Person fields.
Before you start

Ensure you have the exact URL of the SharePoint site and sufficient permissions to access both the SharePoint list and its associated user directory.

Solution 1Recommended

Clear and Re-enter Data Source Credentials

Resetting your SharePoint credentials in Power BI often resolves authentication and permission-based HTTP errors.

Outdated or corrupted cached credentials can prevent Power BI from properly resolving specific field types, such as the Person field in SharePoint. Clearing these permissions forces a fresh authentication token.

1
Open Data Source Settings

Open Power BI Desktop, navigate to the 'File' tab, select 'Options and settings', and click on 'Data source settings'.

2
Locate SharePoint Source

Find your specific SharePoint site URL in the list of data sources and select it.

3
Clear Permissions

Click the 'Clear Permissions' button at the bottom of the window to remove the cached credentials for this site.

4
Re-authenticate

Refresh your data connection and, when prompted, sign in again using your Microsoft 365 account credentials (typically using the Organizational account option).

Authentication Refreshed: If the error was solely caused by an expired token or permission glitch, the data refresh should now complete successfully.
Free Microsoft Office alternative

Discover WPS Office for Seamless Data Management

While Power BI and SharePoint are Microsoft-specific tools, WPS Office provides a lightweight, free alternative for your daily spreadsheet, document, and presentation needs. Experience familiar interfaces and high compatibility without the hefty subscription fees.

  1. 1. Download and Install: Get WPS Office for free from the official website and install it on your device.
  2. 2. Export SharePoint Data: Export your SharePoint list as an Excel file (.xlsx or .csv) to your local drive.
  3. 3. Open and Analyze: Open the downloaded file using WPS Spreadsheet to clean data, apply filters, and build charts effortlessly.
Fully compatible with Microsoft Excel (.xlsx), Word (.docx), and PowerPoint (.pptx) formats.Lightweight application that opens large datasets and files instantly.Free to use with a familiar, easy-to-navigate user interface.Built-in tools for data sorting, filtering, and basic visualization to manage exported SharePoint data.
microsoft office alternative - wps office

Frequently Asked Questions

Why do SharePoint Person fields cause HTTP 404 errors in Power BI?

HTTP 404 errors typically occur when Power BI attempts to resolve a user in the Person field, but the user's profile has been deleted, the URI is invalid, or the user no longer exists in the organization's active directory.

How can I bypass Person field errors without fixing the source data?

In Power Query, you can choose to remove the specific Person column that is causing the error, or filter out the rows containing the corrupted data before expanding the record fields, allowing the rest of the data to load.

Does clearing Data Source Settings delete my Power BI reports?

No, clearing data source permissions only removes the saved login credentials for that specific connection. Your reports, data models, and visuals remain completely intact.

What should I do if the error is an HTTP 500?

An HTTP 500 is an Internal Server Error. This usually indicates a backend issue or timeout with SharePoint itself. Wait a few minutes and try again; if it persists, your Microsoft 365 administrator will need to investigate.