Answered by:
Error deactivating workflow

Question
-
I have been trying to alter an custom entity which is linked to the accounts entity. My predessor on this project had deleted a few custom fields from the accounts entity. I have been trying to clear up the system, but am stuck trying to deactivate and remove a business rule. The field ( lookup to cbfmprofiles no longer exists in the accounts entity
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: System.Web.HttpUnhandledException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #6DF0139DDetail:
<OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">
<ErrorCode>-2147220970</ErrorCode>
<ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic" />
<Message>System.Web.HttpUnhandledException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #6DF0139D</Message>
<Timestamp>2014-10-30T14:40:04.8432106Z</Timestamp>
<InnerFault>
<ErrorCode>-2147160010</ErrorCode>
<ErrorDetails xmlns:d3p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic" />
<Message>The dependent component Attribute (Id=new_cbfmprofile) does not exist. Failure trying to associate it with Workflow (Id=56863d0f-90d0-e311-80ba-00155d01d308) as a dependency. Missing dependency lookup type = AttributeNameLookup.</Message>
<Timestamp>2014-10-30T14:40:04.8432106Z</Timestamp>
<InnerFault i:nil="true" />
<TraceText i:nil="true" />
</InnerFault>
<TraceText i:nil="true" />
</OrganizationServiceFault>
Dont ask me .. i dont know
Thursday, October 30, 2014 2:49 PM
Answers
-
Hi Pete,
First off, try re-adding the missing field then try to de-activate. If that doesn't work (chances are it won't), you may need to create a solution containing the account entity (and so your business rule too), export it, then manually edit the customization.xml file to remove the problem dependency before re-importing. Once done, try de-activating your business rule.
Failing that, log a support ticket with Microsoft.
Good luck!
Rob
MCTS. GAP Consulting Ltd. Microsoft Community Contributor Award 2011 & 2013
- Marked as answer by Pete Newman Friday, October 31, 2014 10:38 AM
Thursday, October 30, 2014 10:44 PMAnswerer
All replies
-
Hi Pete,
First off, try re-adding the missing field then try to de-activate. If that doesn't work (chances are it won't), you may need to create a solution containing the account entity (and so your business rule too), export it, then manually edit the customization.xml file to remove the problem dependency before re-importing. Once done, try de-activating your business rule.
Failing that, log a support ticket with Microsoft.
Good luck!
Rob
MCTS. GAP Consulting Ltd. Microsoft Community Contributor Award 2011 & 2013
- Marked as answer by Pete Newman Friday, October 31, 2014 10:38 AM
Thursday, October 30, 2014 10:44 PMAnswerer -
Hi Rob
Thank you for that, the re-adding of the field worked a treat. Job done
Dont ask me .. i dont know
Friday, October 31, 2014 10:38 AM