Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I am receiving an error when trying to assign or change ownership on a single account record. I have set the current assignee and any prospect owner to System Admin to ensure it isn't permission based. The entity is pretty default I believe.
I have searched for duplicate accounts and can find none. I have checked against this previous and simllar support questionhttps://community.dynamics.com/365/sales/f/dynamics-365-for-sales-forum/311942/cannot-insert-duplicate-key-when-i-try-to-reassign-accounts/905102
Any help appreciated.
Can you check if there is any alternate keys on the account entity? The error message is about duplicate keys and the Account GUID is not within our control, either there is some other alternate key causing this problem ( I don't see how though).
As an alternative solution to make sure the account itself is not the reason, install the chrome extension Level Up and clone the account record. Try to assign the owner on the clone and see what happens.
Thank you for the prompt reply. There are no keys associated to the account entity.
I cloned the record using Level Up and whilst the record cloned I was unable to save with this as the error message
at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.CreateInternal(Entity entity, InvocationContext invocationContext, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode, Dictionary`2 optionalParameters)
at Microsoft.Crm.Extensibility.OData.CrmODataExecutionContext.CreateOrganizationResponse(Entity entity)
at Microsoft.Crm.Extensibility.OData.CrmODataServiceDataProvider.CreateEdmEntity(CrmODataExecutionContext context, String edmEntityName, EdmEntityObject entityObject, Boolean isUpsert)
at Microsoft.Crm.Extensibility.OData.EntityController.PostEntitySetImplementation(String& entitySetName, EdmEntityObject entityObject)
at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute[TResult](ILogger logger, EventId eventId, ActivityType activityType, Func`1 func, IEnumerable`1 additionalCustomProperties)
at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute[TResult](ILogger logger, XrmTelemetryActivityType activityType, Func`1 func)
at lambda_method(Closure , Object , Object )
at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object methodParameters)
at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
Activity Id: 13dd0c96-90b9-4d19-9f81-964aa508a3f8
OK, what we are mostly sure of is that this is a bad data problem and we both agree that this is a bad error to show with no or little information. There is a piece of information in that specific account that is causing this. Before we go into trying to find out which piece of data is that, can you confirm that no plugins are running? May be this account is triggering some edge case in some custom code?
If there are no plugins or any kind of code running and if you are really willing to know the piece of bad data then you need to spend some time, try to clone the record with Level up, start by your custom fields then OOB fields, one by one, clear them out and try to save, once you are able to save the record then that's the piece of info that is causing this. Please keep me updated on this :)
Is the User you're trying to assign the record to in a different Business Unit? Also that error is related to the Cobalt Snapshot Plugin that I'm guessing you have installed to clone records so that's where I'd start looking for the peoblem.
Many thanks for everyone's help. Yes we installed Colbalt to clone contacts that moved organisations.
So I looked closely at the contacts associated to the account. I set all those contacts' ownership to the user I wanted to assign the account to. I was then able to reassign the account as needed. Not sure why this would make a difference but it did.
Business Applications communities