Share via

Issue Importing SharePoint List data into Vibe

Ethan Evers 25 Reputation points
2026-05-19T19:46:39.61+00:00

I’m currently testing the Power Apps Vibe (preview) experience and have run into an issue that I haven’t been able to resolve, and I’m seeing similar behavior mentioned by others online.

Scenario

  • I generate a blank code app using Vibe, with clear instructions to not create any data tables
  • The app is created successfully with no issues
  • I then go to the Data tab and attempt to add a SharePoint list

Issue

When I try to connect the SharePoint list:

  • It appears that Vibe begins to pull in or generate a data table
  • However, the process does not complete successfully
  • The table becomes essentially non-functional / unusable
  • I am unable to:
  • Interact with the table
  • Bind it properly to the app
    • Use it in any meaningful way I’m currently testing the Power Apps Vibe (preview) experience and have run into an issue that I haven’t been able to resolve, and I’m seeing similar behavior mentioned by others online.

      Scenario

      • I generate a blank code app using Vibe, with clear instructions to not create any data tables
      • The app is created successfully with no issues
      • I then go to the Data tab and attempt to add a SharePoint list

      Issue

      When I try to connect the SharePoint list:
      • It appears that Vibe begins to pull in or generate a data table
      • However, the process does not complete successfully
      • The table becomes essentially non-functional / unusable
      • I am unable to:
        • Interact with the table
        • Use it in any meaningful way
          User's image
Microsoft 365 and Office | SharePoint | Development
0 comments

Answer accepted by question author

Ian-Ng 13,275 Reputation points Microsoft External Staff Moderator
2026-05-19T21:26:03.6333333+00:00

Hi @Ethan Evers, 

Thank you for sharing the detailed explanation. 

Based on your description, this issue appears to be related more to the Power Apps Vibe preview experience than to a standard SharePoint Development issue. Power Apps vibe (preview) shows that SharePoint lists can be added as a data source in Vibe, but the feature is still in preview and is subject to change.

In particular, SharePoint lists are currently read-only in Power Apps vibe, and some column types such as Location, ManagedMetadata, Calculated, ExternalData, and TaskOutcome are not fully supported and are converted to text columns. That could help explain why the table appears to connect but then becomes unusable or does not behave as expected in the app.  

User's image

Since your issue is happening specifically inside the Vibe app-building experience right after adding a SharePoint list through the Data tab, it is tied directly to Power Apps data-binding behavior rather than standard Office features.

Because of that, I highly recommend reposting this in the Power Platform Community, specifically under the Power Apps forum. That space is actively followed by Microsoft MVPs, platform developers, and experts who work directly with Vibe and SharePoint connections every day. They will be much better equipped to pinpoint exactly why the data is misbehaving and give you a quick, practical workaround.

If you repost there, it may help to include whether the list contains unsupported column types, whether the same behavior happens with a simple test list, and any error message or session details shown during the connection attempt.

I hope this helps point you to the right support channel.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-05-19T19:46:58.46+00:00

    In the current Power Apps Vibe (preview) experience, SharePoint list integration is limited and behaves differently from Dataverse tables, which explains the behavior being observed.

    Key points from the preview capabilities:

    1. SharePoint lists are read‑only in Vibe.
      • Vibe connects directly to the list, but list items can’t be edited from Vibe.
      • Any changes to items must be made directly in SharePoint.
    2. Some SharePoint column types are not fully supported and are converted to text when brought into Vibe:
      • Location, ManagedMetadata, Calculated, ExternalData, and TaskOutcome columns are converted to text columns.
      • Other unsupported list/column types may not behave as expected.
    3. When a SharePoint list is added successfully:
      • It appears in the Data workspace with a SharePoint icon and its columns.
      • Because it is read‑only and not a Dataverse table, actions such as New row, Row ownership, and some table‑editing operations in the Vibe data designer are not applicable in the same way as for Dataverse tables. This can make the table appear “non‑functional” compared to native Vibe data tables.
    4. Vibe does not automatically suggest or identify lists; the list must be selected explicitly from the SharePoint site. If the list is added, but cannot be interacted with like a normal Vibe table, that is consistent with the current preview design rather than a fully supported CRUD data source.

    Given these preview constraints, the SharePoint list in a Vibe blank code app can currently be used primarily as a read‑only data source for the app UI, not as a fully editable table inside the Vibe data workspace. Any item creation or updates must be done in SharePoint itself, and complex/unsupported column types may limit how useful the list is inside Vibe.

    For scenarios that require full create/update/delete and richer table manipulation inside Vibe, Dataverse tables are the supported option in the preview; SharePoint lists are intended mainly for quick reuse of existing list data without migration, with the trade‑off of read‑only behavior and column‑type limitations.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.