Skip to main content

Power Automate - Records modified during the last 30 minutes

Query operators

Recently I have been working on a requirement to query accounts and contacts that have been modified during the last 30 minutes in Power Automate.

Out of the box only the following time based filters are offered:



https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/use-fetchxml-fiscal-date-older-datetime-query-operators

So as you can see a filter "Older than X minutes", but no filter "Last X minutes" is offered.

Also the "On or After" filter only allows as to provide a date and not the time part into the filter:

So we have to be a bit creative, to solve this challenge.

Compose - Date Time in Power Automate

As a first step we use the Compose action and provide the following expression to calculate the current date/time minus 30 minutes:


And now it is time to define our filter expression to query all accounts, modified during the last 30 minutes:


Lets prepare some test data and modify one account:


Finally we test the flow. As we can see, the time minus 30 min. is correctly returned:


And the List records action returned our test account, that just recently has been modified:




Comments

  1. Nanfor IbéricaJune 5, 2021 at 8:24 PM

    Great articles and great layout. Your blog post deserves all of the positive feedback it’s been getting. PL-200: Microsoft Power Platform Functional Consultant

    ReplyDelete
  2. AvaNoahAugust 31, 2021 at 1:49 AM

    centered and descriptive articles written in this blog is surely very helpful for me similarly to for different who looking for such type of expertise. it is in reality going to grow to be useful in coming destiny. Power conditioner

    ReplyDelete

Post a Comment

Popular posts from this blog

Power Automate Get absolute Sharepoint URL from document location

Document Locations If you enable Sharepoint document integration in your model driven apps, you can define for which entities the possibility to upload documents to sharepoint shall be offered and you can define a folder structure. Possible folder structures can either be based on account or contact, which means if you create child items (e.g. opportunities, activities, ...) sub folders are created below. If an entity is enabled for document management a "Files" tab is added to the form of your model driven app and as soon as you click on that tab a folder is automatically generated on Sharepoint. Once the folder has been created you have options to create new or upload existing file or to open the document location (folder) on Sharepoint: What happens behind the scenes is, as soon as you click on the files tab your model driven app checks, weither a "document location" for this item already exists, or not. The document location is an own entity in C...
1 comment
Read more

Send e-mails with a link to the record via Power Automate

Today we gonna have a look at how to send an e-mail with a link to a CDS record via Power Automate. In the good old classic workflows, you could directly reference the "record URL" from the dynamic data. But since UCI has been launched and you have the possiblity to target different apps, you already had to do a few more steps in the classic workflows as well. The URL to a CDS record consists of multiple things: CRM URL appid entity name record id So we will work this out one after the other. First we add a "List record" action to lookup the appid of the app, we target. We look for "model driven apps" and filter by the name of the app: Then we initialize a variable with the resulting app id: Then we initialize another variable and extract the CRM_URL: Then we fetch our records, where we want to send out a notification with a link, in this case we look for workorders fullfilling certain criteria: Now we compose the record URL: As a next step we create a new...
2 comments
Read more

Working with Optionset lables in Power Automate

Connector Types Power Automate currently offers 3 different connectors, to connect Power Automate with your Dynamics 365 instance: Dynamics 365 Common Data Service Common Data Service (current environment) Today we will look on ways how to retrieve option set labels via the different connectors, for our sample accounts: Dynamics 365 This connector should not be used any more , since in April 2019 it has been announced as being deprecated. https://flow.microsoft.com/en-us/blog/nine-new-connectors-in-april-and-improved-visibility-into-trigger-failures/ With the Dynamics 365 connector it was quite easy to work with optionsets, since it offered both the optionset value (int) and the optionset label (name) in the dynamic content: And here we go, these are our results: Common Data Service Since the Dynamics 365 connector has been deprecated, this is the connector you should use. If you perform a "Get record" or "List records...
13 comments
Read more