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.
