Power Pages WEB API | Perform CRUD Operation in Dataverse using Power Pages WEB API | Portal WEB API

foreign [Music] this is the 20th video of Power Pages 30 days learning challenge so if you are new to this learning series uh just wanted to give a quick introduction before proceeding uh with this uh new video this is the mentorship program I started this new year uh where uh I'll dive deeper into the power Pages components from basic to Advanced and we are learning uh how to quickly uh create a local no code Business website using the power Pages technology so if I just wanted to give a quick uh recap what are the components and what are the topics that we have covered till now so as part of this agenda we uh we are today we are on the 20th video where we're gonna discuss about the portal web API but if I just wanted to give a quick recap we discussed about the introduction of the portal components licensing and uh we also discuss about uh some practical things of the portals like how to set up a website what is uh how the designers Studios look like how to create a form to insert the data in the data bars how The List look like multi-step forms and we we had couple of sessions related to the designings as well like how to manage the content how to write the liquid templates code how to design the home pages uh how to customize the toolbars how to write the script so a lot of interesting stuff we have discussed till now some of the things we discussed about the integration perspective uh where we discussed about the SharePoint integration powerapps integration chatbot integration and the power via integration as well okay now today in this video uh I just wanted to give a quick background about the portal web API that is basically used to perform the crude operation on the data board so if uh if I just look back where the portal web API was not introduced so we did not add much component in the portal to interact with the data box so we we had only components that we discussed earlier like the forms that could be the basic form of the multi-step forms or the list so that was the only way we had the fetch XML as well that we could use it in the uh in the liquid templates or in the web templates but uh there was no way actually to update the data to insert the data accept the forms or the list okay so there was uh and there was lot of needs uh in the in the live project where I want to customize the page I want to create the subgrade HTML table I want to validate something or or I just wanted to have a control uh on the operation that I'm gonna perform on the on the on the dataverse okay so like we have the API already available in the data works that we call it as Dynamic 365 web API and uh that that API is basically the rest based API and support course and you can interact with the data Works using that API so in the similar way Microsoft has uh provided a web API called portal web API and that API gives you the flexibility uh to perform the operations uh with your custom code or your uh or within your auto box components also you can use that API and let's have a look uh you know what other uh an interesting fact about it so I'm going to cover everything about the power Pages web API here following with the live practical example how to use it and how to set up it all right now if I talk about why we use the power Pages web API so we should know the capabilities of it and all we should also know like what it cannot do it actually in the power pages so if I talk about the capabilities of the power Pages or why we use it so power Pages where VPI is basically used to perform the crud operation along with some additional option like associate and de-associate uh across all the Microsoft data was table from your portal pages okay so just one thing I would like to highlight here is it only performed the operation on the Microsoft data Works tables what it cannot do is it cannot perform the crud operation on all the power Pages related components so we have the power Pages related entities or the tables called content snippet basic forms uh the list uh the site settings markers so there are a lot of components we already been discussed about so it cannot perform the operations on the portal Pages tables it only performed the since these are all tables are part of data watch tables only but we call these tables as a portal tables because these are the table which actually uh store the configuration related to the power pages okay so that is a very interesting fact that you can only perform the operation only the data Works table not on the portal configuration table now what are the operations that it supports so it supports all the crud operations so it can create the record you can read the record it can update and delete the records and along with that it has the association a d Association as well so let's say we have uh you know any sort of relationship like one is to n or n is to one uh and N is to n as well so if you have to associate or de-associate the report sometimes then you can also use the web API for that purpose all right next is power Pages web API security so we have been discussed about the security a lot so if you haven't watched my earlier videos I would recommend to watch them all I'm going to provide the links in the description so I have discussed already about the security so obviously uh since the portal web API is going to perform the crud operation in the dataverse so there should be a proper Security in place so that we can control uh that who is authorized to perform the transaction on the data works okay so we we have the table permission that we already discussed about that can control at the table level that whether you can create the table sorry whether you perform the operation to create the data in the table read the data or update the data or delete the data so we have the table level permission as well but there is one more granular level of security that that Microsoft provides in the web API that is column level up security right so uh if you already have the table permission then you have to make sure that you have enabled appropriate column permission as well so it is no it is something like the field level security we have uh in the in the Dynamics but just wanted to highlight here is this column permission is only applicable uh for this web API it's not on it's not applicable for other features that you are using so for example if you are creating a form and you want like I want to apply uh the column permission on a particular field so that the user cannot access that field value so that is not for that purpose unlike field level security that is only for the web API so what column you can retrieve it from a particular table it actually uh decide that okay to understand uh it uh in more uh way uh I just created this diagram so you can see inside we have the Microsoft data works on top of it we have the portal builds so all the communication of the data basically happens with the Microsoft dataverse so first level of security you have the table permission so let's say you have the contact table account table so you just lock with the permissions like who can access these tables so if you have the access of these tables then you have the column permission enabled so for example you have access to read the date of or to the contact table then what uh you know columns you can access it doesn't mean that you have provided the table permission on the contact table you can access all The Columns of it right so probably you don't need to so let's say you have the first name last name and the salary so these are the columns you have enabled so you cannot access the salary of the employee so you can lock that with the column permission okay and on top of the column permission where we we have the web API settings as well okay so we're gonna have a look quickly like how how the web API settings look like in the Practical implementation but web API settings basically decides like which table or which columns uh you want to retrieve it from the data bars so if you can see uh this URL uh the power Pages training and uh Power portals.com after the API I have mentioned the table name that is contact and mention the the all the all the you know the the column name of the table like first name job title and the salary okay so in the web API also if I have to retrieve uh the the first name job title and the salary from the contact table so that I have to Define it in the settings first that on which table I want to enable the web API on which column I want to enable the web API so that is the first level of security so once you enable that web API feature on a particular table and on a particular column then on top of it you can provide the column permissions as well so let's see let's say I have applied the web API enable functionality on contact table that means I can retrieve the contact data and what column I can retrieve I have I have also mentioned in the settings like first name job title and the salary okay now uh that doesn't mean that you have provided the first name job title server in the settings you can retrieve it as well so you can read that of course because you have mentioned in the settings but option what other transactions like whether you can delete that field value whether you can update that feed value that you can decide using column permission so on top of it you have the column permission then on top of it you have the table permission so there is a three level of security you have before you can perform the operation of the transaction in the data bars all right awesome so we have the web API configuration step so that we also going to perform in the Practical session as well but uh just to remember uh what are the steps we have to perform in order to enable the web API for a particular table because I have seen there are a lot of folks uh are struggling uh with issues uh when they are configuring the web API they they set up everything but still they get sometimes resource not found error 500 internal error 404 not found error so there are a lot of Errors they they actually face it when they actually start using the web AP and the real-time implementation so configuration steps are basically very necessary to understand that which step is used for word purpose okay so the first step you have to create the web API site setting as I told you in my earlier slide you have to create the site setting to enable the web API for a particular table okay so let's say if I have to I want to retrieve the data of contact table so I have to enable the contact table for the web API so I have to create the site setting uh for that table first now for that table what column I want to retrieve it the second side setting is for the column so let's say for the you know contact table I want to retrieve first name job title and the salary so I have to mention this column name in The Comma separated form in this particular site setting or if you want to retrieve all the columns then you can put asterisk instead of mentioning individual column name so you should always avoid using asterisks unless it is really required but if you are if you are trying to retrieve any out of box table like contact account lead opportunity it has lot of columns that could be uh that could be confidential from the internal user perspective right so you should always avoid uh you know using asterisk uh if you if you have the custom table that uh don't have a much uh fields or the columns and that doesn't have any confidential value then you can anyways use the abstract sign all right so you have enabled the set settings uh for tables and the columns then the third thing is that you have to enable the permission so the table permission so let's say you have enabled so you have basically created the site settings for two things one is for the table and one is for the columns so you have to enable the permission for all the site settings so first you have to enable the permission for the table whether you can read create update or delete and then you have to create the column permission for the columns right because you have created two settings one is for column and one is for table so it's your duty that you have to perform the permission as well on on both the settings so let's say uh you have enabled three columns first name job title and salary but on the salary you you want only read permission create permission and on the first name and job title you want to perform all the current operation okay so you can Define in the column permission that which column uh you want to perform the read update and delete permissions and the last one is your script so once you enable all this configuration and uh enable all the settings then you are good to go and then you can write a script to call the API uh same like other apis uh that we have in the real time right so it's not a different thing uh or different way to call this API because this API is also a rest based API so the way you call the other external apis in your JavaScript code you can call this API as well okay but still I just wanted to uh give uh some basic information about this uh API URL that how your web API URL look like so let's say this is My URL uh the first part is your uh API uh Power Pages web API URL so the https power Pages training powerapps portal.com API slash so this is basically your power Pages where we pay URL it can be changed based on your configuration and the second part is contacts so that is obviously the column name sorry the it is the entity set name of the table so uh there are a couple of names of the table the first is The Logical name schema name and the entity set name so there are a couple of uh properties are there in the data bars for an individual uh component so for a table also we have the logical name and we have the schema name and we have the entity set name so here you have to use the entity set name so entity set name is nothing but the plural name of your entity okay so let's say if my table name is contact then the plural name plural name of that entity is the contacts sometimes it happens that you have created the table with already have S in the in the in the last character okay so for example if the table names ends with the S then you have to append the es uh in the name for example if the table name is events so we have already created the table with the prur name then your entity set name should be eventsis all right so you should always remember that this is your entity set name then the green one the first name job title and the salary these are the logical name of your columns so for lookup columns always you have to use the schema name so these are the some of the settings you need to keep in a mind and you always end up facing lot of issues because you always use a logical name but uh if you are using any lookup column in this list you should use the schema name I'm gonna show that uh quickly uh in the live example as well and another thing is that uh crfco published by underscore value so that is basically uh the lookup column so let's say you want to retrieve any lookup uh field so you don't need to provide uh the schema or The Logical name of the lookup field if you want to read the value of it you need to provide this uh the field name in this particular format the field logical name underscore value okay so let's say uh if the published by is the name of my lookup field so if I have to retrieve the value of it I need to provide underscore and the schema name sorry The Logical name of it and then underscore value okay now you may have the confusion because in the earlier step I told like for lookup columns you have to use the schema name and uh for uh you know uh for you know uh retrieving the the value of the lookup name I have to provide this syntax so basically there are two difference here so lookup is basically referring to the another table so if you are trying to insert the data in the lookup field you have to mention that look of field value as well okay so in that purpose you have to use the schema name of the lookup but if you have to retrieve the value of the lookup then you have to use this underscore value format okay I'll show you in the live example so that you will understand that where we have to use the schema name and where we have to use the logical name few more things and that is quite basic thing so if you have been using uh the web API URL or the old data then then dollar select is basically used to select or list down all the columns that you want to retrieve it from the datawverse table order is basically used to order the data in a particular order if you want to retrieve the data or if you want if you are creating an HTML table and you want to list down all the data in a particular order when you have to use the order tag filter is basically used to filter the uh the data based on the condition so as you as you can see it uh in the in the in the example I am just ordering it by the name in the sending order and filtering it by the revenue which is greater than the 90 000. and the top is basically if you want to filter so it's a typo here so top is basically used to get the top records of it so let's say if you want to retrieve the top three records or top five records only so let's say you are creating a dashboard on the on the power pages and you want to show the top 10 opportunities that I'm working on currently so you can use the top feature for that so ignore this text here because I couldn't change it so this is about the web web API URL okay count sometimes uh you just only wanted to show the count so let's say we are creating the event management portal and I just want to show like how many events uh have been published how many events uh I have registered for it so if I just only want to show the count of it okay so let's say you are creating the portal for case management and you want to see like how many open cases uh closed cases or resolved cases then you can simply show dollar count equal to true that will gives you the the count of the uh the data that is in the table okay now the last thing is the general data protection that is very important from from the gdpr perspective that whenever you make the request from the portal all the request header will have a contact ID passed for the auditing purpose okay so for the anonymous user this will be passed as a null but for the authenticated user it is it will always pass the contact ID who is making the request and what kind of transaction they are performing through the web API okay so if you have the auditing enabled in your organization you can track track that as well that how many transactions have been performed and uh which user perform uh the what kind of transaction so that you can do it from The Office 365 audit log as well so this is from the auditing purpose or reporting purpose if you just wanted to trace it uh that which contact is uh you know performing transaction from the portal so that is about that all right so let's quickly uh get into the implementation and uh and see like how the portal web API configuration looks like so this configuration cannot be done right now in the in the designer Studio because that is uh right now for the low code no code capabilities so all the kind of local no code components you can design it in the in the designer Studio but since it is it is one of the capabilities provided for the professional developer so you you have to manage all these things um in the portal management app okay so I have already opened the portal management app uh in a tab here and as you remember like if I have to configure uh you know the web apis first of all I need to create the site settings okay so my my use case uh for uh this example that I've taken today is I want to create a page on the power Pages site uh called manage events and I want to directly create the events I can edit the events I can delete the event so I've already created a event page called publish event if you remember if you have watched my previous videos but this time I just wanted to create a editable HTML table and I don't want to use any Autobox components to perform the crud operation because earlier I was using basic form and if you remember like in order to create the data I was using basic form but in order to update the data I was using list okay so that I could see the list of data and when I click on this so if I just head over to my portal here let me open the portal so that I could show you that what action actually I was performing so in order to perform the different different types of transactions I was using different different types of pages here so if you can see I had the publish event page so this publish event page was actually using to insert the data so it was creating the event but I cannot edit the data or list down the data from the same page I have to go to The View events page and here I could see the list of all the pages uh sorry list of all the events and if I have to edit that then I have to click here and click on the edit then then only I will be able to you know edit the data so there was so many clicks if I had to use the Autobox components to update the data delete the data insert the data but instead of doing that I just wanted to do everything all the operations from a single page so I want to create a table HTML table and want to perform all the cloud operation from there itself okay so I want to enable uh the web API for events page so publish event page okay now if I have to enable the publish event for web AP AI I need to know the table name so my table name is basically you can get it either from here so if I go to the tables or you can head over to the you know designer Studio go to the data workspace and you have this table called Power guide event so this is the table on which I am going to perform the crud operation here okay so if I go to the edit table properties you can check the properties of the table directly from here so this is uh we go to the advanced option as I told you every components that you created in the dataverse you have the logical name that is always in the lower case okay how you remember like uh what is the difference between schema name and The Logical name so I always remember with the keyword L because L stands for lowercase and L stand for The Logical name so this is the trick you can also use it because sometimes you forget like uh you know what is The Logical name so logical name is always the lower case of uh of of the display name okay of your schema name sorry because this schema name can have the some uppercases as well because it exactly copy the display name in the schema name so sometimes uh it has the uh you know the uppercase letters as well but you have to always use the logical name in the apis okay so this is The Logical name that we have to uh use it in my uh web API setting so let's head over to the portal management app and go to the site setting so the first step we're gonna create the site setting uh for uh the table so I have already created here so if I search web so this is the the first site setting I have to create it so this is I am just enabling uh the the table for a web API Cloud operation so this is the table name as I told you so I had copied from here exactly same sorry it's a logical so I exactly same I copied from here and paste it over here so web API the name of your table and enabled and you have to set it to true so that is that means I I can now start performing crud operation on this particular table so if you want to perform the current operation on other another table then you have to create a new site setting for that particular table so for each individual table in the database if you want to enable it for the web API crowd operation then you have to enable it you have to create a separate side setting for that now I have enabled it I need to I need to provide the details like what column I want to retrieve it or what columns I can use it as part of this web API so for that I have a separate setting called uh the name of the table and the fields and here I have to provide all the column name so here all the column name is basically The Logical name also so if I head over to the table and uh if I just click here so let's say this is the event name so if I just wanted to check the logical name of this column so always remember that you have to use the logical name so if I go to the advanced option this is The Logical name of this column so I have to use the same name here and in the comma separated form but this published Y is basically it's a lookup column okay so if I head over to the table again and check the published by column here it is since this is the lookup column so I want to use the schema name here see so this is the schema name and here p is capital and B is and also in the Caps right so for lookup column you always have to use uh uh the the schema name okay now why you need to have this schema name of it because if you have to insert the data you need to have the schema name of the data right if you are if you have the basic fundamental knowledge if you have to insert the data in the data bars using plugins or using custom workflows or if you are writing C sharp code you always remember that if you have to insert the data in the database you have to use the schema name okay but in the web API you always use the logical name right so if if you want to perform the insert operation using the web API so then you have to use the schema name here or if you just wanted to retrieve the data then for uh retrieving purpose this is the this is the name uh you have to use it for this particular lookup okay so crcfo this is the prefix published by is basically uh this is the you know the logical name of that entity and underscore value so this is the format you have to use it if you have to retrieve the value but if you have to insert the value in that lookup because lookup is basically referring to another table right so if you have to set the value in it you have to use this value so all the columns whether no matter whether you are performing any operation current operation performing whatever attributes you required in the web API you have to mention all the attributes in this particular format all right the third side setting that is basically the inner error so you have to create this side setting so that whatever error you are getting you will get the uh you will get the error message in the read in the user friendly format so sometimes uh the web API gives a common error message that you that that is not understandable that what exactly the error is but if you enable this inner error message that means it exactly gives the error message that you are facing so let's say if you do not have the appropriate permission enabled so that you can just quickly go and enable the permission for that uh so let's say let's say I'm just giving an example so you have not mentioned the event description field here okay but if you try to retrieve the event description from the from the code you will not be able to do that so you will get the error message that even description field is not enabled for this particular web API right so these kind of error message you will get it if you enable this site setting okay so these are the side setting you have to create it for each and individual table this side setting is is common for all but these two side setting is for the individual tables all right this is done now we have to head over to the table permission because that is the third step we have to do it so if I head over to the table permission I think uh if you have seen my earlier uh you know videos I've already uh created the table permission the security uh videos so if I just go to my website if you just see a event permission uh for admin I have already because I just wanted to create this table only for the admin because I want to give this privilege to the administrator only that they can you know manage the event not all authenticated user can create update or delete the event so I have created a permission here that on the on the same table I want to give the global privilege that uh you know you can read create update and delete but only for the sorry only for the you know the administrator okay but for the authenticated user uh for the rest of the users I don't want to provide the create option the right option and the delete option they can only read it uh but they cannot uh perform the create and update and the delete okay so that is for the rest of the authenticated user but right now I'm logging on the portal uh with uh the admin privilege okay so the table permission is done you have to enable the table permission as per your needs since I want to perform the current operation on this table so you have to enable the table permission for this particular table okay now the third thing is that we have to enable the column permission so column permission is actually optional it is not mandatory actually unless you have the specific need so let's say but I just wanted to give a quick uh introduction about it so if let's say I have created a column permission here and you can see it here that I have also mentioned in the my slide deck that these are currently available for web API features not for other features if you just wanted to use it so this is the column permission I have created so once I create the column permission I have two option either I want to give the uh I either I want to keep the you know access to all the columns so I can select here and select all that means for this particular table I can access all the columns okay but it's not a good practice actually I can provide the individual column permission as well so for this particular table I have created two column permission so for example for event name I can perform the create read and update and for published by also I can perform create read and upload if if I don't provide this by default it can create read and update but sometimes uh you have some of the columns and on which column you want to you don't want to perform the update or the delete right so in that case you can only create uh the column permission and provide them the create read and the uh whatever permission you want to provide so you can click on the new column permission here and you need to choose the column here whatever column it is there for that entity and here you can provide the necessary privileges okay so the only thing I just want to highlight here is all the columns that you have already enabled in the web API settings you can by default perform the read operation create operation and the delete operation update operation all the operation by default you can perform it unless you are providing any column permission here if you are providing column permission here then this guy this this Security will be applied on all those columns all right perfect so we have enabled all this settings as well now let's head over to the JavaScript part where we gonna write the code to perform the crud operation okay so what I'm going to do is I'm just adding it to uh heading over to the designer studio and click on the pages and I've already created a Pages called manage events under the events okay so events is basically my parent page and under that I have created a manage event page and on this manage event if I click on edit code I have written uh some of the HTML and the JavaScript uh to design a table so I'm not diving deep into that how to write the HTML code or css or the JavaScript to design the table you get plenty of examples on the internet okay uh to how to design the edit tables upgrade how to design the HTML tables and all so I just wanted to give you know the syntax of it how you can perform the ad how you can perform the delete operation and how you can perform the update operations so I just wanted to give the background about that and I'm also going to provide this code in my GitHub repository so if you just wanted to have a look into it you can also watch it from there as well okay I just created a normal table and now if I have to add the record if you can see here uh I if I have to insert the data uh I'm I'm currently taking three columns uh for uh demonstration purpose event name event location and the published wire so published Y is a lookup column right so I just wanted to give the example of Lookup as well so that you will understand where to use the logical name and where to use the schema name all right so I want to uh add the record and I want to insert the data only these three fields so when I insert it event name should go with the type event name and event location type event location so I'm gonna type it here but in the published y so published Y is basically my uh lookup column so since I want to insert the data in the lookup column and I have to you know Simpsons lookup is basically uh the table that is referring to the another tables okay so in order to insert the data in the lookup table or set the value in the lookup table I always have to use the schema name and this is the syntax I have to use it so this is the schema name of my lookup field and then I have to use this o data bind okay and this is the table uh for uh which I'm going to uh you know retrieve the data because this published Y is basically referring to the contact table so I want to set the contact table data so I'm sending the information that go to the contact table and find user.id so user.id you know like if I have to retrieve any logged in user information I have to use the liquid syntax called user because it's a object or it's a container which contains all the information of the logged in user and since if I have to set the value in the lookup field I need to set the unique identifier I cannot set the text value or any other value I have to use the unique identifier so I have to use the user.id that basically gives me the contact guid okay so I I'm just sending this information that set this uh in this lookup go to the contact table and find this guid and set to this lookup value okay and then the way you call any uh you know Ajax uh you know syntax or the way you call any external rest web API I'm using the same I am just calling this API so this is the URL sending the data in the application and Json format and then you know converting it to the you know Json and getting the record object and once I get the success message I am just adding the recording to the table okay so this is the syntax of uh you know the post message because I'm just inserting the data and here this is the delete example so for deleting I need to have a the guid of the or the unique identifier of the record so this is the syntax and I have to use the message called delete and this is the you know the URL I have to use it and the uh the ID of the of the record that I'm choosing it from the table okay one very important thing about uh you know this API URL is that I am using on the entity set name here in the URL as I told you that in the in the schema sorry in the web API URL you always have to use the entity set name and if you remember the name of my entity so the name of my entity is basically this so it already has the s in the in the as the end character so that means it's already a plural so I have to append Es as a additional character here to convert it to the plural value so this is this uh entity set name I'm using here and same goes with update so I need to choose or provide the the guid that I want to update it here okay so this is just a very simple example I'm going to post it on my GitHub repository as well you can just have a look at it because it is the same way how you call it any external web API so uh I'm not going to change anything here so let me cancel it and go to the preview uh to see like how this HTML table looks like so if you can see here under the events I have created a manage event so this is just a simple HTML table and uh so this is the retrieval I am retrieving all the events here and on on on hovering to the particular column I I get the option to you know edit it directly I get the option to delete that record and I get the option to add event as well okay so let's say if I add a new event here so it by default create the event with type event name type location so let's say I am typing the event uh let's say power page hackathon all right click ok so it got updated to hackathon event location let's say I'm just giving to angular India okay and since I have not refreshed the table actually so uh the data got inserted if I just refresh it I can provide the refresh option as well so yeah all right so if you can see here the published y has not been Auto populated so publish Y is supposed to be the logged in user okay so it should be Auto populated here but as you can see uh it was actually commented out and I didn't refresh the I didn't sync the changes so let me save this data and sync the changes here so you don't need to perform the query uh in order to retrieve the logged in user information uh you can get that information from the liquid template syntax called user.id and it always gives you the logged in user details so let me head over to the portal again and uh let's perform the delete operation first so that you can check that as well so let me delete this record so are you sure you want to delete all right so it got deleted let me add a new event and update that uh power apps hackathon okay location I just wanted to give India okay so this information got updated so if I just try to refresh the page you can see uh the arpit the srivastava which is the logged in user get automatically Auto populated here and now this new record got added and whatever operation I am performing I can see it in the View events as well so that is the out of box list components so now you can see here since I didn't provide other information on the grid so you can see here powerapps hackathon Pune so these details got updated in the Autobox list as well okay so this way uh I can perform lot of operations so this is just an example how you can perform the third operation in the portal where using the portal web API don't worry I'm just going to provide this code uh in the description link so that you can download this code or edit it as per your business need but the objective of this portal web API uh you know session is to let you know like uh how you can perform the uh the current operation in the dataverse and sometimes you need to you know validate something uh probably you may not require to perform all the operation in one go but the retrieval is one of the operation that you often use it sometimes you have to perform any complex validation you need to check it in the data Works table then allow user to submit the data so in that case also you can you can use the the web API okay so thank you so much for watching this video uh in the next video we have some more interesting stuff coming up so if you if you like this video just uh just put it in the comments if you have any questions related to the portal web API that also you can post it out in the comment I'll try to respond it back okay thank you so much take care bye

Channel: Arpit Tech Show

Views: 11,480

Keywords: #PowerPages, #MicrosoftPowerPages, #PowerAppsPortals, #Portals, #PowerPagesIntroduction, #PowerPlatform, #MicrosoftDataverse, #PowerPlatform30DaysLearningChallenge, #PowerPages30DaysLearningChallenge, #LowCodeNoCodeWebsite

Id: 5PwLZd_HE30

Length: 44min 45sec (2685 seconds)

Published: Mon Jan 30 2023