Hi!
Am running Aspose.Task version 3.4
When I tried to read mpp file I found 2 issues below:
1) The name of Resource’s Calendar is always null.
2) Aspose lacks Resource Type = Cost (although Microsoft Project supports 3 types for Resource: Work, Material and Cost).
Could you please check it asap.
Thank you so much!
With regards,
-Ngoc Pham.
Hi Ngoc Pham!
I have linked one existing issue ‘Missing resource calendar’s name when read project data from MPP file.’ with ID = 21623 to your forum thread. The issue is in coming December plans.
And I have created a new issue ‘Incorrect cost resource’s type reading from MS Project 2007/2010 MPP files.’ with ID = 21864 and linked it to this forum thread too. This issue is in our December plans as well.
Sorry for your inconvenience.
Thanks Sergey for quick reply,
We are in development, and in urgent for solving these issues to use in our product that will be released in late December, Could you please make a patch ASAP for us with these 2 solved bugs only so that we can use in our product ? The product that we will release is very mission-critical to us.
Here is our order information you can check.
|
Order ID: 101115110534 |
|
Order Date: 11/15/2010 |
Hope your reply soon !
Many thanks !
Thanh
Hi,
The first issue is under development currently and we can shift it to this month release. The second one needs some investigation before but we’ll try.
Sorry again for the inconvenience.
Hi,
We have completed the second issue investigation. The problem is only with MS Project 2007 MPP files. You can check resource’s IsCostResource flag to define if the resource is a cost resource. You can find the element description in MS Project Data Interchange Schema reference here and in our documentation here.
We are going to fix the issue for MS Project 2007 MPP files in this month release. The product documentation will be updated accordingly.
Sorry for your inconvenience.
Hi Sergey!
The second issue also occurs with MS Project 2010 MPP/XML and 2007 XML file 
Yes, I have been using this field to check whether the resource is a cost resource or not. I just wanna notify to you this issue.
Thank you for your time and consideration again.
Am looking forward to seeing the next release. It’s so important for our product.
Have a nice day Sergey.
Cheers,
-Ngoc Pham.
Hi Ngoc Pham,
Could you please provide as with the project data (or just some part of it) when the issue has place for MS Project MPP 2010 and XML formats?
I can see the correct flag values for these cases at my side. Sorry for your inconvenience again.
Thank Sergey for quick support,
To the second bug, we found that it occurs in XML/MPP file in MSP 2007 and 2010 also. Could you please double check ?
It would be highly appreciated for your team effort in fixing 2 fixes promptly. Hope to get the patch in this month or the early of December.
With regards,
Thanh
Hi Thanh,
Could you please attach the XML and MS Project 2010 MPP file to this forum thread (put it in zip archive and use File attachment Add/Update button)? Or you can send it by e-mail using Contact/Send e-mail forum’s feature.
It can help us understand the problem at our side.
Hi Sergey!
Here is MSP 2010 and 2007 MPP/XML file 
Ah! The flag values for the resources are always correct. I just talk about ResourceType
Sorry if I makes you missunderstand.
Thank for your support.
Cheers,
-Ngoc Pham.
Hi Ngoc Pham,
Sorry for my misunderstanding. We have updated MS Project 2007 MPP files reading by adding support of IsCostResource flag and going to include it in the next release.
But now you have to check the flag (IsCostResource) to define if the resource is a Cost resource, if flag is false you can check resource’s type to define if it’s a Work resource or Material one. I think MS implemented the approach for XML schema backward compatibility and we followed them.
We need some time to understand if we can just add the third value (Cost) to ResourceType enumeration without any impact on customers who use the old approach.
The same is true for Budget resource, the feature is under development now but the MS Project Data Interchange Schema has a separate flag for it too (see the flag description here).
Sorry for your inconvenience.
The issues you have found earlier (filed as 21864;21623) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.