Moving SharePoint Based Power Apps to Dataverse for Teams
HTML-код
- Опубликовано: 2 авг 2024
- #PowerApps #SharePoint #DataverseForTeams
Considering moving your SharePoint based Power Apps to Dataverse for Teams? Learn the key differences and decision factors between SharePoint, Dataverse for Teams and Dataverse when choosing a data source for your Power Apps and Power Platform solutions. You'll see a demo of how you can import a SharePoint Lists structure and data into Dataverse for Teams with Data Flows and how we can export and import a Power Apps canvas app into Dataverse for Teams with solutions.
Table of Contents:
00:00 - Intro
00:46 - SharePoint vs Dataverse for Teams vs Dataverse
09:49 - Importing the SharePoint List Data
14:27 - Importing a Standalone Power App
17:52 - Adding the app to Teams 
Наука
Wow! I'm seriously impressed with all this new import functionality we now have, thanks for the video!
You're very welcome - I was super impressed with it too so I had to share :)
Google exactly landed the search to the correct video… thanks April
Good job Google! 🙂
I had to revisit this vid because Matt Devaney twitted why one should use Dataverse forTeams instead of a SharePoint list 😊
Great overview and love the way Microsoft is going. Thanks April for your guidence!
You're very welcome. Thanks for watching!
Thanks, April, very happy I was actually able to try this thanks to your guidance! My question is about relationships between existing datasets as you import the tables via Dataflows, so that you can fully leverage D4T in the transferred app. I have a 1-many relationship with a text string key, but I'm not sure how to map the text field key in the "many" table as a lookup to the "1" table. I have gotten the RELATE function to work (post import) for individual rows, but haven't gotten that to work with a FORALL and so am trying to come up with the right approach for a few thousand rows, do you know what that might be? I could be a bit spoiled by data modeling in Excel PowerPivot where you can just draw a line in diagram view ;-D
Hi April - Great video. Many thanks for sharing.
Thanks for watching!
Awesome and informative as usual !
Thank you!
Really clear and helpful , thanks!
Glad it was helpful!
Great video and Great news.. Got so excited when i first saw the video and just had to start right away only to find out that the feature is NOT available in our region yet (Europe,Greece).. Thanks Microsoft
Sorry to hear it's not available in your region yet. It's a public preview so it might take a bit to hit all regions.
Great video April.
I have one concern when moving this to Dataverse for Teams. If we have a Power BI report or a Power Automate routine we will have to update everything. This seems to be handy for small apps that don't have integration with other Power Platform tools.
It's awsome :D, thanks for great video
Thanks for watching!
Thank you April!
You're welcome!
Great content but sadly i do not have the "Dataflows (Previev)" tab on my apps list seen on 11:05. Am i missing something? My tenant is located in Switzerland.
Hello April congratulations for the video. I created a small test app with a table and published it to a team that I owner. What do my colleagues have to do to access and what kind of license do I need? Because we all have the same corporate accounts, but they are required to open a license of power apps trial or premium. Thank you. Michele.
One of the odd quirks about DV4T is that everything, by default, ends up in the "Common Data Services Default Solution". However, from the "See all" link, there is an option at the top to "Open in Power Apps". That provides you with a new screen that gives you the ability to create new solutions. The devil is in the details, though. If you put your stuff in a different solution (other than Common...), you won't see it back in the "see all" list anymore. That list only shows things in the CDS Default Solution. So... to be able to edit your apps, they also have to reside in the CDS Default Solution. Weird, but seems to be no way around this.
Hi, April - thanks a million for this; greatly appreciate your patient step by step explanation. I notice that when I'm importing my Sharepoint List, all the data types come over as text, and I don't seem to get the option to change the data type for any of the imported columns. For example, in the original Sharepoint list, a column that is number comes over as text, and in Dataverse for Teams I'm not seeing an option to change that back to number. Is there something I'm missing?
When you build your data flow and you are in the Power Query editor, you can click the little "abc" or "abc 123" icon in your column header (second power query screen) and select the data type. You can also, for complex columns like a person column, click on the double arrow icon on the right side of the column name. click it until you are presented with a list of values to select from. For person, pick title and email, then check the box at the bottom "use original column name as prefix". Now you will have two columns for that person column, one for display name and one for email address, that you will pull into your dataverse.
Cool that's an awesome demo. Do you have any video that shows difference between canvas vs Model apps and when to use them?
You're welcome! Yes I do. Here is it: ruclips.net/video/M_tvnAmHMZY/видео.html
6:37 2g limit per Team site? or per Table? For Dataverse Full version, is it suggested that every project or developer get their own Environment? does that environment require separate licensing? same access AD groups? There is a role to enable a user to manager all role permissions (even at table level) ?
Also, why does DV4T require me to first create an App before I can create Tables? That seems like a bug.
For some reason I am missing Dataflows link - Is there something else I need to do?
Your instructions have never failed me before. I am on a GCC tenant, with what looks to be a standard license. I am receiving errors when trying to create the Solution portion. Does creating a Solution require a Premium License?
Very useful info as usual. BUT, I'm having a problem understanding something that no one seems to be addressing.
The technique of importing the SharePoint list data into Dataverse for Teams is easy enough, BUT(!!) the newly created in Dataverse doesn't look anything like the SharePoint list fields in your table. ALL fields in the new Dataverse table are "Text" fields. One can have images, choices, date fields etc. Those aren't text fields.?? How is that new Dataverse table even usable for inputting data via the Powerapps app??
I think that’s part of the power query step if I’m not mistaken. You have to set the column types.
How did you do the time visualizations with the circles behind the time ? Power BI ?
Hey! That's actually all done with native Power Apps functionality. I show how I did it in this video and there's a link to download the app: ruclips.net/video/S-YUearXrBA/видео.html
@@AprilDunnam Thank you! I’ll check it out!
For anyone getting Authentication loading continuous spinning in Dataverse for Teams, you need to click the Open in Power Apps button at the top when you see it.
Thanks for calling that out!
my only concern is database size only 2GB, with image it will expand quicly
That's a valid concern and one of the reasons I made sure to bring up the capacity comparison. I've seen a lot of people using Azure Blog storage to handle images or just going to the full version of dataverse
@@AprilDunnam that's a good point, and I would also mention if Azure Blob or full Dataverse is not an option, you can still leverage a SharePoint library outside your 2GB Teams environment for big files etc, while keeping the metadata associated with the files in D4T. I liked the way @ThatAPIGuy did this -- ruclips.net/video/_vKzIy4jF8c/видео.html
@@derek_shannon Yep Vivek had a great approach there!
april , when you changed the Sharepoint list table for dataverse table, power apps automatically change all formulas inside application?
or do we need to do it manually?
Hey there - It depends. If you set up the new dataverse table the exact same as your SharePoint list (same name, column names, column types, etc) then it *should move over fine when you update the data source and your formulas are ok. But if there are any differences you will need to change your formulas.
@@AprilDunnam Thank you, Very clear.
@@AprilDunnam Thanks for clarifying that, April. I'll have to try it, but when you said in the video, "So that we can make any changes we need," it brought back memories of trying to convert from Excel to Lists and all the headaches that entailed. BTW, that might make a good topic for a video someday, going into the nitty gritty of actually handling field name changes and schema changes and how to handle the sometimes confusing error messages.