Dynamics Community Forum Thread Details

Opportunity Close as Lost errors and how to find "Legacy" Command Buttons

Hi, and thanks for your help.

With some Opportunities but not others when using the Close as Lost button we are getting the following error:

Action could not be taken for few records before of status reason transition restrictions.

ErrorCode: -2147160050
HexErrorCode: 0x8004f00e
Error Details: {"ActivityId":"","errorCode":2147807246,"message":"Action could not be taken for few records before of status reason transition restrictions.","stacktrace":"","Timestamp":1760539715869}

Activity Id: 2069e678-053c-42ec-be21-6274faebd3d4

When I tried to find the flow that is triggered by that button I see in the Command Bar Editor that the Close as Lost button is "This button is read-only. Legacy button is not supported at the moment".

Yet, I'm sure that this process was customized by our (no longer available) consultant and is not just legacy out-of-the-box.

Where can I find the process that is triggered, and the execution log that will show where it failed?

Thanks!

Categories:

Dynamics 365 Sales

Is it possible that this Opportunity is linked to another record, like a case, that is being closed when the Opportunity is being closed? There is actually a setting specifically for Status Reason transitions available on some tables in CRM. It was never widely used in my experience, and I think you need to go to the classic editor of a table to update it.

Define status reason transitions with Power Apps - Power Apps | Microsoft Learn

Open the default solution in your environment from https://make.powerapps.com
In the top ribbon, click on the "..." menu and choose "Switch to Classic"

In the left menu, expand the "Entities" list and find the listing for "Case"
Open the "Fields" sub-menu under Cases, and find the Status Reason field. Open the settings for the field
Find the "Edit Status Reason Transitions" option in the top ribbon and review it or remove the restrictions if necessary

The button being shown as "Read-Only" in the new PowerFX Ribbon editor is not unexpected. Most of the existing ribbons are still considered "Legacy" buttons and can't be customized with PowerFX.

Quick Links