Problem with Predecessors

Aspose.Tasks Product Family
1

Hi ,


I found that the predecessors are incorrect after save the file “Task-Predecessor-Test.mpp” to “Pre-test.mpp”, you can run below code and check both of the predecessors:


public static void main(String[] args) {
FileInputStream fstream = null;
try {
// Create a stream object containing the license file
fstream = new FileInputStream(“Aspose.Tasks.lic”);
// Instantiate the License class
License license = new License();
// Set the license through the stream object
license.setLicense(fstream);
} catch (FileNotFoundException e) {
e.printStackTrace();
} catch (Exception e) {
e.printStackTrace();
}finally {
try {
fstream.close();
} catch (IOException e) {
e.printStackTrace();
}
}
// Create a new project
Project proj = new Project(“Task-Predecessor-Test.mpp”);
proj.save(“Pre-test.mpp”, SaveFileFormat.MPP);
}


I attached a file for test it,

The config I used to reproduce the issue:
- Win7
- MSP 2013
- Java 8


Best Regards,

2

Hi Zhencheng,


Thank you for contacting Aspose support team.

This issue is reproduced and logged under Id: TASKSJAVA-216 for further investigation by the product team. You will be automatically notified once any update is received in this regard.
3

The issues you have found earlier (filed as TASKSJAVA-216) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
4

Hi,


I retest the issue by Aspose9.5.0, but the issue still exist, please check it again, thanks!


zhencheng.guo
Best Regards!
5

Hi,


We regret the inconvenience caused to you.

Could you please elaborate which version of MSP you are using at your end? Please share a screenshot of the differences you have found with us for our reference.
6

Hi kashif,


The version of MSP is 2013, I uploaded the pic as attachment, you can observe the differences of the predecessor.

zhencheng.guo
Best Regards!

7

Hi Zhencheng,


Thank you for sharing your feedback. We’ll get back to you once we have further information available in this regard.
8

Hi kashif,


How is it going?

9

Hi,


We regret the inconvenience caused to you.

Unfortunately, there is some complexity involved in resolving this issue and our Product team is investigating it further for resolution. I am afraid that a fix for this won’t be available in the upcoming release of the API due to the complexity involved. We’ll update you here once there is some update available in this regard.
10

Hi kashif,


I mean that can you reproduce this issue for Aspose9.5.0?
11

Hi,


Yes, we were able to observe the issue and found that your source MPP file was created in MSP 2003 that can not be saved to newer version of MSP i.e. the saved file will have these issues when opened in newer version of MSP. This involves alot of complexity and will take some time to be investigated and rectified.

For now, you can:

1. Use MSP 2010 only where this issue is fixed

2. Use template file of latest version i.e. open the input in MSP 2013 and resave it. This will solve this problem for time being.