Unanswered

Exporting dataverse/CDS table to SharePoint list

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hi all,

I have a powerapp which allows users to submit information about tickets they have been working on throughout the day. That information is stored in the dataverse because the app is built and runs within MS Teams. I was just wondering what the best way of exporting all the entries/rows into a SharePoint list is?

I know I will probably need to use PowerAutomate but can anyone guide me how to do a bulk transfer of all the rows which have already been collected?

Thanks,

Freddie

Categories:

General topics

All responses (4)

Answers (0)

Sort by

DamoBird365 8,942 Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Anonymous

This is relatively new in Teams Dataverse and assuming that is where you are? You can click on the elipses next to the table within PowerApps in Teams and Edit in Excel.

Alternatively if it is in your main environment, you can do it from PowerApps Portal -> Tables.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Cheers,
Damien

P.S. take a look at my new blog here
mahoneypat 1,720 on at

Like
a
(1)

Report
Copy link

Link copied!

I agree you could export your data to Excel and then import or copy/paste that into SharePoint. You could also create a flow in the same environment with your Dataverse/DataverseForTeams table and use the List Rows action (see Advanced pull down to specify only the columns you want). You could then do an Apply to Each and create a new SharePoint list item for each row/record.

Pat
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for replying Damo. I don't seem to have those options under the ellipses for some reason.
DamoBird365 8,942 Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Anonymous

If we are talking Teams Dataverse, it's a new feature. Have you tried accessing this via Teams in the browser as it may be more up to date? Otherwise it may be that the feature is still to hit your environment.

Damien