Skip to main content

How to deactivate Opportunity in Dynamics 365 with Power Automate Flow

 

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})

 



Labels

Labels:

Comments

  1. AnonymousMay 15, 2022 at 2:53 PM

    The title of this article is misleading as you aren't deactivating the record, you are simply closing it

    ReplyDelete
    Replies
    1. Michael GhebremedinMay 19, 2022 at 8:28 AM

      When you Close the opportunity it automatically gets deactivated

      Delete
  2. AnonymousMarch 3, 2025 at 11:27 PM

    I am getting this issue
    Action 'Add_a_new_row' failed: URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL.

    ReplyDelete
  3. AnonymousMarch 3, 2025 at 11:31 PM

    Thank you for this valuable post

    ReplyDelete

Post a Comment

Popular posts from this blog

How to use Formatted Values in Power Automate Flow Dynamics 365

  How to use Formatted Values in Power Automate Flow Dynamics 365   If you have been working on Power Automate for Dynamics 365 you might have been wandering how you can access a lookup Formatted Value or Option Set formatted values. You can use the following format to access: body(‘{Action Name}’)?[‘{fieldname} @OData.Community.Display.V1. FormattedValue’] You just have to be mindful in Dynamics 365 lookup field name they do not translate to the proper field name, you might have to and an “_” as a prefix and “_value” as a postfix, I will leave that to you.
Post a Comment
Read more

Azure DevOps Fork Repos between two Organization

  Azure DevOps Fork Repos between two Organization This weekend I embarked on a topic a bit foreign to myself, on the surface seemed a bit simple. The idea is to fork my Azure DevOps Repo to a different organization and push changes between them. Bad news DevOps doesn’t allow to fork Repos to a different organization, you have only the capability to fork to a different Projects within the same Organization. I’m pretty much sure there are so many other ways to solve this issue, but this is the one that I found to be easy to implement. Import Repo to the new Organization Remember here you have to generate a personal token to be able to import the Repo you have to be a member of the new organization as well This might take a few minutes depending on the size of your project, once its complete you will receive a confirmation email, or just refresh it after few minutes So far all looks good, you can clone the solution in your new Organizati...
5 comments
Read more

How to Close/Resolve Case in Power Automate Flow

 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})
5 comments
Read more