The SharePoint Guru

This also applies to other TimeZones. When you query SharePoint in Power Automate using steps like "Get Items" the raw information that is returned when you are working with dates and currently inside British Summer Time will be out by an hour. Below I've created a step which runs Get Items and I add a compose to check the Created date: Going into SharePoint you can see the date time returned is an hour out (I'm currently inside British Summer Time and my laptops date/time is set as such). Whenever you are handling dates from SharePoint in Power Automate you have to remember that the original value stored in SharePoint for date/time is the UTC value. Depending on your regional settings the value is converted for you when it's rendered. Fear not! Power Automate has conversions, here's one way: In the example above I'm taking the source Created date/time which is in UTC and converting it to my location - Dublin, Edinburgh, Lisbon, London. The expected Create

Something I found relatively difficult to find online is what to do when I have two tables and I want to create a many to many relationship but additionally hold extra columns about that relationship. When dealing with regular databases you would create a join table (intermediate table) which would hold a one to many relationship between tables: Creating a many to many relationship is pretty straight forward in Dataverse and there is an out of the box relationship builder to do that, however any joiner table is hidden and you can't customise this. This guide explains a really simple way to hook the joiner table up, as when I tried to make the one to many relationships manually and add data using a model driven app, the relationship wasn't being recognised. Some Background My example takes a very simple "Building Project" log book which is to hold information about building jobs and the contractors associated to that job. The contractors will be coming from the default