{"id":11275,"date":"2018-02-28T18:05:23","date_gmt":"2018-02-28T12:35:23","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=11275"},"modified":"2021-05-14T09:02:44","modified_gmt":"2021-05-14T09:02:44","slug":"fixed-unable-to-create-or-update-record-after-upgrading-dynamics-365-crm","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2018\/02\/fixed-unable-to-create-or-update-record-after-upgrading-dynamics-365-crm\/","title":{"rendered":"Fixed – Unable to Create or Update record after Upgrading Dynamics 365 CRM"},"content":{"rendered":"

Introduction:<\/strong><\/h2>\n

Whenever we upgrade Dynamics CRM we learn many things along with it. Recently we had a business requirement where we recently upgraded Dynamics CRM from CRM 2011 to CRM 2016. We completed upgrade smoothly but after upgrading to CRM 2016 we were not able to Create\/Update the Service Activity record. While saving the record we were facing the error message.<\/p>\n

After downloading Error Log File, we found below error message.<\/p>\n

<Message> Both statecode and statuscode must be set or both of them must be null. <\/Message><\/p>\n

The error messages show that Statecode and StatusCode fields must be filled or set NULL. But more often, we are not setting any values and as we know, CRM internal program sets the default value for these fields.<\/p>\n

So, we plotted this issue and found the root cause, .i.e. the \u201cstatecode\u201d field was entered in the form that was in the editable mode. And while saving the record this \u201cstatecode\u201d field was filling with a default value and converting its mode to \u201cdirty\u201d. Later on, it was passing in the save record context but on the other side \u201cstatuscode\u201d field was not getting passed. Hence, the above error message was getting displayed while saving the record.<\/p>\n

The absurd thing occurred is that after upgrading, the field was in editable mode but CRM generally doesn\u2019t allow to edit the \u201cstatecode\u201d field while saving the record.<\/p>\n

\u00a0You can see below screen that field was in editable mode:<\/p>\n

\"Unable<\/a><\/p>\n

But when we saw the properties of the field, it is still showing in the lock mode.<\/p>\n

\"Unable<\/a><\/p>\n

Then to fix the issue, we set the \u201cField\u201d to read-only mode using field properties from \u201cForm Editor\u201d.<\/p>\n

\"Unable<\/a><\/p>\n

So, while saving the record, this field won\u2019t be dirty. And CRM Internal programs handles to update this field.<\/p>\n

Conclusion:<\/strong><\/h2>\n

Using the steps above user will be able to create or update records in Dynamics CRM after upgrading to newer version.<\/p>\n

\"Microsoft<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction: Whenever we upgrade Dynamics CRM we learn many things along with it. Recently we had a business requirement where we recently upgraded Dynamics CRM from CRM 2011 to CRM 2016. We completed upgrade smoothly but after upgrading to CRM 2016 we were not able to Create\/Update the Service Activity record. While saving the record\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":11276,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[16,18,19],"tags":[1747,1763],"class_list":["post-11275","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dynamics-365","category-dynamics-365-v9-2","category-dynamics-crm","tag-unable-to-create-or-update-record","tag-upgrading-dynamics-365-crm"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/11275","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=11275"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/11275\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/11276"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=11275"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=11275"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=11275"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}