web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Unable to close opport...
Power Automate
Answered

Unable to close opportunity as WON/LOST using flow

(0) ShareShare
ReportReport
Posted on by 84

Using Flow, i am creating an opportunity and then as part of soem other logic, i need to close the same opportunity as WON/LOST in the same flow .

However i get the error

{\"error\":{\"code\":\"0x80040216\",\"message\":\
"This message can not be used to set the state of opportunity to won. In order to set state of opportunity to won, use the won message instead. \"type\":\"Microsoft.Dynamics.Solution.Common.CrmInvalidOperationException.

 

I have been using three fields to achieve teh same

1 actual close date

2. status (WON)

3. status reason (WON)

 

KIndly assist.

Categories:
I have the same question (0)
  • Ed Gonzales Profile Picture
    4,531 Most Valuable Professional on at

    @Rkaur 

    Hi there!

    What does the rest of the Flow look like?  Are all of the required fields in the opportunity filled in?  Closing an opportunity has a few sub-jobs so D365 (assuming that's your CRM?) may be yelling at you because of that.  I did see this in the ideas side, so I'm wondering if it's not totally possible yet.

    Show us the rest of the process and we'll see what we can do. 🙂

     

    -Ed-

     

     

    If this reply has answered your question or resolved your challenge, please consider marking it as a Solution. This helps other users find it more easily via search.

  • Rkaur Profile Picture
    84 on at

    Hi Ed,

     

    Thanks for your response.

    So, when we close an Opportunitya s WON/LOST from CRM UI it also, it only takes the three fields i mentioned above which are auto populated there except for the status reason.  Hence, i mapped the  same fields in my flow with the status reason as WON/LOST.

    if there was any field missing it gives some other error to help identify.

     

    But this error, im just not able to decode "In order to set state of opportunity to won, use the won message instead" What does won message mean?

    IN other discussion forums i came across an API "LoseOpportunityRequest()"  https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/164822/how-to-change-opportunity-entity-status-as-lost

     

    so does it mean that even when using c#code instead of updaterecord() method there is another method used to close opportunity. And if thats the case then thiss functionality may be hasnt yet been brought into FLows.

     

    Would you have any idea around this ?

  • kcpacker85 Profile Picture
    36 on at

    Any update on a resolution?  I'm running into the exact same issue

  • Rkaur Profile Picture
    84 on at

    Hey.. theres no solution to this. its left open for me as well.

    if you see the reply from Ed, he pointed out to ideas forum where the exact requirement has been mentioned.

    so propbably we can just wait until teh solution comes or we may need to figure alternate way for now to make it working.

  • kcpacker85 Profile Picture
    36 on at

    Ok thank you @Rkaur 

     

    I also initially thought that I needed to set status values within the 'opportunity close' entity along with the 'opportunity' entity.  I tried every combination of running the flow with parallel steps, setting opp status first, setting opp close status first, etc. and still same errors.  Very frustrating this can be done through a crm workflow, but not within a flow.

  • Ahmet_Göker Profile Picture
    8 on at

    @Rkaur @msm8504 @edgonzales I have had the same problem but found the solution at the end of the day.

    First you need to create your opportunity without setting or updating your status. Just leave it empty

    Screenshot (102)_LI.jpg

    Second: You need to create a Opportunity Close activitities. With the created Opportunityid. From this point you can set your Opporunity status.

    Screenshot (103)_LI.jpg

  • Community Power Platform Member Profile Picture
    on at

    Hi! 

     

    I have the same problem and I've tried your solution with adding the Opporunity Close Activities, but I still get an Error Message. 

     

    In my flow(Power automate) the opporunity will be "Closed as won" after the manager have approved some documents and received a confirmation email. The Erreror message I get is: 

     

    {
    "error": {
    "code": 502,
    "source": "europe-002.azure-apim.net",
    "clientRequestId": "3b7277d4-ed2e-4121-8b70-038b273ec715",
    "message": "BadGateway",
    "innerError": {
    "status": 502,
    "message": "--batchresponse_dce3e803-f50b-48eb-931a-1fe0cee85858\r\nContent-Type: application/http\r\nContent-Transfer-Encoding: binary\r\n\r\nHTTP/1.1 500 Internal Server Error\r\nREQ_ID: fcafe468-d2c9-4efa-bfa2-a2eff1b454aa\r\nContent-Type: application/json; odata.metadata=minimal\r\nOData-Version: 4.0\r\n\r\n{\"error\":{\"code\":\"0x80040216\",\"message\":\"An unexpected error occurred.\",\"innererror\":{\"message\":\"An unexpected error occurred.\",\"type\":\"System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]\",\"stacktrace\":\" at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.Execute(OrganizationRequest request, InvocationContext invocationContext, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode, ExecutionContext executionContext, Dictionary`2 optionalParameters)\\r\\n at Microsoft.Crm.Extensibility.OData.CrmODataExecutionContext.Upsert(Entity entity)\\r\\n at Microsoft.Crm.Extensibility.OData.CrmODataExecutionContext.Update(Entity entity, UpdateOption updateOption)\\r\\n at Microsoft.Crm.Extensibility.OData.CrmODataServiceDataProvider.UpdateEdmEntity(CrmODataExecutionContext context, String edmEntityName, String entityKeyValue, EdmEntityObject entityObject)\\r\\n at Microsoft.Crm.Extensibility.OData.EntityController.PatchEntityImplementation(String& entityName, String key, EdmEntityObject entityDelta)\\r\\n at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute[TResult](ILogger logger, EventId eventId, ActivityType activityType, Func`1 func, IEnumerable`1 additionalCustomProperties)\\r\\n at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute[TResult](ILogger logger, XrmTelemetryActivityType activityType, Func`1 func)\\r\\n at lambda_method(Closure , Object , Object[] )\\r\\n at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters)\\r\\n at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken)\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\\r\\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext()\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\\r\\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\\r\\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext()\"}}}\r\n--batchresponse_dce3e803-f50b-48eb-931a-1fe0cee85858--",
    "source": "felleskjopettest.crm4.dynamics.com",
    "errors": [],
    "debugInfo": "clientRequestId: 3b7277d4-ed2e-4121-8b70-038b273ec715"
    }
     
     
    Have anyone seen this before or have any solution to this issue?  🙂
  • Verified answer
    Tarjani Profile Picture
    243 on at

    Hi there,

    I'm not sure if anyone is still having an issue with doing a Closed Won on the Opportunity, but we have managed to action it successfully.  The trick that we had was that instead of updating the Opportunity we had to create an Opportunity Close Activity and set the Status Reason/Status as Won.  This was the last step in our workflow and we now have it updating successfully.

    Create Opportunity Close Activity.jpg

  • Community Power Platform Member Profile Picture
    on at

    I am encountering this same problem but have not been able to resolve it. 

    I get the following error. I cannot tell which field is missing or has bad data: 

    "An error occurred while validating input parameters: Microsoft.OData.ODataException: Does not support untyped value in non-open type."

     

     

    Here is the flow: 

     

    any suggestion on how to resolve this?

  • Community Power Platform Member Profile Picture
    on at

    The image was left off of the previous postThe image was left off of the previous post

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 525 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 324 Moderator

#3
abm abm Profile Picture

abm abm 232 Most Valuable Professional

Last 30 days Overall leaderboard