logo
search
SharePoint Document Issues

Fix SharePoint List Items Missing in Power Apps and Automate

Steven ParkerSteven Parker Oct 19, 2026 869 views

Question details

Unexpected SharePoint list items are appearing in Power Apps and triggering Power Automate flows, but they are not visible in the connected SharePoint list.

How to Fix SharePoint List Items Created Automatically But Missing from the List
Product
SharePoint
Device & OS
not provided
Scenario
Managing a SharePoint list connected to a Power Apps application and customized with Power Automate approval flows.
Observed behavior
Dummy or automatically created items are visible in Power Apps and trigger workflows, but they remain completely hidden in the default SharePoint list views and lack version history.
Before you start

Ensure you have full owner permissions for the SharePoint list and the connected Power Automate flow to review run histories and view configurations.

Solution 1Recommended

Investigate Power Automate Flow Configurations

Check your Power Automate flows to ensure that loop actions or attachment processing steps aren't silently creating dummy list items.

Complex workflows involving multiple approval stages, loops, or moving attachments to newly created folders can sometimes generate unexpected dummy items. By analyzing the flow's run history, you can pinpoint exactly which step is creating these hidden items.

1
Open Power Automate

Navigate to the Power Automate portal and log in with your Microsoft credentials.

2
Select the Connected Flow

Go to 'My flows' and select the workflow connected to your affected SharePoint list.

3
Review Run History

Click on 'Run history' and select a recent run where the dummy item was generated. Look specifically at loop actions ('Apply to each') and approval outcomes.

4
Check Attachment Steps

Inspect any actions designed to move attachments or create folders, as these can mistakenly map attachment names to the title of a newly generated dummy item.

Investigate Power Automate Flow Configurations
Dummy Item Titles: Pay attention to the titles of the dummy items in Power Apps. If they match the names of attachments, the issue likely originates from the folder creation or attachment relocation steps in your flow.
Free Microsoft Office alternative

Boost Your Productivity with WPS Office

While troubleshooting complex SharePoint and Power Automate sync issues, ensure your actual document editing remains uninterrupted. WPS Office offers a free, lightweight, and highly compatible alternative for everyday document creation and team collaboration.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installation package for your device.
  2. 2. Install the Software: Run the installer and follow the on-screen prompts to set up WPS Office on your computer.
  3. 3. Open Your Documents: Launch WPS Office and seamlessly open any existing Microsoft Office files (.docx, .xlsx, .pptx) to continue working.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats.Lightweight installation with incredibly fast document processing times.Familiar user interface for a seamless migration from Microsoft Office.Built-in PDF editing and team collaboration tools.
microsoft office alternative - wps office

Frequently Asked Questions

Why do items show in Power Apps but not in my SharePoint list?

This discrepancy often happens when items are created in an incomplete state by a background process like Power Automate, or if the SharePoint list view has active filters hiding those specific items while Power Apps directly queries the unfiltered data source.

Can a Power Automate approval flow create dummy items?

Yes. If an approval flow includes actions that move attachments or create new folders upon completion, misconfigured mapping can cause the flow to accidentally generate new list items (dummy items) using the attachment names as item titles.

How do I know if my SharePoint ID column is skipping numbers?

If you look at your SharePoint list and see a jump from ID 717 directly to 734, the missing IDs (718-733) were likely created and either immediately deleted, hidden by a view filter, or generated as orphaned items by a workflow error.