Skip to main content

We have a package installed https://github.com/SalesforceLabs/ActionPlansV4/blob/main/README.md

 

After creating ActionPlans (which are linked with internally with our custom objects ), when independently trying to delete the action plans, we are getting error:  

 

"There's a problem saving this record. You might not have permission to edit it, or it might have been deleted or archived. Contact your administrator for help." 

 

I am sys admin and I have provided myself with FULL access to the LabActionPlan object, also associated objects, but still cannot delete the action plan. 

 

While checking on the "Developer Console" log, there is no sign of error seen, but the action plan doesn't get delete with the error message as shown above. 

 

While discussing this with the Salesforce support team, they suggested, they don't have access to third party code/log, so I landed here for the help.  

 

Can anyone help here or suggest ? 

 

Thanks, 

AnkitS.

1 respuesta
  1. 10 oct, 11:56

    @Ankit Shrestha full access on LabsActionPlans__ActionPlan__c is not the check that failed. That message is Lightning hiding an access or deleted-record error inside the delete.

    Action Plans V4 does not only delete its own row. The delete trigger also removes the Tasks the plan created. If one of those tasks, or the record the task hangs off, blocks the delete, the whole save fails and you get this generic line. A validation rule or a trigger on Task is enough. Sys admin on the plan object does not bypass that.

    No line in the log usually means the trace flag was not on for your user when you clicked delete. Set a flag for yourself, Apex at finer, delete one plan, and read the DmlException. The real object is in there.

    A lookup set to restrict deletion throws a different message, the one that names the related record. If you only see the permission text, start with the tasks, not with another perm set on the plan.

    Support is right that they do not own this package. The delete path is in the public Salesforce Labs repo you already linked. Once the log names the task or the parent record, that is the fix, not more access on Action Plan.

0/9000