Defect 2409212: This issue applies for dashboards that have Project, Project Detail, or AR Detail dashparts with a SQL Where clause that uses OrgLevel2 or OrgLevel3 from Organization table on the role's record level View Access for Projects. When you tried to run and display a dashboard with any of those dashparts, you received an error message stating that the column name OrgL2, OrgL3, or both were invalid.

Defect 2412853: 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 2411295: 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 2413860: 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 24138792412851: On the Project Earnings report, the Business Development Lead and Marketing Coordinator columns were blank.

Defect 2404364: This issue occurred when you upgraded from Vantagepoint version 7.0 to 2025.1. When you opened an existing proposal template, the Select Projects option was missing in the Text Properties pane. This option has been added to the pane for the first page of the template, as a partial fix.

Defect 2410749: This issue occurred when you upgraded from Vantagepoint version 7.0 to 2025.1. When you opened an existing proposal template, the Select Projects option was missing in the Text Properties pane for all the pages after the first page of the template.

Defect 2412849: 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."

Defect 2412851: This issue occurred when a source database had a user-defined field with a Comment History field type in a hub other than 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: "Violation of PRIMARY KEY constraint in the database.....Cannot insert duplicate key in object..... The statement has been terminated."