Defect 2417327: When a plan had a WBS3 task and labor code under it, and there were expense, consultant, or unit assignments under the WBS2 phase level, bad data was generated during the upgrade. If Time Phase Data (TPDs) were present under those assignments, the planned data did not upgrade, and an error appeared, although the plan itself was upgraded.

Defect 2420962: When you generated planning data that included expense and consultant planned amounts, project planning and reporting experienced delays.

Defect 2417319: When you added a new phase to an existing project record on the Projects form and saved the changes, an error occurred due to a date data type conversion issue. This happened if you changed the fee allocation method to Use Revenue Forecasts option by using the Search and Replace utility or by using a workflow.

Defect 2416276: This issue applies if you import credit charges in Vantagepoint using the Credit Card Reconciliation application. Matching expense lines and credit card charges did not display on the Matched Credit Card dialog box when the entry in the Merchant Description field for an expense line in an expense report did not exactly match the description for the import charge.

Defect 2411286: This issue applies for the Project Earnings report. The JTD Unbilled Gain/Losses column in the report was blank when the opt-in feature titled Performance Improvements: Project Earnings Report - Only Include Needed Columns in Query was enabled in Settings » General » Opt-In Features.

Defect 2413884: On the Project Earnings report, the Business Development Lead and Marketing Coordinator columns were blank.

Defect 2413900: The Project Earnings report did not display the client address when the opt-in feature titled Performance Improvements: Project Earning Report - Only Include Needed Columns in Query was turned on in Settings » General » Opt-In Features.

Defect 2412850: This issue occurred when a source database had a user-defined field with a Comment History field type in the Projects hub. When you tried to import settings into a target database in Transfer Settings, the import failed, and you received the following error message: "There is already an object named <xxxxxx> in the database."