#306 MPXJ 5.5.7 and Microsoft Project 2016: Issue with assignment 'Work Contour' attribute.

[Deepak Phalke]

Hi Jon,
This is about an issue with assignment 'Work Contour' attribute.

Use case (Valuesin MS Project 2016): **
Task1 with 2 assignments
Assignment1, work- 24hrs, %work complete- 35%, units- 50%, ** Work contour-Flat
Assignment2, work- 80hrs, %work complete- 21%, units- 100%, Work contour-Flat

While reading Assignment1 through MPXJ, it shows 'Work Contour' as 'CONTOURED' instead of 'Flat'. The issue occurs only with MSP 2016.
When same file is opened in MSP 2010 or 2013 and imported, for the assignment, mpxj shows the Work contour as Flat.

As per my initial investigation, it appears below code in MPXJ sets the assignment 'work contour' as Contoured casuing the issue.

ResourceAssignmentFactory.process() (Line no 248 to 265 of above function from MPXJ 5.5.7)

 if (timephasedWorkData != null)
            {
               if (timephasedFactory.getWorkModified(timephasedWork))
               {
                  assignment.setWorkContour(WorkContour.CONTOURED);
               }
               else
               {
                  if (timephasedWorkData.length >= 30)
                  {
                     assignment.setWorkContour(WorkContour.getInstance(MPPUtility.getShort(timephasedWorkData, 28)));
                  }
                  else
                  {
                     assignment.setWorkContour(WorkContour.FLAT);
                  }
               }
            }

When I saved MSP 2016 file to .xml format instead of .mpp, it shows the work contour correctly as FLAT.

Attachments:
MSP-2016.mpp ( please open this file with MSP 16 only and not with earlier MSP releases.)
MSP-2016.xml : (above MSP-2016.mpp file saved to xml format from MS Project 2016 and it shows work contour as flat for the Assignment1)

Could you please take a look into this? Please let me know if you need more information.

Thanks for your help,
Deepak

[Deepak Phalke]

Hi Jon,

Could you please take a look? Please let me know if you need more information on this.
Thanks,
Deepak

[Jon Iles]

I've made some changes to address this. I won't say I've fixed it as this code depends on heuristics, we just don't understand the file format well enough. The changes are on GitHub and will form part of the next MPXJ release.

[Deepak Phalke]

Hi Jon,
Thanks for your help!!
I have tested the fix in MPXJ 5.13.0 and above issue is no more reproducible.

Regards,
Deepak