cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
AhmadAnwar
Level: Powered On

Close Opportunity record in Dynamics 365

I built a canvas app that should close an Opportunity record in Dynamics 365 when a button is clicked.

The button executes the Patch function as below.

Patch
    (
        Cases,
        LookUp
        (
            Cases, 
            Opportunity=GUID("55B78509-1AF1-E811-A973-000D3AE0BC37")
        ) 
        , {statecode: 1}
        , {statuscode: 3}
    )

This returns an error with Status Code 502 and the body:

{
  "error": {
    "code": 502,
    "source": "australia-001.azure-apim.net",
    "clientRequestId": "43d4a0ac-6749-4c6e-81cd-e1ec546f7de7",
    "message": "BadGateway",
    "innerError": {
      "status": 502,
      "message": "--batchresponse_67cae861-e762-4114-83db-948b60543257\r\nContent-Type: application/http\r\nContent-Transfer-Encoding: binary\r\n\r\nHTTP/1.1 500 Internal Server Error\r\nREQ_ID: 46dfd3b4-5392-423c-9dd3-d996de9a5c80\r\nContent-Type: application/json; odata.metadata=minimal\r\nOData-Version: 4.0\r\n\r\n{\"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.\",\"innererror\":{\"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\",\"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_67cae861-e762-4114-83db-948b60543257--",
      "source": "hfnz.crm6.dynamics.com",
      "errors": [],
      "debugInfo": "clientRequestId: 43d4a0ac-6749-4c6e-81cd-e1ec546f7de7"
    }
  }
}

I tried populating State Code and Status Reason in MS Flow and I get the same error.

 

It seems that it is not possible to change record status by design?

Are there other solutions?

5 REPLIES 5
Community Support Team
Community Support Team

Re: Close Opportunity record in Dynamics 365

Hi @AhmadAnwar ,

Do you want to change the State Code and Status Code of a Case record using Patch function?

 

Based on the formula that you mentioned, I think there is something wrong with it. Actually, the Status column (statecode) and Status Reason column (statuscode) are both Option Set type column. We should provide a Option Set value for the two columns rather than Number value (you typed in your formula).

 

I have made a test on my side, please take a try with the following workaround:7.JPG

Set the OnSelect property of the "Patch" button to following:

Patch(
Cases,
BrowseGallery1.Selected,
{
Status: 'Status (Cases)'.Resolved,
'Status Reason': 'Status Reason (Cases)'.'In Progress'
}
)

On your side, you should type:

Patch(
      Cases, 
      LookUp(Cases, Opportunity = GUID("55B78509-1AF1-E811-A973-000D3AE0BC37")), 
      {
        Status: 'Status (Cases)'.Cancelled, 
        'Status Reason': 'Status Reason (Cases)'.Cancelled
      }
)

Note: Please make sure you have enabled the "Relation data, option sets and other new features for CDS" option within Advanced settings of App settings of your app.

 

More details about providing a value for a Option Set type column in CDS Entity, please check the following blog:

https://powerapps.microsoft.com/cs-cz/blog/option-sets-and-many-to-many-relationships-for-canvas-app...

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
AhmadAnwar
Level: Powered On

Re: Close Opportunity record in Dynamics 365

Thanks for your reply.

 

I tried this following formula:

Patch(
      Cases, 
      LookUp(Cases, Opportunity = GUID("55B78509-1AF1-E811-A973-000D3AE0BC37")), 
      {
        Status: 'Status (Cases)'.Exit, 
        'Status Reason': 'Status Reason (Cases)'.Closed
      }
)

And I get this error:

The type of this argument 'statecode' does not match the expected type 'Number'. Found type 'Error'.

I double checked that the Relation data, option sets and other new features for CDS is checked.

 

A side note:

  • Both fields don't exist on the Form, meaning that the user won't interact or set the fields. The app will automatically close the current record upon clicking a submit button.
  • The labels for both Status and Status Reason fields are renamed.
  • (Status) Canceled -> Exit
  • (Status Reason) Canceled -> Closed
  • And the name of Opportunity entity is renamed to Case.

 

 

Community Support Team
Community Support Team

Re: Close Opportunity record in Dynamics 365

Hi @AhmadAnwar ,

Do you mean that the Cases Entity that you added in your app is actually the Opportunity?

Do you mean the Status field and Status Reason field could not be enabled within the Edit form?

 

I have made a test on my side, and don't have the issue that you mentioned, I could enable the Status field and Status Reason field in my Edit form. The screenshot as below:2.JPG

Please check the following GIF screenshot for more details:Test.gif

Please consider click the "Edit fields" property for Edit form in right panel, then click "Add fields", find the Status field and Status Reason field, check them. then click "Add" button, then they would be displayed within the Edit form.

 

If you could not find the Status field and Status Reason field within the fields list as above screenshot mentioned, it means that the Status field and Status Reason field are not supported within your current Entity (the two fields are read-only or generated by System in your current Entity). So there is no way to set values for the two fields in PowerApps currently.

 

Also please consider re-generate a new app based on your CDS Entity, then try the app again, check if the issue is solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Administrator
Administrator

Re: Close Opportunity record in Dynamics 365

Hi @AhmadAnwar how are you progressing with this? Was the above reply from our Community Support Team helpful? 

 

Thank you,

 

@TopShelf-MSFT 

AhmadAnwar
Level: Powered On

Re: Close Opportunity record in Dynamics 365

Not really.

 

Still getting the same error.

 

Here are the steps I followed:

1- Create a new Dynamics 365 Powerapp template.

dynamics365 app.PNG

 

2- Selected the Data Source connection to my production instance.

3- Deleted all screens and kept the Edit Screen

screens.PNG

 

4- Added a new button to the form and called CLOSE

5- In the button's onSelect, I added this formula

Patch
    (
        Cases,
        LookUp
        (
            Cases, 
            Opportunity=GUID("55B78509-1AF1-E811-A973-000D3AE0BC37")
        ) 
        , {
            Status: 'Status (Cases)'.Exit, 
            'Status Reason': 'Status Reason (Cases)'.Closed
        }
    )

error.PNG

 

The CLOSE button should do only one thing, closing the current record.

 

Note: I made sure that the Relational data, option sets, and other new features for CDS is enabled

Helpful resources

Announcements
firstImage

Microsoft Business Applications Virtual Launch Event

Join us for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.

firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

FirstImage

Power Platform World Tour

Coming to a city near you

thirdimage

PowerApps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

FourthImage

Join PowerApps User Group!!

Connect, share, and learn with your peers year-round

Top Kudoed Authors
Users Online
Currently online: 340 members 1,820 guests
Please welcome our newest community members: