Task Extended Attributes

With ASPOSE Tasks 8.9.0.0

I am attempting to obtain the Extended Attribute values from a Task and it is current giving me the first value for each list item instead of what the user has selected in the mpp.

Below is the code.

private List GetTaskMappingValues(List projectMappings)
{
List taskMappingValues = new List();

foreach (Task task in LeafTasks)
{
ProjectMappingValues info = new ProjectMappingValues();
info.MicrosoftProjectTaskId = task.Get(Tsk.Uid);
// Store the mapping by MicrosoftProjectColumnName
Dictionary<string, ProjectMapping> mappingLookup = new Dictionary<string, ProjectMapping>();
foreach (ProjectMapping m in projectMappings)
{
mappingLookup.Add(m.MicrosoftProjectColumnName, m);
}
// Store the mapping values
Dictionary<ProjectMapping, string> mapValues = new Dictionary<ProjectMapping, string>();
foreach (ExtendedAttribute extendedAttributes in task.ExtendedAttributes)
{
string val = extendedAttributes.Value;
if (mappingLookup.Keys.Contains(extendedAttributes.AttributeDefinition.FieldName))
{
mapValues.Add(mappingLookup[extendedAttributes.AttributeDefinition.FieldName], val);
}
}

foreach (ProjectMapping projectMapping in projectMappings)
{
if (!mapValues.ContainsKey(projectMapping))
{
Log.LogWarning(string.Format(“Task ‘{0}’ does not have a mapping for ‘{1}’.”, task.Get(Tsk.Name), projectMapping.Type));
}
}

info.AssignmentMappings.Add(task.Get(Tsk.Uid).ToString(), mapValues);
taskMappingValues.Add(info);
}

return taskMappingValues;
}

Attached is a zip containing a Project 2013 file with the associated information.

Hi Craig,


We are sorry for the inconvenience caused to you.

We were able to observe the issue at our end and have logged it as TASKS-34409 in our bug tracking system for further investigation by our Product team. We shall update you here as there is some information available about the problem.

Thanks for the quick reply.

Are you able to provide a possible ATA on a solution or fix?

This is functionality that we would like to be able to provide to our customer in the near future. Knowing this information will provide knowledge into a possible timeline for its implementation.

Thanks again.

Craig

Hi Craig,

We are sorry for a delayed response.

Unfortunately, there is no ETA available for the issue by now as the issue is pending for analysis by our Product team. We usually do monthly Product releases and this month’s release has already been scheduled. We have requested an ETA from our Product team and shall share it here as soon as it is available.

Thanks again for your quick response. Best of luck on implementing a fix.

Hi Araig,


You are welcome.

Has there been any progress made on implementing a fix for this problem. It’s been a while since our last conversation in regards to this problem and I figured I would check back.


Thanks.
Craig

Hi Craig,

The issue has been fixed and will be part of our upcoming release of Aspose.Takss for .NET 9.3.0. We’ll update you here once the fix version is available for download.

Thanks for the reply. Do you have any idea on when the new release will be available. Thanks!

Hi Craig,

We have requested an ETA for the release from our Product team and will update you here as soon as some information is available in this regard.

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


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