bug/issue with operational resource assignments in resource management workspace

[Adrianadrian]

NB This is updated with detialed description in the comments below with screenshots 🙂
Hi,

We are implementing Resource Management Workspace for a large client and have encountered a peculiar issue when creating operational resource assignments.

When creating an operational resource assignment for a named resource, it works as expected. However, when creating an operational resource assignment for a group, only a few assignments are created. The expected behavior is that all users within the group should have an operational assignment created for them.

For example, creating an operational resource assignment for a group of 10 people should result in 10 records in the resource assignment table. However, in the scenario described, only records for two users are created, and eight are missing. Interestingly, when we create an operational resource plan for a named user, it works for all users.

Has anyone experienced this problem or a similar one?

Thank you!

See example.
 
All users in the group below have same schedules, and capaciity is generated with UI action. All have same attributes, expect that one user, user #4 has employement end date 30.11.2025

Example A) - creating a group assignment with start date after employement start date, and end date after employement end date. This works as expected. See picture 🙂

Example B) Creating a group assignment with start date after employment end date for the user in the group.
This works not as expected/only partly.  Skips creating a record for the user who had an employment end date of 30.11.2025, which is correct.

 
However, it then skips creating records for other users in the group and only creates for user 2.

Our hypothesis is that when the system generates records and it comes to the next person with no capacity, it skips creating records for the next groups. 

[phil_bool_unifi]

I'm wondering if you're entering a value in hours rather than percentage of capacity. If so, it may be that the requested number of hours are fulfilled by the first two group members, so no further resource assignments are getting created. 

I'm also seeing that one particular "OOTB" Yokohama instance is only offering 'hours' value in the choice list today if I use the 'Create Operational Plan' module or the 'New' button on the Resource Mgt Workspace.  That seems to be because the 'plan type' value isn't set at the point the form loads.  If you're seeing the same, this might be worth raising a Hi ticket about.

[Adrianadrian]

Hi @phil_bool_unifi . 
We have not found the issue yet. We can create an operational plan for % capacity and hours in our instance. I will update you if we find out.

Also, just curious: When creating reports where we want to show how much FTE is allocated to Projects, Demands vs. "Operational resource assignment," we see that when creating an operational resource assignment, the effort type is always "hours" or % capacity, which is converted to hours when requesting on capacity. However, on the resource assignments on tasks, you are allowed to request on FTE. The problem is that the effort amount when creating an assignment on a project with effort type FTE is not comparable with the effort on operational plans. See the picture below. Have you circumvented this in any way?

[phil_bool_unifi]

When you come to reporting, if you want to aggregate the amount of effort spent on any project, you'd be better to capture your data from the Resource Allocation records (Resource Allocation Daily, for example).  They will give the totals for the hours assigned from the plan that originally converted FTE into hours.  There are a lot more records, so be sure to use the 'aggregate' feature on the report to roll up totals.

[phil_bool_unifi]

Very interestingly, going back to the original issue, the SN Demo of the Resource Management Workspace given today included creation of a Group resource assignment where 2 out of 8 group members needed to be assigned.  In that case, the assignment happened in the way we want, where all the group members got an assignment for the appropriate period, and the time was split between them.  I've asked if Operational Group Assignments are expected to work the same way, and the response is Yes, so it may be worth making sure you've updated the Resource Mgt Workspace to the May store release and checking if the issue still occurs.