Timesheet Approval Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hello All
Our resource managers are experiencing the following error when approving a timesheet with an associated project - Either a resource or attribute is mandatory / You do not have permission to perform action (also see attached screen shot). As you can see, the Timesheet was approved.
I verified an existing Resource Assignment exists at the Project Level, the resource is legitimate. What is causing these errors/warnings? TIA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi @PennyDMc,
You're actually looking at two separate messages stacked on one click, not a single bug, and the screenshot backs that up: the time cards themselves all show green checkmarks and the banner says 5 approved, so the approval on the time_card record did go through. The warnings are coming from downstream validation.
- Permission warning: out of the box, project task time cards are approved by the Project Manager field on the task, not by a resource manager role. If Gregory isn't listed as PM on that specific project task (or the approving user lacks the timecard_approver role), you'll get the permission message even though someone with rights already pushed the approval through.
- "Resource or attribute is mandatory": this one traces back to Resource Assignment/Resource Plan validation, specifically the "Validate Resource availability" business rule that calls into RMUsersCapacityAPISNC to pull capacity data from the Employee Profile (sn_employee_profile) table. If the resource on that assignment doesn't have an Employee Profile record, this check fails even though the Resource Assignment itself looks fine at the project level.
- Check whether the resource in question actually has an sn_employee_profile record, separate from the Resource Assignment you already confirmed.
Worth pulling the system log for the exact business rule name on your instance since attribute-based resource plans can throw a similar message for a different reason.
Thank you,
Vikram Karety
Octigo Solutions INC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi @PennyDMc
- Ensure the Resource Assignment and Resource Plan fields are properly populated on the time card . Refer: https://www.servicenow.com/community/developer-forum/resource-assignments-and-the-time-sheet-portal/...
- Ensure Approver is having any of timecard_approver or timecard_admin role.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti