'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Duplicate Power BI Datasets in Excel Data Search
Question details
The user is seeing duplicate Power BI datasets when importing data into a local installation of Excel, despite only one matching dataset existing in Power BI.
- Product
- Microsoft Excel
- Device & OS
- not provided
- Scenario
- Searching for and importing datasets into Excel via Get Data > From Power Platform > From Power BI.
- Observed behavior
- Duplicate datasets incorrectly appear in the Excel data search results on a local desktop installation, whereas it functions normally in an Azure VDI environment.
Ensure you have the latest version of Microsoft 365 installed and verify that your Windows account credentials match the ones used for your Power BI workspace.
Clear Office Cache and Credentials
Clearing stored credentials and the Office cache resolves sync conflicts that cause Excel to display duplicate entries from the Power Platform.
Since the issue only occurs on a local desktop and not in Azure VDI, corrupted local cache or conflicting background credentials are the most likely cause.
Open Microsoft Excel, click on your profile name in the top-right corner, and select Sign Out.
Open the Windows Control Panel, go to Credential Manager, select Windows Credentials, and remove any credentials related to Microsoft Office or Power BI.
Navigate to File > Options > Save in Excel, scroll down to Cache Settings, and click Delete cached files.
Restart your computer, launch Excel, and sign back in to refresh your connection to Power BI.
Update and Repair Microsoft 365
An outdated or corrupted Office installation on a local desktop can cause discrepancies with Power BI integrations.
Manage Existing Data Connections
Verifying your existing workbook data connections can help identify if older duplicates are lingering within the current file's background queries.
Try WPS Office for Lightweight Spreadsheet Management
If you frequently encounter caching issues or integration errors with Microsoft Excel, consider WPS Office. It is a free, lightweight, and highly compatible alternative that offers powerful data analysis tools without the complex background sync processes.
- 1. Download WPS Office: Visit the official WPS website and click Free Download to install the software.
- 2. Open Spreadsheets: Launch WPS Office and select Spreadsheets to begin managing your data.
- 3. Import Your Data: Click Menu > Open to load your existing .xlsx workbooks and continue your analysis seamlessly.
Frequently Asked Questions
Why do Power BI datasets duplicate in Excel?
This typically happens due to corrupted cached credentials, outdated local Excel versions, or conflicting data connection histories on a local desktop environment.
How do I access Power BI datasets in Excel?
In Excel, navigate to the Data tab, click on Get Data, select From Power Platform, and then choose From Power BI.
Why does Excel work correctly in Azure VDI but not locally?
Azure VDI instances often use fresh session states or centralized network profiles, which automatically bypass local cache corruptions that commonly affect standalone desktop installations.
