"The Status or Status Reason of the Microsoft Dynamics CRM Record Could Not Be Set"

(0) Share

Report

Posted on by JDMCRM

1,799

Hi,

I'm importing roughly 3,500 cases into a new system from 2011. Nearly all of these are now resolved or canceled, with around 34 still active. A lot of the resolved cases have odd values for 'Status Reason'. What I think must of happened is that someone added a load of Case Status Reason values a long time ago and subsequently they were deleted over time. However, the cases that were resolved when the Status Reason values were active in the system have the value locked into their Status Reason field.

Now as I'm using the import wizard I have catered for this by adding all of the possible Status Reason values into the target system, I map them all within the import process, but I still get the error "The Status or Status Reason of the Microsoft Dynamics CRM Record Could Not Be Set". I can't seem to find a way around this error. I don't even need the status reason to be set on the resolved cases. I just need to get them in to the new system.

The 'Status' field appears to map fine, with just the three, Active, Resolved, Canceled. So I think it's more likely an issue with Status Reason.

Any ideas? Or even a workaround solution so I can get them in.

Thanks

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

JDMCRM 1,799 on at

Like (0)

Report

After doing a little more digging, this error seems to be associated with Resolved cases only. In Progress and Canceled appear to be fine. The error description actually says, "the record was created but the state could not changed to the target value".

I wonder if it's the the State causing the error and not the Status Reason. Some of the resolved cases are importing as partial failures and are switched from there import status of Resolved to Active.

Was this reply helpful? Yes No
Verified answer

ScottDurow 21 on at

Like (1)

Report

The issue is that you cannot create a record in any other state other than active - you will need to import another custom flag field and make a workflow that closes the case if the flag is set.

Was this reply helpful? Yes No
JDMCRM 1,799 on at

Like (0)

Report

Thanks Scott appreciate the response. Will give this a go.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Awesome, thanks Scott, I was also having the same issue.

Was this reply helpful? Yes No
Eric Hula 25 on at

Like (0)

Report

I'm having the same exact problem. However, we've already successfully imported thousands of Account, Contact, Lead, and Opportunity records in CRM Online that are in the Inactive state. So you absolutely can import a deactivated record into the CRM database. I don't understand why Cases specifically are complaining about ErrorInSetState and why partially imported records are now in an active state. I may have to open a ticket for this.

For reference, I'm migrating from CRM 2013 On Prem to CRM Online.

Was this reply helpful? Yes No