How do Microsoft Project monthly patches impact CA PPM?

Document ID : KB000011553
Last Modified Date : 15/06/2018
Show Technical Document Details
Question:
How do Microsoft Project monthly patches impact CA PPM (Clarity)?
Answer:

For each respective version of CA PPM (Clarity), we test and certify specific Versions/Releases and Updates of Microsoft Project that will integrate with our product, as noted in the Compatibilities section of the Release Notes (which can be accessed at: https://docops.ca.com)

Beginning in 2015 Microsoft started pushing out regular Updates for its Office Suite and MS Project. We have found that some of the code changes that are pushed in these Updates can cause issues with the CA PPM integration. As a result, end users may experience various issues following a Microsoft Project Update application.

For Microsoft Project Updates pushed between our Product releases, beginning with CA PPM (Clarity) version 14.4, we conduct standard regression testing to determine if said Microsoft Project Update will cause potential issues with the integration for the CA PPM (Clarity) GA version available at that time. This Knowledge Base article will be updated with the latest supported versions following the Microsoft Project Updates tested. If there is an update we will not support due to the impacts it has on our Integration, we will document that here as well.

If an issue/defect is found during our testing, it is then reported back to Microsoft as a defect within Microsoft Project and then follows Microsoft’s 'rules' for fixing defects.

Microsoft Updates that are not supported

Based on our testing, the following are Microsoft Project Updates that have been determined to have impacts and cause adverse effects to the CA PPM (Clarity) and Microsoft Project Integration.  These Updates should not be installed as we do not support their use due to these issues.  

  • Microsoft March 2015 Update: Causes project name to be changed to its internal project id when saved back to PPM
  • Microsoft November 2015 Update: Causes tasks exported with 1 or 0 day duration, resource allocation changes to 0%; task may export as 100% complete
  • Microsoft December 2015 Update: Causes projects with assignments to hang or crash when exporting to MSP (reported to Microsoft)
  • *Microsoft February 2016 Update: Fixes previously reported issues, however Actuals & ETC may be impacted due to a Microsoft code change. This Security Update is supported (in the MSP New Driver only) starting in CA PPM 14.4. 
  • Microsoft November 2016 Update: Causes Remaining Work (Referred as ETC in PPM) to be removed on export to MSP

* The February 2016 Update is supported in CA PPM 14.4 and higher.

NOTE: all of the adverse effects that impact the PPM / MSP integration have been resolved through cooperation between CA PPM Engineering and Microsoft; applying the latest Microsoft Update (e.g April 2018 will effectively resolve the impacts caused by the problem updates listed above, which must be uninstalled.) 


Microsoft Updates supported in 14.4 MSP New Driver and higher

The below updates have been found to have no issues in CA PPM 14.4 and higher MSP New Driver based on our testing. Note that no security updates are supported with the MSP Legacy Driver.

It's recommended to be on the latest supported update listed below, as there have been multiple defects fixed in the later updates. Microsoft updates are cumulative, so fixes in previous updates are included in the latest update. 

  • Microsoft February 2016 Update: Fixes previously reported issues, however Actuals & ETC may be impacted due to a Microsoft code change in versions lower then CA PPM 14.4. This Security Update is supported (in the MSP New Driver) in CA PPM 14.4 and higher MSP New Driver. 
  • Microsoft May 2016 Update: No issues found in CA PPM 14.4 and higher MSP New Driver in our testing.
  • Microsoft July 2016 Update: No issues found in CA PPM 14.4 and higher MSP New Driver in our testing.
  • Microsoft October 2016 Update: No issues found in CA PPM and higher MSP New Driver in our testing. This includes the fixes for two issues:
    • An unexpected increase duration on a fixed duration task type.
    • A completed task finish date may show as the end of the week.
  • Microsoft December 2016 Update: No issues found in and higher MSP New Driver in our testing.
    • See Microsoft's December 6, 2016, update for Project 2013 or Project 2016 for a list of fixes included in this update. 
  • Microsoft January 2017 Update: No issues found in and higher MSP New Driver in our testing.
    • See Microsoft's January 3, 2017, update for Project 2013 or Project 2016 for a list of fixes included in this update. 
  • Microsoft February 2017 Update: No issues found in and higher MSP New Driver in our testing.
    • See Microsoft's February 7, 2017, update for Project 2013 or Project 2016 for a list of fixes included in this update. 
  • Microsoft March 2017 Update: No issues found in and higher MSP New Driver in our testing.
    • See Microsoft's March 7, 2017, update for Project 2013 or Project 2016 for a list of fixes included in this update. 
  • Microsoft April 2017 Update: No issues found in and higher MSP New Driver in our testing.
    • See Microsoft's April 4, 2017, update for Project 2013 or Project 2016 for a list of fixes included in this update. 
  • Microsoft May 2017 Update: No issues found in and higher MSP New Driver in our testing.
    • See Microsoft's May 2, 2017, update for Project 2013 or Project 2016 for a list of fixes included in this update. 
  • Microsoft June 2017 Update: No issues found in and higher MSP New Driver in our testing.
  • Microsoft July 2017 Update: No issues found in and higher MSP New Driver in our testing.
  • Microsoft September 2017 Update: No issues found in and higher MSP New Driver in our testing.
    • See Microsoft's September 5, 2017, update for Project 2013 or Project 2016 for a list of fixes included in this update.
  • Microsoft October 2017 Update: No issues found in and higher MSP New Driver in our testing.
    • See Microsoft's October 3, 2017, update for Project 2013 or Project 2016 for a list of fixes included in this update.
  • Microsoft November 2017 Update: No issues found in and higher MSP New Driver in our testing.
    • See Microsoft's November 7, 2017, update for Project 2013 or Project 2016 for a list of fixes included in this update.
  • Microsoft December 2017 Update: No issues found in and higher MSP New Driver in our testing.
    • See Microsoft's December 5, 2017, update for Project 2013 or Project 2016 for a list of fixes included in this update.
  • Microsoft January 2018 Update: No issues found in and higher MSP New Driver in our testing.
  • Microsoft March 2018 Update: No issues found in and higher MSP New Driver in our testing.
  • Microsoft April 2018 Update: No issues found in and higher MSP New Driver in our testing.
Notes: 
  • Fixes may vary based on Microsoft Version, so be sure to check the link for your specific version of Microsoft Project. 
  1. To find out which update is installed on any given workstation, go to: Control Panel > Uninstall a Program > View Installed Updates > sort by the Program column 
  2. You should then look for the highest KB number in the section for Microsoft Project and google the KB number to see for which month the update applies.
  • Additionally, we encourage all customers to fully test a newly released Microsoft Project Update before applying the Update to ensure there are no issues based on your usage of the products and integration.  If in your testing you find an issue not documented above, please log a case with CA PPM (Clarity) Support. We can then work with you and log a case with Microsoft to address any potential Microsoft Project defects caused as a result of the Update.
  • If you do find an issue or have installed one of the aforementioned Microsoft Project Updates, our recommendation is to remove problematic Microsoft Project Updates.
Additional Information: