Custom Action import failed in CRM 2013

All replies

• 

  

  0

  Sign in to vote

  What error message do you get when importing ?

  What components are in the solution that you're trying to import, and which of these already exist in the destination organisation ?

  ---

  Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

  Tuesday, May 6, 2014 9:56 AM

  Moderator
• 

  

  0

  Sign in to vote

  Hi,

  I have created solution which has Custom Actions and that custom actions included workflow activity as step.

  When I am trying to import in another online CRM 2013 then It gives me an error message.

  "The Requested Record was not found or you dont have sufficient ... the import fails with message "Workflow With Id = {GUID} Does Not Exist"."

  Thanks

  Tuesday, May 6, 2014 10:03 AM
• 

  

  0

  Sign in to vote

  Hi, it happened before to me.

  I realize that it is because of the Arguments and Steps that related to the workflow as parent.

  In the destined organization (your another online CRM 2013), it has no that custom action (CRM makes it as workflow) as parent, so when they import the Arguments and Steps, it will fails with message "Workflow with Id = {Guid} does not exist"

  So, what I did is : 

  1. I remove all of of my arguments and steps (or you can create another blank custom action first)

  2. Then export a solution with your blank custom action (please remember import first your custom action without any arguments or steps)

  3. Import your solution from number 2.

  4. Then you make sure you can have your blank custom action imported successfully in your destination CRM Online organization, then your workflow with ID ={Guid} already there

  5. Next, you can update your custom action by adding some arguments and steps, then you can export and import to your destination since your workflow ID has been there (in your destination organization)

  You can refer to this link : http://missdynamicscrm.blogspot.com/2014/05/crm-2013-custom-action-import-solution.html

  In conclusion, you should make sure that your destination org has your blank custom action before you adding custom action arguments and steps, or if you are still not sure which organization you wanna to import, you can create a solution containing a blank custom action, save it to your local, then you can continue to develop your custom action by adding arguments and steps as well. Then, later you have another organization, first, import your solution created before with blank custom action as one of the component first. Then, you can continue import your current solution (with added arguments and steps).

  Thanks. 

  Hope it helps and please help to mark as answer if you managed to do it!

  Thanks.

  Friday, May 9, 2014 6:15 PM
• 

  

  0

  Sign in to vote

  Hi,

  This is a known issue that is fixed in SP1 (Leo). The problem is that the SDK Processing Message Step is not correctly linked up to the Message ID that is created for the custom action that is created. I find the easiest way to deploy these solutions is to exclude the SDK Message Processing Step from your solution and then use the Plugin Registration Tool to add it back in once deployed to the target solution.

  There is a connect issue that provides more information - https://connect.microsoft.com/dynamicssuggestions/feedback/details/810477/crm-2013-solution-import-fails-when-plugins-attached-to-custom-action-processes-sdkmessage-are-included-in-solution

  Andrii describes the work around here - http://a33ik.blogspot.com/2014/01/how-to-fix-sdkmessage-with-id-does-not.html

  Hope this helps,

  Scott

  ---

  Scott Durow
  Blog www.develop1.net    Follow Me
  Rockstar365
  If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

  • Proposed as answer by Scott Durow (MVP)MVP, Editor Sunday, May 11, 2014 9:52 AM

  Sunday, May 11, 2014 9:51 AM

  Answerer