Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
1000 accounts need re-assigning from one user to another. 999 have re-assigned fine but one key account which obviously has a substantial amount of information against it will not budge. It does not just time out, it actually causes the web page to just freeze and you don't see the little Green bar load. I was considering going into SQL and doing this via an update statement but I believe it would be unsupported and could cause a problem due to the cascading. Now I could go and turn off cascading but then a lot of the information against this account would not be carried across. Does anybody have any other ideas?
Select that single Account and try to assign it to the other user.
If it fails CRM will pop an error message.
Copy that message and post here.
This error message doesn't give much info about the issue.
Try assigning the account record to Admin user and then reassign it to the user that you wanted.
Do this assigning task as a CRM Admin user.
Try this workaround it may fix your issue.
I would enable tracing in the server while assigning this record may that will throw more information about the issue
I agree with Chitra here, collecting the CRM serer traces should give us more information about the error.
Could you also please collect a SQL profiler along with the CRM traces? I think the exception here is occurring at the SQL end.
I found that there were thousands of orders and invoices attached to this account which did not need to be moved across. I turned off the "assign cascading" on orders and invoices to get around this.
Thanks for the input.
Business Applications communities