'%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 Remove Corrupted Records from a SharePoint List in Power Apps
Question details
The user needs to remove corrupted records containing encoded HTML and image data from a SharePoint list without breaking connected apps.
- Product
- SharePoint
- Device & OS
- not provided
- Scenario
- Managing a SharePoint list that feeds data to Power Apps and Power BI, where specific exported records have become corrupted.
- Observed behavior
- Affected values do not appear normally in standard list views, and the ID column incorrectly displays encoded data instead of the expected eight-digit numbers.
Before escalating the issue, document the affected item IDs, gather the export data, and note the specific timestamps when the corruption was first observed.
Escalate to Microsoft 365 Support for Backend Removal
Since the corrupted records are invisible in standard SharePoint views, backend intervention from Microsoft is required to safely remove them without affecting your Power Apps integration.
Because these corrupted records contain complex encoded HTML and image data that break standard SharePoint list views, attempting to delete them via regular list settings might fail or cause synchronization issues with Power Apps and Power BI. The safest method is to have Microsoft support inspect the backend data logs and remove the specific entries.
Gather the SharePoint list URL, affected item IDs (if identifiable), export data logs, and details of your Power Apps and Power BI connections.
Reach out to your organization's Microsoft 365 Administrator, as standard users cannot open backend support tickets directly.
Have the administrator log into the Microsoft 365 admin center and go to the 'Support' section.
Provide the compiled list details and timestamps in a new service request so the Microsoft engineering team can clear the corrupted entries from the backend.
Need a simpler way to manage your data? Try WPS Office
While complex SharePoint list corruptions require Microsoft backend support, WPS Office offers a lightweight, hassle-free alternative for managing standard spreadsheets and daily records offline. Enjoy seamless compatibility with Microsoft Office formats without the heavy enterprise overhead.
- 1. Download WPS Office: Visit the official WPS Office website to download the free suite for your device.
- 2. Install the Software: Run the installer and follow the quick on-screen instructions to set up WPS Office.
- 3. Open Your Records: Open your exported CSV or Excel files directly in WPS Spreadsheet to analyze and clean your data.
Frequently Asked Questions
Why can't I see the corrupted records in my SharePoint list view?
Corrupted records containing malformed HTML or heavy encoded image data can break the rendering of the standard SharePoint list view, making those specific rows invisible or causing the entire view to fail loading.
Will deleting the SharePoint list and recreating it fix the Power Apps connection?
While recreating the list removes the corrupted data, it will immediately break existing data connections in Power Apps and Power BI, requiring you to remap all data sources and formulas. Backend cleanup by Microsoft support is much safer.
Can I use a Power Automate flow to delete these hidden corrupted items?
If you know the specific item IDs, you might try building a Power Automate flow using the 'Delete item' action. However, severe data corruption often causes API failures during deletion, which is why escalating to backend support is the recommended path.
