[ProjectServer 2013] Resource authorization data lost on PSI Resource Update

Question

Hi,
as the title says I noticed that sometimes resource authorization data of a resource/user is lost in ProjectServer 2013 on a PSI resource update. Since it did not happen every time for every resource (user) I tried to investigate this issue in more detail.
I found out that it is related to a change in the resource availabilities. A resource/user loses its resource authorization data on a UpdateResources PSI call when the following criteria are fulfilled:
- "Earliest available" or "Latest available" date is set
- Resource/user has more than one ResourceAvailablities row
- Max units are changed for one of the rows
Since this is a quite complicated and specific issue here are some simple steps to reproduce it on a PWA instance:
1. Create new resource/user.
2. Enter any date in the "Earliest available" field and assign the user to some security groups.
3. Programmatically change the max. units of any ResourceAvailablityRow and update the resource via the UpdateResources PSI call.
4. Open the user in PWA. The security group associations will not be there any more.
I have successfully reproduced this issue on two different PWA instances on two different servers.
Did i miss anything obvious or is this a well known issue?
If yes are there any workarounds?
Did anybody else run into this issue?
Thanks in advance for you help,
Michael

Answer 1

I created a Fiddler trace (see link at the end of the post) but i could not find anything suspicious in there.
If it helps here is the code that i use to reproduce the issue:
var singleResDs = resourceClient.ReadResource(resUid);
var maxUnitsRow = singleResDs.ResourceAvailabilities.First();
maxUnitsRow.RES_AVAIL_UNITS = maxUnitsRow.RES_AVAIL_UNITS + 1;
resourceClient.CheckOutResources(new Guid[] { resUid });
resourceClient.UpdateResources(singleResDs, false, false);
resourceClient.CheckInResources(new Guid[] { resUid }, false);
As you can see there is nothing special about it.
I also checked the patch level on one of the servers and its 15.0.4569.1506 which corresponds to SP1 (April 2014). I can definitely try to install the newest CU and check if that fixes the issue.
Fiddler trace:
http://bit.ly/1DvaWsZ
EDIT:
I have now installed the March 2015 CU (15.0.4701.1001) and the issue is still existing.