If you are working with Power Pages Pro Code Development, you might need to access the current logged user Contact ID for various purposes, such as personalizing the content, saving data using the WebAPI and relating to the current user. In this blog post, I will show you how to do it via JavaScript in two different ways. Liquid to help To get the current logged user Contact ID via liquid we can to use the Liquid syntax {{user.id}}. This will return the GUID of the Contact record that is associated with the current Power Pages user. Liquid code as you might be aware needs to be used in a WebTe ..read more

I was doing some investigation on how I could automate some standard messages we send for my team related to some sprint tasks using Power Automate, and one simple requirement was to automatically detect the current sprint (iteration) name, to make an email content dynamic. The problem There is one action in Power Automate to get iterations, but it does not have a filtering option. We could leverage this one in combination with the Filter array action in Power Automate, but I was wondering if I could make it in a more performant way and with only one action. The solution Azure DevOps also ha ..read more

One limitation we have in Power Automate’s standard Microsoft Teams actions is the inability to send high messages flagged as URGENT on Teams. However, with the new ‘Send a Microsoft Graph HTTP request’ action, we can overcome this issue and send messages flagged as urgent in Microsoft teams, enhancing our communication automation capabilities within Teams and Power Automate. The Microsoft Graph Request needed & Action in Power Automate To send a teams message via Graph, you need to send a request body representing the chatMessage object. This object has an property named importance. When ..read more

When we use the Cloud Flows integration in Power Pages, we can use Web Roles to restrict what users can call the Flow or not. But sometimes only this is not enough and we might want to add more logic in the Flow to prevent certain actions. For instance, you can validate the Contact ID against Dataverse records to ensure the user has the right to execute certain actions. Check out how you can do it. Contact ID in the Trigger Every Power Pages user is mapped to a record in the Contact table in Dataverse. If we have a look at the properties that Power Automate provides us in the Power Pages trigg ..read more

Last week I demoed an improved solution of my previous blog post: Using JavaScript and Cloud Flows to download files from a SharePoint document library in Power Pages in the Microsoft 365 & Power Platform community (PnP) call. The Cloud flows are the same as on the previous post, but on the JavaScript side there were a few updates: Using jQuery instead of Vanilla Js Added more comments to the code Added option to preview PDF files on a new tab (be aware that you need to allow pop-ups in your browser for the site address for it to work) Source code The updated source code for the Power P ..read more

In my previous posts Creating and removing N:N relationship between Dataverse records using Javascript and Power Pages Web API I showed how we can leverage the Power Pages Web API to handle single N:N associate and disassociate requests for a custom N:N relationship between Accounts and Contacts, and also in the following post Generic JavaScript Functions to Associate and Disassociate Dataverse records using the Power Pages Web API, I brought revisited versions of functions to handle the Associate and Disassociate process for any table. In case we want to handle multiple requests, we need to d ..read more

In my previous post Creating and removing N:N relationship between Dataverse records using Javascript and Power Pages Web API I showed how we can leverage the Power Pages Web API to handle single N:N associate and disassociate requests for a custom N:N relationship between Accounts and Contacts. In case we want to extend that to be more generic to any N:N relationship we can leverage a custom function that can be used in multiple pages easily. Prerequisites All required fields (including the N:N relationship name) in the code must be enabled for the WebAPI for the Power Pages site where you w ..read more

Managing Dataverse N:N relationships between records using the Power Pages Web API can be trickier as there are few samples around and the syntax differs a little bit from handling N:N relationships using the Dataverse Web API. In this post I will show a quick code sample on how you can handle that, using a sample N:N custom relationship between Contacts and Accounts. Prerequisites All required fields (including the N:N relationship name) in the code must be enabled for the WebAPI for the Power Pages site where you wish to run the code creation via Web API The WebAPI Wrapper code must be adde ..read more

This post is based on a recent question that I got from a blog reader in a blog post related to List Formatting and setting field values: I am trying to add an action button to my Microsoft list. The reason for this is that I would like the trip date column to populate with the current date the button was pressed. Just to make it easier for the executives to confirm they have completed a work trip. Can this be done thru list and conditional formatting and json coding? We can use the customRowAction attribute with the setValue action type in list formatting to achieve this. Basically we need ..read more

Even though we can now use Virtual Tables to expose SharePoint lists in a Power Pages site, the same does not apply to SharePoint Document libraries. You can use the native SharePoint integration to display content that was set up in that way from the Model Driven Apps side, but you cannot expose a custom library in that way. For example, if you want to expose a random library with Document templates for users to download, there is no simple way by using out-of-the-box features. However, you can use the new Power Automate integration to leverage that, by creating a custom Page and manipulating ..read more