265
We recently upgraded to Hosted CRM2013, a user is attempting to close an opportunity and gets the error code "state code or status code invalid" It wont let me download the log file to see where the error is occuring.
*This post is locked for comments
Hi Chasab
Microsoft Dynamics CRM 2013 Update Rollup 1 (UR1) is available now.
This rollup contains stability and memory-consumption improvements, as well as fixes for 32 issues. Many of the resolutions like Opportunity closed as won does not take custom status reason while closing.
We have this same issue. please fix this ASAP! we can't use CRM 2013 without fixing this issue
Hello,
we need to export the Opportunity entity without dependent components and modify the xml file. As suggested by CHASAB I would recommend you to create a service request for CRM Online support from the below contact information as they would help and walk you through the entire process in modifying the xml in the recommended way. Also you can check with the CRM Online support about the fix for this issue in detail.
Microsoft Customer central number : Phone: 1-800-936-4900 in the United States or Canada
Link to create CRM Online support ticket : rc.crm.dynamics.com/.../support.aspx
Thanks
GSLESZ My advice would be to put in a ticket, I had a call with a microsoft tech today and he walked me through the process of exporting the opportunity xml files, gave me the correct code to edit it, and walked me through the re-upload process.
CHURCHILL - Do you know when this issue might be resolved? My users are very frustrated. Also, where is the customization.xml file located so I can try and edit it? I'm assuming this is possible even for CRM Online users. Any help would be appreciated.
Thanks
Hello,
This is a recently discovered issue with CRM 2013 in which custom status codes cannot be used for closing opportunities as 'Won' because the default value for Status reason field (Statecode ) "Won" is missing. Custom values are ignored and the system instead tries to save it with the system default status reason value of 'Won' and currently investigation is in progress.
We may need to add the default value "Won" in the Customization.xml of opportunity entity as a workaround which should also take care of your issue and also now you do have another workaround which Marco suggested is also the better one temporarily i.e. closing the opportunity as won via workflow.
Thank You.
Ok, thanks... and if try to close as won from the list of record (selecting the opportunity) and not inside the single form... what happen?
As a test you could try to close the opportunity state with a WF...
#1
André Arnaud de Cal...
291,735
Super User 2024 Season 2
#2
Martin Dráb
230,466
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
