Michael Ghebremedin Dynamics 365 Notes

  Overview Developers of model-driven apps can configure notifications to be displayed to app users as  toasts  or within the  notification center . Here are some key points about Dataverse notifications: Automatic Polling : Your model-driven app automatically polls the system for new notifications and displays them to the user. Customizable Display : The notification sender or your system administrator can configure how the notification is shown and how it can be dismissed. Expiration : Notifications appear in the notification center until the recipient dismisses them or they expire. By default, a notification expires after  14 days , but your administrator can override this setting. On the other hand you can set expiry in seconds. User-Specific : Each notification is intended for a single user, identified as the recipient when the notification is sent. Sending a notification to a team isn’t supported; you must create notifications for each individual user. Ena...

Refresh DataFlow If you have an existing DataFlow and you would like to refresh it before its refresh time, one of the ways to use Power Automate Flow to trigger the refresh. After you have identified your trigger, all you have to do is use the Data Flow Action. Group Type : Environment or Workspace Group : is dependent on what you select on the Group Type, if you select Environemt like I did you will find your envoroment listed under Group. Dataflow : Name of you DataFlow DataFlow trigger If you have a scenario to run automation after a specific DataFlow has completed, you can use DataFlow Trigger When a dataflow refresh has completed The parameters are idential as the previous action. Thank you for reading :)

  The format for populate lookups as we know is: TableName(RecordId) In the latest updates of Power Automate Flow we have noticed few addition to lookups, these are the properties that are available: Table Name Type Value This will make it easy to populate a lookup field and save us time from searching the Table Name TableName(Value) In my example:Company Name(Table Name)(Company Name(Value)) One note this functionality so far is not available for existing older Power Automate Flows.

 How to Close/Resolve case from Power automate flow from your DataVerse Connector Add a New Row Table Name: Case Resolutions Subject: Add your subject here Case (Cases): incidents({Case Id Guid})

 Power Automate Flow Relate N-N records This is going to be a short and sweet post. To relate two records that are related N-N (Many to Many) you can follow this steps. In your Power Automate Flow search for Dataverse and select Relate Rows Table name   :- Entity Name Raw ID         :- Entity ID Relationship  :- Name of N-N relationship  Related with  :- Odata Id (Entity to be related)

Synchronous Power Automate Flow Error Handling In the previous article we walked through a scenario how to call a Power Automate Flow Synchronously. In this article we are going to discuss how we can notify the Web Hook when Power Automate Flow errors out or success  At the end of my Flow I have introduced a parallel branch and Configure the left branch to execute has failed has timed out  Once the flow errors the left branch is going to execute, we will execute a Response with Status code 400. when the flows errors out on save you are going to get the following error The error indicates that the webhook has error out, it enough for you to understand that the flow has errored out.

Synchronous Power Automate Flow   As we all know Power automate flow is an asynchronous execution mode. There is the question though can we execute Power Automate Flow Synchronously? The answer is yes. It will need a little bit of reworking and thinking. The idea is to create a Flow that we can control when to trigger it. What if we create a Web Hook and trigger the Synchronously. I have created a sample Power Automate Flow for this experimentation Create a Flow with HTTP Request Action Once you have saved the flow Copy the URL Open Plugin Registration Tool Register New Web Hook Register a new Step, I want this to execute on update of Account Entity on change of Description fiel Happy Coding 

  Power Automate Flow and Environmental Variables On my last blog I have shown you how to create an Environmental Variable in Dynamics 365 Solution. Now for the second part we are going to focus on how to consume or use the environmental variable in a Power Automate Flow. As you can see in the following image the environment variable will be accessible through the dynamic content, bare in mind you will be able to see the appropriate Environmental variable based the field data type you have selected. In this example we are creating a Task with Subject and Description populated by the Environmental Variables I hope this was helpful on how to use Environmental Variable inside a Power Automate flow, you can addopt this to your specific use case.

  How to deactivate Opportunity in Dynamics 365 with  Power Automate Flow   This is going to be a simple article, to deactivate an Opportunity in Dynamics 365 through power Automate Flow, you just have to create an Opportunity Close Activity record   Make sure Status and Status Reason are properly set. Opportunity = opportunities({Guid of Opportunity})  

Dynamics 365 Power Automate Flow Send Email In This Article we are going to describe a section of Power Automate Flow where we are going to create Email Message for Dynamics 365. Following this approach is going to make sure that the email message generate will be visible in our Activity Feed and the appropriate Email Message record are created in Dynamics 365 1.         Create a New Record a.        Entity Name “ Email Messages ” 2.        Set From, To, Cs and Bcc a.        You can not type email addresses on these fields b.        You are to create a reference to one of the following                                           ...

  Power Automate Flow How to Create Email Message with a Table of list of record.   If you are working on a scenario where you must include a list of records in an email, then I would say keep on reading. Let’s pick a simple scenario, when and account is assigned to a user lets send the list of Contacts associated to the account to the new Owner.   Our next step is going to be , to retrieve all associated Contacts to the account, we are going to use the List records action from the Common Data Service, I prefer to use the Filter Query if you are not comfortable with rest calls just go ahead and use the Fetch Xml Query you can use advance find to build the appropriate Fetch Query   Here there are two options you can take:   Call Create HTML Table and build your table Build a list then pass the list to Create Html Table I personally prefer the second approach, its cleaner, it will give you the ability to select which fields you want to in...

  Create Power Automate Flow that triggers on Demand Let start by finding When a record is Selected     Note :- This component belongs to the old Common Data Service, I have noticed you can use it with the new Common Data Service, which is good in my book.   For our example here we are going to select Accounts as our Entity, you can enter your environment under Environment, it will take the URL of the environment you are targeting. If you have any parameters to pass to the Flow you can select any of the following Inputs         Text         Yes/No         File         Email         Number         Date Text 1.        Add drop-down list options :- will give you the ability to add dropdown values 2.        Add a multi-select list option :- as it name explai...

I have seen a lot of complicated Power Automate Flows to handle Empty Lookup Values when trying to Update records. As you know setting a lookup field with empty value is going to cause the Power Automate Flow to error out. Example: Setting Lookup =   accounts() We are going to work with a scenario where we are going to retrieve Parent Account field value and populate it on another Account. To handle this issue, we are going to declare a variable that hold the Lookup Value (String)   Then we are going to analyze if the source record has Parent Account populated or not If the Parent Account has Value then we are going to set the variable with accounts(ParentAccount)   Otherwise we are going to set the value to null   The last thing to do here is to populate the field on your Update  This is going to save us time on our Power Automate Flow development and keep the flow clean and concise at the same time.