I am reading the MPP file, which is a resource pool. For some resources, a mark indicates that their availability is exceeded. I do not make any changes, I save this file.
p.save (fileName, SaveFileFormat.MPP);
Opening a file in MS Project shows that resource availability marks have been reset.
To check, immediately after reading the MPP by the debugger, I looked at the Rsc.OVERALLOCATE property, it was False for all resources.
For fun, I added a new resource to the file with the setting of this property.
Resource r = p.getResources (). Add (name);
r.set (Rsc.NAME, name);
r.set (Rsc.CODE, Integer.toString (dvpUserId));
r.set (Rsc.CALENDAR, c);
r.set (Rsc.OVERALLOCATED, new NullableBool (true));
After saving in MPP format and viewing in MS Project, I saw that the mark was saved.
Obviously this is a very unpleasant bug for me when reading the MPP file.
If the opportunity to get around this bug?
Additionally, I noticed this is not so critical, but still. The dates of creation of resources in the export to XML became current, that is, information about their creation in the original MPP file was lost.
I can more accurately say that the problem with the lack of the Rsc.OVERALLOCATE property is due to the fact that when reading the MPP, information about the Use of resources in other MPP files is lost. This is very critical.