My title
  • Predictive Analytics for Improved Cost Management  
Resources > Product Known Issues

Known Issues

The table below includes some of the known issues in PRICE® Systems products. We include only issues we think are important or may potentially impact many customers, as well as a temporary solution until the issue is fixed. Use this information to decide when to upgrade to a new release and to see if we are aware of issues affecting you.

We are adding new issues as we discover them. When we release a new software update that addresses an issue, we will add a link to download the update in the Status column.

Last updated: June 14, 2017

 

Product

Description

Status

TruePlanning 2016 Update 1 Projects created in TruePlanning 2016 Update 1 where cost objects have the same name at the same level in the PBS cannot be reopened once saved to a tpprj file.            




Resolved in TP2016 Update
TruePlanning 2016  Software costs estimates are incorrect when specifying certain languages with COSMIC Function Point size units. The programming languages are: C#, Java, Oracle, PHP, SAP or VB. 




Resolved in TP2016 Update
 TruePlanning 2016  The Phoenix® Integration ModelCenter® interface does not work properly with standalone desktop installations.  It always looks for a connection to a database.




Resolved in TP2016 Update
 TruePlanning 2016  When importing multiple WBS or mappings into the Manage Mappings dialog, and changing the order that they are listed within the dialog, there is a risk that any newly or previously created mappings will not be retained when saving the project.




Resolved in TP2016 Update
 TruePlanning 2016  TruePlanning® 2016 cannot launch after being installed and prompts a message about “api-ms-win-crt-runtime-l1-1-0.dll” missing from the computer. Typically, this occurs because Microsoft® Visual C++ 2015 Redistributable did not install correctly.


Temporary Solution: Perform a repair on the 2015 redistributable installation or reinstall the redistributable. The TruePlanning® 2016 installation does not need to be changed.


 Open
 TruePlanning 2016  Saving a project to a Microsoft® Excel® file and then importing that file into another open project sometimes results in extraneous costs being shown for cost objects.




Resolved in TP2016 Update
 TruePlanning 2016  Projects created in TruePlanning® versions 14.0 and 14.2 were not using the appropriate rates for currency conversions when opened in TruePlanning® version 16.0.




Resolved in TP2016 Update
 TruePlanning 2016  When using the new Templates, if a Missile Template is selected, it may fail with an error. This is because the Missile Templates use a catalog called "equations" for calculating Fuel Costs.




Resolved in TP2016 Update
 TruePlanning 2016 The "First Piece Cost" and "Nth Unit Cost" (FPC/NUC) metrics for Hardware COTS items are incorrect when the fiscal year for "Results" (set in Project->Properties->Economics) and that for the Hardware COTS "Purchased Hardware Units Costs" are different. This also affects their parent System/Assembly FPC/NUC metrics. Only the FPC/NUC metrics are incorrect in this circumstance. The costs on the "Results" tab are correct.



Resolved in TP2016 Update