cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
AhmadAnwar
Frequent Visitor

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?

7 REPLIES 7
v-xida-msft
Community Support
Community Support

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.

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.

 

 

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.
Anonymous
Not applicable

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

 

Thank you,

 

@Anonymous 

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

Was this ever resolved? I'm running into a similar issue with patch trying to conditionally update the status code:

image.png

 

When the user selects a Status Reason of Completed or Cancelled, I'm trying to get the Activity Status to match, but it doesn't work for either scenario (default is fine). 

I just gave up and didn't bother. This issue had taken me a lot of time and I had to figure out a workaround.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (707)