Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
Yesterday while editing a business rule I accidentally hit save as a few times and ended up with 4 copies of the same business rules.
I went to clean it up and was able to purge 1 copy, and the original.
But when i went to deactivate the 3rd one, it says there is a 'duplicate' record. Log says 'Cannot insert duplicate key' and nothing more. Not helpful.
When i went to deactivate the 4th one, it DID deactivate, but when i try to delete it, it says 'record could not be deleted because of an association'. Opening the log is useless - just the same error - 'The object you tried to delete is associated with another object and cannot be deleted'.
I've published all in between just for good measure.
I've looked all over for a process/workflow that I can kill to stop this to no avail so this is NOT good since it's allowing a flawed business rule to run wild with no way to stop it.
Has anyone else seen this and has anyone found a solution yet or is this a MS bug?
I'm running on-prem.
Change the names of each of them, save it and then delete it if not required
tried that too - could only change the names of the ones i could deactivate but still, cannot delete them
i'm thinking maybe there is some runaway WF process and if i can isolate it and kill it, that might release to lock that's causing this problem haven't found a way to find it though
Can you try removing all the conditions from your rule and then try it. Just do it for the one's which you dont want to use
if it did not work even after removing conditions; here:
Seems to be a bug :(
Raise a ticket to Microsoft
tried that as well - you have to be able to deactivate to do that and you have to have at least one condition to save the changes
Try deactivating it from Advanced Find like the screenshot below and then delete it.
Thanks Natraj but same result. Nothing useful in the logs either. Unless anyone has ideas, looks like I get to burn a M$ support case on this.
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: System.Web.HttpUnhandledException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #7391BCAC
Detail: <OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts"> <ErrorCode>-2147220970</ErrorCode> <ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic" /> <Message>System.Web.HttpUnhandledException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #7391BCAC</Message> <Timestamp>2016-12-13T16:15:23.6927505Z</Timestamp> <InnerFault> <ErrorCode>-2147220953</ErrorCode> <ErrorDetails xmlns:d3p1="schemas.datacontract.org/.../System.Collections.Generic" /> <Message>The object you tried to delete is associated with another object and cannot be deleted.</Message> <Timestamp>2016-12-13T16:15:23.6927505Z</Timestamp> <InnerFault i:nil="true" /> <TraceText i:nil="true" /> </InnerFault> <TraceText i:nil="true" /></OrganizationServiceFault>
Go the default solution and location the business rule. Then click on "Show Dependencies" and see what the dependencies are.
They were the same as the other duplicate business rule. However, i was able to finally delete this (without burning a support ticket with M$) after the application of 8.2 update. We'll never know if that fixed it or the subsequent reboots fixed it but I just noticed that I am able to now delete this rogue B/R so if anyone else encounters this problem, if you've updated to 8.2, try a reboot. Maybe some process got hung up that prevented deletion or maybe it was something in the 8.2 update.
Similar problem I had faced which was from business rules.
Here is a blog post -
Business Applications communities