• Pettycash73
  • NEWBIE
  • 0 Points
  • Member since 2007

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 3
    Questions
  • 2
    Replies

I am recieving the following install error when trying to upgrade from an older version to the V3 posted on the AppExchange.

 

Is there no way to upgrade from the old to new version?

 

Error

Package install error

There are problems that prevent this package from being installed.
<script type="text/javascript">// if (window.sfdcPage) sfdcPage.registerMessage('packageUploadTitle'); // </script>

 

Problems

 
Error: Invalid Data.
Review all error messages below to correct your data.
   
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VccFMAS__r" is already used by custom field APTaskTemplate__c.Action_Plan__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VaVDMA0__r" is already used by custom field APTTaskTemplate__c.APTTaskTemplate__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000Vd65MAC__r" is already used by custom field APTTaskTemplate__c.User__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VcWbMAK__r" is already used by custom field APTaskTemplate__c.APTaskTemplate__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000Vd7NMAS__r" is already used by custom field APTaskTemplate__c.User__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "Action_Plans__r" is already used by custom field ActionPlan__c.Account__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VbUtMAK__r" is already used by custom field ActionPlan__c.Action_Plan_Template__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "Action_Plans__r" is already used by custom field ActionPlan__c.Action_Plan__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VZZ8MAO__r" is already used by custom field ActionPlan__c.Contact__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VZZDMA4__r" is already used by custom field ActionPlan__c.Lead__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VZZIMA4__r" is already used by custom field ActionPlan__c.Opportunity__c. Please rename existing relationship name.

Receiving the following errors when trying to update from v. 1.25 to v. 3. What are the proper steps to upgrading versions?

 

Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VccFMAS__r" is already used by custom field APTaskTemplate__c.Action_Plan__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VaVDMA0__r" is already used by custom field APTTaskTemplate__c.APTTaskTemplate__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000Vd65MAC__r" is already used by custom field APTTaskTemplate__c.User__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VcWbMAK__r" is already used by custom field APTaskTemplate__c.APTaskTemplate__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000Vd7NMAS__r" is already used by custom field APTaskTemplate__c.User__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "Action_Plans__r" is already used by custom field ActionPlan__c.Account__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VbUtMAK__r" is already used by custom field ActionPlan__c.Action_Plan_Template__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "Action_Plans__r" is already used by custom field ActionPlan__c.Action_Plan__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VZZ8MAO__r" is already used by custom field ActionPlan__c.Contact__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VZZDMA4__r" is already used by custom field ActionPlan__c.Lead__c. Please rename existing relationship name.
Duplicate RelationshipNameCustom Field DefinitionsThe relationship name "R00NR0000000VZZIMA4__r" is already used by custom field ActionPlan__c.Opportunity__c. Please rename existing relationship name.

 

We downloaded the Action Plan app for use with our Lead process.  The idea is that there are 4 steps to each action plan as it relates to the selling of our leads. If the Lead is unqualified at any point, the action plan continues to think that the next steps need be taken, which they don't.  

 

We are using dependent tasks, so that when step 1 is completed, the next action is set automatically for 7 days from today.  If the lead is unqualified at step 1, when the task is marked as completed, step 2 is triggered, unnecessarily.

 

Is there any logic that can be built to kill an action plan based when criteria is met? In this case, if the lead status is changed to Unqualified than the action plan should be stopped.

 

Open to any ideas.

I installed Action Plans and got it set up for one of my custom objects. However, when I marked off a task, it was creating two dependant tasks. I looked at the debug log and it turns out that I had a field update on the task object which was causing the task trigger to run again, creating a second dependant task.

 

Luckily, I just had this problem with some other apex code, so here's what I did:

 

In the ActionPlansTaskTriggerUtilities class I added:

 

public static boolean firstTrigger = true;

In the ActionPlanTaskTrigger I wrapped everything inside of an if statement:

 

if(    ActionPlansTaskTriggerUtilities.firstTrigger == true){
        ActionPlansTaskTriggerUtilities.firstTrigger = false;
      // Existing code went here
}

 

This appears to be working correctly. Let me know if this will mess anything else up.