Opportunity owner update failure in the UI

Opportunity owner update failure in the UI

When an opportunity owner is tried to update "1 opportunity failed to update" error is shown. Whereas when the owner is updated via API it is successful. 
 
This happens because of the duplicate detection rule. If there are duplicate opportunities then the update is not possible in the UI.
The three workarounds are as follows:
  1. Clear the duplicate opportunities.
     
  2. Disable the duplicate detection rule and update the owners.
     
  3. Perform update operation via API.


    • Related Articles

    • Opportunity import error | Updation | Import restrcition

      Issue reported: When trying to update opportunities using the opportunity import function, the following error is displayed in the import report as shown below. Import parameter to be noted - Overwrite duplicates. Error message - "Creation of new ...

    • Task owner in opportunity page and in manage task page can be different

      Hi Team, There can be a possibility where the task owner in opportunity page and in manage task page can be different. Reason for this issue:- If the the user Name, Email and phone number everything will be changed for any user who is task owner, ...

    • Automation Cards Failure email alerts

      The Automation Failure notification will trigger only those who created the automation and who modified the automation. Please note all the users who modified the automation will get the automation failure notification (e.g.: if user-a modified the ...

    • Filter and search only opportunity fields in form rules

      Problem: Currently if you try to search form rules containing a particular opportunity field in the search bar, it does not yield any results. This is a bug and will be fixed in upcoming releases. Workaround: Remove the opportunity code in the search ...

    • Unable to update the distributed owner's name in the automation

      Issue: Customer was using an automation to update the assigned lead owner to the specific field. RCA: Customer was using incorrect mail merge for the owner (@{Owner:EmailAddress ,} @{Owner:FirstName ,}), because of which was values are getting ...