Having configured a worker as a project resource and associated them with a user, the Employee self-service > Timesheets > New timesheet shows the worker resource as default, but doesn't list them in the lookup control:
This isn't a problem as long as the user only has to record their own timesheets, but should they ever be nominated as a delegate, it's possible to get to the point that they can't then complete their own timesheet:
| Before selecting delegate, only the delegate is shown in lookup |
Having selected delegate, user's own resource isn't available |
 |
 |
The behaviour isn't consistent across all environments, so it feels like it's more likely to be a matter of configuration, but I can't work out what. I've tried debugging in an attempt to identify what might be at play, going through
- Form/TSTimesheetCreate::lookupReference
- Class/TSResource::lookupDelegateResources
- Class/SysReferenceTableLookup::performFormLookup
- Class/SysTableLookupBase::formRun
- Class/SysTableLookupBase::buildSelectionList
Running the query at 3 within SSMS shows the current user's resource alongside the delegating resource as I'd expect, but the buildSelectionList method doesn't iterate over multiple records as I thought it might.
Whilst the lookup isn't populated, any user who has completed a timesheet for a delegating resource can get back to their own resource by typing in the name, but that's not the most user-friendly of suggestions, and given this behaviour isn't consistent across all environments, I'm hoping someone can please suggest what might impact the resource lookup
