How to keep flows remain on if the flows don't run for 90 days

-

This is a common requirement in power plat form world, flows turn off after 90 days if they don't run. We can address this issue by writing a scheduled flow and run every day. 

I will explain how to write this flow. 


Start with by selecting a schedule flow.




Select Power automate management connecter- List flows as admin(V2)




Once you select it will ask you to create a connection then Select your target Environment


Next we need to filter the flows which we want to turn it on, Here I am using a unique display name which you have common for all the flows you want to check. In my case I am using "-Production-" to filter down the flows. 

Select the value from the list flows




Select edit in advance mode and enter the below expression


@and(equals(item()?['properties/state'], 'Stopped'),contains(item()?['properties/displayname'],'-Production-'))



In the next action, select apply on each , Select the output value from the filter array, Select the same Power automate management connecter - Turn on flow. 



Select the Target Environment and put the flow name Custom value- select flow name from filter array.



Now all done, Run the flow and test it


Thank you for visiting this blog 🙏. 

Comments

Post a Comment

Popular posts from this blog

How to update 100000(hundred thousand) records with power automate flow by using chunk expression, Split the list and pass onto child flows.

-
Image
The Dataverse connecter returns up to 5000 rows by default, We can increase this up to 100000. To get more than 5,000 rows, turn on the Pagination and set the threshold up to 100,000 in Settings If you have more than 100,000 rows to process? you can get more than 100,000 rows from Dataverse, use the skip token to send another request until the skip token returns empty When we have thousand of records to update instead of doing list down the records and apply on each, I have approached this slightly different here.  We will build one parent flow and 4 child flows. So that we can divide the whole list into 4 identical list and pass on to child flows. This approach significantly reduces the time to update the total records.  Lets jump in and build a flows! Based on your requirement you can choose the type of flow you want, for example purpose I am using Schedule flow.  Since I am using the current date to filter down the records, I am initialize and format the date. use the ...
Read more

D365 CRM-Change Entity translations(Sub area) in Modern driven app.

-
Image
  Have you ever tried activating language packs in D365 CRM and tried to change the Entity names in Modern driven app? Normally When we activate the language pack for your preferred language Microsoft default translates all out of box entity names. If you want to change the translations for existing ones or create new for custom entities we need to update the translations.  You can enable the language pack under Administration>Languages Open the Modern driven app editor in classic version, select the Entity name you want to change the translations Select the language you want to update the translation and delete the existing translation and enter the new one.  Now the new translation name is updated.  Note: We cant update custom translations for recent and pinned fields in the left navigation at the moment. This is limitation from the Microsoft side at the moment.  Thank you for visiting this blog 🙏
Read more