Skip to main content
Solved

Delete Task added to Project X (Non-Project Code)???

  • April 20, 2026
  • 3 replies
  • 66 views

nickcerri32
Captain II
Forum|alt.badge.img+7

Team - one of our customers wants to limit the characters used for Project Tasks.  This is simple enough.  However, it turns out that the consultant who originally configured this customer somehow (???) added a Task to Project X.  To make matters more unnecessarily inconvenient, they used the maximum characters allowed by the segmented key.  I can neither open this task (on Project Tasks), delete the tasks using a Mass Update, or Update the Task ID (also using a Mass Update).  I’ve also tried renaming the Non-Project Code, but this isn’t helpful either.

 

  1. Is there a way, short of using a customization, that I can access this task to delete it?
  2. How in the world was this able to be done in the first place?

 

Thanks in advance!

Best answer by nickcerri32

Thanks for the reminder, ​@Chris Hackett . As it turns out, the task in question was added as a common task.  I don’t typically use these, so I overlooked them, but it was just a matter of deleting out the associated common task, which solved the problem.

3 replies

darylbowman
Captain II
Forum|alt.badge.img+17

I think the incredulity of your question indicate the likeliest answer:

How in the world was this able to be done in the first place?

I don’t think it should have been possible. It could have been done with a SQL script, although the motivation eludes me.

 

Is there a way, short of using a customization, that I can access this task to delete it?

Extremely unlikely


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • August 5, 2026

Hi ​@nickcerri32 were you able to find a solution? Thank you!


nickcerri32
Captain II
Forum|alt.badge.img+7
  • Author
  • Captain II
  • Answer
  • August 6, 2026

Thanks for the reminder, ​@Chris Hackett . As it turns out, the task in question was added as a common task.  I don’t typically use these, so I overlooked them, but it was just a matter of deleting out the associated common task, which solved the problem.