Why convert External Task to Local Task?

Hi,


Please follow the step:

1.Move the “ProjectB.mpp” and “ProjectA.mpp” in attachment to “c:\aspose” .
2.Run the code as below :

public static void main(String[] args) throws ParseException {
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();
}
}

Project asProject = new Project(“c:\aspose\ProjectB.mpp”);
// Save the Project
asProject.save(“c:\aspose\output_external_task.mpp”, SaveFileFormat.MPP);

System.out.println(“ok”);
}

3.Open the “output_external_task.mpp”.

I have external task in “ProjectB.mpp”, why the external task convert to local task after save as to “output_external_task.mpp”? Do you have any way that I can keep the external task?


Best Regards!
zhencheng.guo

Hi Zhencheng,


Thank you for writing to Aspose Support team.

This appears to be a bug with API functionality that we have logged as TASKSNET-1658 in our issue tracking system for further consideration by our Product team. We’ll update you here once there is some information or update available in this regard.

Hi kashif,


In addition, the external predecessor will change to msp uid from full path, is it a defect as well?

Best Regards!
zhencheng.guo

Hi Zhencheng,


This issue is already highlighted to product team where full path is replaced with MSP uid. You will be automatically notified once any update is received regarding the logged issue.

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


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

Hi,


Has it fixed on Java version?

Best Regards!
zhencheng.guo

Hi Zhencheng,


The issue has been fixed in .NET version of the API and will be part of the Java version automatically once it is available for download. We’ll update you here once the Java version is available for download.