hi everybody in this video i'm gonna show you how to create a powerapps for teams application using dataverse14s as a data source we will explore the different functions and operations and you will compare that with an application using dataverse the full version so let's start with this video [Music] okay so let's start reviewing our powerapps application that we have created on teams in this particular case we are using power apps for teams and the data source is database for teams just to explore the design of this application you you need to access to teams you need to search for your powerapps application here if we click here you will see that it will open an interface in which we can create new apps for teams and you will be also be able to see the apps that you have recently created okay so from here you can create a new app you see your recent apps actually the app that i have created is this one or you can go to build and in build you will see for example the different teams you have created and that are particularly associated to an application that you have created my teams is this one mws demo team and here you will see the different components that are part of my application for example here we have the different tables those are data verbs for teams tables and here is my powerapps canvas application if i click here i can open my application in design mode and we will be able to customize this application okay so here we have our powerapps for teams application you will see in this section that we have all our databars for teams tables if you want to create a new table you can easily do that from here you can click on create new table you can specify the name and customize your table as needed if you want to customize for example any of the existing tables for example the courses table you can click on here and edit table and you can easily add new column for example if you want to add a new column you can easily do that from here and you can select also the different data types right something that is interesting is that in comparison to the full version of database like the premium version you won't have all the complex or advanced data types right you have a limited number of or existing data types and you won't have other advanced capabilities like for example security at the record level or security at the field level you won't have auditing at the field level as well so there are some specific advanced capabilities that probably are more complex or critical application will need however in this case for example for small applications or productivity application probably these field types are going to be enough you can also easily update the values of your table you can add new rows you can show or hide columns and in terms of relationship is the same right you can create relationships between between those tables so we are replicating the same data structure as we had in our powerapps application that uses dataverse as the data source in terms of screens we have the same screens if we have replicated also the same screens here something interesting is that if we go to the section of controls you will see that obviously it will has a limited number of control type we won't have all the capabilities available in in powerapps canvas up for example things like shapes you have yes on shapes but you don't have all the variety of shapes available in thunder power-up campus app but basically you will have the most common control so with this probably it will be enough for you you can add forms you can add galleries you can add tables as you can see here right i have a table here and i have the information that i need okay it is just a test that is that this is working perfect now let's explore the the filters right a great news in this type of application is that all the functions that are deliverable to database are also delegable to databars for teams so you won't have the litigation issues if you look at the filters for example here and remember the way we configure our combo boxes is very similar to the way we did on database we just need to specify the table name in the items property so it's exactly the same in the filters if we go to review the filters we will see that the functionality and the filters that we are applying here are the same actually it's very similar we are just specifying the the correct table name as well as the correct table fields but the filters are the same and we don't have any delegation warning here if we go to numeric filters as well you will see that we don't have delegation warnings and the filters are the same we just change the the name of the table but the expressions the filters the operations are exactly the same the same is going to happen in date filter for example right remember that the advantage of dataverse is that we can apply filters by date which is something that by default is not possible in sql for example remember that we had to create a calculated field but in this case we don't have to do that and the the function is exactly the same in the case of text filters it's working equally we haven't done any any additional change the filters are the same and all of them are delegable and the same is going to happen with the search function and right you can see here that obviously the only change that we need we had to make is in the internal name of the of the contour if you want to know which is the internal name of the control you just you put comma and you will see the different internal names but the the functionality is gonna be the same even if we go to operators remember that in operators there is a delegation warning right because we can use the type this type of operators in our filter expression is not delegable so this is the same delegation warning that you have in dataverse so it's exactly the same functionality now some interesting considerations here because you will see okay most of the functionality is basically the same in terms of delegation right you will be able to basically replicate the same functionality and delegate the the same functions and have good performance now remember that there are some restrictions in terms of capacity right for example that one database for teams environment will have a capacity of up to two gigabytes of data or up to one million records obviously if you compare that with database you have up to four terabytes of content so it's like the the capacity of dataverse is significantly more than in database for teams another interesting consideration as well is that each time you create a new teams and you create an app for a teams there is going to be one environment associated to that or to that team so each team is going to have an environment right if you would like to to see that you basically can go if you are obviously if you're an administrator you can go to the admin portal you can go to the admin portal and you can go to all administered centers and access to the power platform administration portal or administration center and from here you will be able to select the microsoft teams environment in this case you will see that the the environment type for example i have created this trial environment which is the environment in which my solutions are and applications are hosted but in this case there is an environment of microsoft's teams type and if i click here obviously there are some configurations i can do from here something interesting is that you can upgrade this database for teams databases database premium versions so that's the reason of that is that you can start with a small application right but then your needs can increase you you could have additional demand you can have additional users or more information and you you require additional functionality security functionalities a better performance so you have the possibility to upgrade and from here if you go to powerapps you can see also the the application that we have created in teams here is the application we can click here and we can open the the application in the browser also it's important to review the documentation in the documentation you will see the difference between database for teams and database so not only consider the delegation warnings or the delegation issues that you can have because you will see database for teams and database in terms of delegation is going to be the same but you need to evaluate also the different features and capabilities and restrictions as well so if you want to look at the differences you will see that there are a lot of additional features available in the full version of database for example advanced data types so if your application is more complex and you need more advanced data types it's better to go with the default version of databars in addition to that there are some capabilities related to business intelligence there are some limits you will see that you can the maximum size of a database for teams is one million rows or two gigabytes right and you have one environment per team and also in the case of data version you can store even more than four terabytes of content so the capacity is also something interesting and important in terms of security there are a lot of security capabilities available in the full version of database that are not available in database for teams as well as integration capabilities right so database for team is a great option for citizen developers to build applications and quickly build solutions for teams for projects for small productivity applications but for more complex scenarios for most important or critical scenarios it's important that you consider other options like databars or okay guys i hope you like this video in our next video we will explore our last data source sharepoint online so remember that if you like this content subscribe to the channel and if you have feedback or recommendations on what would you like to see in next videos please put your comments below bye [Music] [Applause] [Music] [Applause] you