Resource Assignments (Group): Deleting individual assignment within a Group assignment
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
We are moving to Resource Assignments in May. We are currently testing in classic UI (demands/projects) as well as Project Workspace (PW). We create assignments at the demand and project levels, not tasks. When creating Group assignments, we need to have ability to delete underlying individual assignments for those Users that end up not working on the project.
Can someone tell me how to delete underlying individual assignments within the classic UI and Project Workspace (not using the "Planning" tab in PW)?
Thanks,
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Navigate to the Resource Plan related list on your Demand or Project record. Expand the Group assignment to see the underlying individual (member) assignments. You can delete individual assignments directly from the related list by selecting the record and using the Delete action, or open the individual assignment record and delete it from there. Make sure the assignment state allows deletion (e.g., it's not in an Approved/Committed state that locks edits — you may need to move it back to Requested/Planned first).
Project Workspace (without the Planning tab):
From the Project Workspace, go to the Resource Plan section/tab (not Planning). The group assignment should list its member assignments underneath. Right-click or use the context menu on the individual assignment row to delete it. Alternatively, you can open the individual assignment record directly and delete from the form.
If delete isn't available in either UI, check these common blockers:
- The assignment is in a state that restricts deletion (Approved, Committed, etc.) — change state back to Requested/Draft first.
- Your role may lack the
resource_management_adminor equivalent ACL. Theresource_managerrole can typically manage assignments, but deletion ACLs can be more restrictive. - There may be a business rule preventing deletion of child assignments when the parent group assignment is in certain states. Check for BR/ACLs on
resource_planorresource_assignmenttables.
If the UI doesn't expose delete natively, you can always navigate directly to the individual assignment record via the URL (resource_plan.do?sys_id=<xyz>) and delete from the form, assuming your ACLs permit it.
Hope that helps — happy testing!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Appreciate the response Naveen20, however, you reference resource plans. We need to be able to delete individual resource assignments after a Group assignment is created, at the project/demand level, not the task level. Any thoughts on that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Try the soft delete
- Set the individual assignment hours to zero — rather than deleting, zero out the planned hours for users who won't be working on it. This effectively neutralizes the assignment without fighting the group sync logic.
- Use a targeted group — if only a subset of members will work on the project, consider creating individual assignments instead of a group assignment, or create a narrower group.
- Soft-delete via state — move unwanted individual assignments to a Cancelled or Rejected state (if your state model supports it) so they're excluded from capacity/demand views.
