When converting 1.mpp file to 2.xml and then back from 2.xml to 3.mpp the Microsoft Project shows different value for duration field. It is shown on the picture below:
image.png (68.1 KB)
The lower file on picture is before conversion (1.mpp) the upper file is after conversion (3.mpp).
Moreover after converting 3.mpp again to xml (4.xml) we can see differences between 2.xml and 4.xml in file - removed calendars, TimephasedData, changed some properties.
Can you explain why is that?
mpp.zip (65.7 KB)
@rbednarek ,
we need some time to investigate the issue.
@rbednarek
the defect was found which results in incorrect calculation of timephased data for the original file.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): TASKSNET-11098
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
Thank you for response. When can we expect the fix?
@rbednarek ,
the fix will be released in version 24.2 or 24.3.
The issues you have found earlier (filed as TASKSNET-11098) have been fixed in this update.
Thank you for fixing the issue with duration field.
Still the problem with calendars exists.
Here are 2.xml and 4.xml file obtained using your new version of library (24.2.0)
xmls.zip (9.1 KB)
Again the conversion was like this:
1.mpp → 2.xml → 3.mpp → 4.xml
4.xml does not contain two calendars defined in 2.xml
Why? Can you explain or fix it?
@rbednarek ,
the issue with calendars has a lower priority than issue with duration field and will be fixed in a future release.
@rbednarek
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): TASKSNET-11117
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
But how can it be low priority if this is the basic functionality of MS Project?
The export/import functionality of your library is not compatible with itself
@rbednarek ,
The post is about that fact that the issue with calendars has a priority lower than the priority of the issue with duration field because it doesn’t affect dates of the project. It doesn’t mean that priority of the issue is low.
The issues you have found earlier (filed as TASKSNET-11117) have been fixed in this update.
Download