Expose Accounting Company Configuration API Endpoints

Use the new Accounting Company Configuration API endpoints to retrieve and update data in the Accounts form. These API endpoints honor existing validations and restrictions as well as security requirements at the application level.

Updates to the Users Form

This change applies for cloud customers who have the Flex Cloud ODBC Connectivity module activated.

In Settings » Security » Users, in the Cloud ODBC Settings section of the Users form, the Password field has been removed. As a cloud administrator, you see this change when you configure your company's cloud users with ODBC access. Now when you select the Enable Cloud ODBC Connectivity checkbox in the Cloud ODBC Settings section, only the Email field is enabled and required.

Removal of the ODBC Password field in the Users application does not affect your ODBC credentials. The Password field has been removed because Deltek now manages the password for the ODBC service. If you need to change your ODBC password, contact Deltek Support directly.

Updated the Smart Summary Tooltips

The client Smart Summary tooltips were updated in the following locations: Hubs » Firms and Settings » General » Options.

Defect 1993898: This issue occurred when you re-used the number of a voided invoice for a new invoice. On the Invoice History tab of the Interactive Billing form, the invoice details for the new invoice were the same as the details for the voided invoice.

Defect 2021430: This issue occurred when you edited an invoice using third-party software and then uploaded the invoice on the Interactive Billing form. On the Invoice History tab, when you selected the uploaded invoice and then selected Print, Vantagepoint displayed the invoice as code. This issue happened if the following were true:

• You previously voided an invoice and you were replacing that invoice.

• The voided invoice had an earlier invoice date than the new invoice.

Defect 1970181: When you tried to add a Monthly Recurring activity in the Activities hub, you received an error message.

Defect 2015805: When you added a new phase with at least one associated task and the Enable Overall Revenue Limit was selected at the WBS1 level, you could select the phase in the Phase to Adjust field. However, the Task to Adjust field was locked (instead of displaying the associated task). After you clicked Save, the Task to Adjust field displayed the same value as the Phase to Adjust field.

Defect 2018870: When you switched View options on the Edit Project Structure form, some of the data in the column fields did not refresh automatically.

Defect 1988429: The currency symbol displayed in the Total Billed field on the Project Review form was incorrect when the project and billing currencies differed.

Defect 2006828: The indirect expense cost was not included when calculating the job-to-date (JTD) earned profit amount in Project Review.

Defect 2026526: When you created, saved, and submitted expense reports in Mobile Time and Expense, default tax codes were not used and no tax amounts were calculated for the expense reports in Vantagepoint (My Stuff » Expense Report). This issue occurred if the Expense Location field on the Expense Report form was hidden from your security role and your employee record did not have an entry in the Default Expense Location field on the Employees form in the Employees hub.

Defect 2027012: When you searched for a project to add hours or units--to your timesheet or to your expense report--there was a significant delay in loading and displaying the list of projects on the Find Project screen.

Defect 1999833: This issue occurred when you configured a pie chart dashpart in the Dashpart Designer with a grouping, date range, and drill to, if the drill to dashpart was a table dashpart configured with a date range (also in the Dashpart Designer), with the Filter Drill to Dashpart option enabled on the Drill To dialog box. When you displayed the affected drill to dashpart from the pie chart dashpart, you received this error message: "Invalid column name 'TransDate'."

Defect 1493821: This issue occurred when you, on the Options tab of Purchase Order reports, selected the Bottom Clause and Page Break Bottom Clause checkboxes. When you tried to print a draft purchase order report, submit a final purchase order, or reprint the purchase order, Vantagepoint did not apply the page break settings. The text that you specified for the Bottom Clause was displayed on the first page of the report, but was not included on succeeding pages.

Defect 1985079: This issue occurred when you did not specify a default font size in Settings » General » Options and, on the Layout tab of the report options, you selected the HTML Formatting checkbox. When you tried to run, schedule, email, or download a report as a PDF file, you received the following error message: "An error occurred during rendering of the report."

Defect 1993259: When you ran the CRM Project Summary report, the Ajera-related financial columns were visible even if your role was not supposed to have access to those columns and there was no option to remove the columns in the report's options.

Defect 2009610: This issue occurred on the Voucher Ledger report when you were using multiple currencies. In the Report At field on the Options tab, if you selected the Functional Currency reporting amount and then ran the report, gains and losses on unpaid vouchers were excluded.

Defect 2016652: When you processed a change order for a purchase order, the Vendor field incorrectly became editable.

Defect 1993040: In the Queue Processes grid, when you selected an AR Aging Alert Job process and resubmitted it, you encountered a security role error. This issue occurred when you, in Settings » Billing » Alerts, displayed the AR Aging dialog box and specified a project in the Selected Projects field.

Defect 2026994: When you upgraded to Vantagepoint from Vision, a “Violation of PRIMARY KEY constraint” error displayed in the error log if the upgrade encountered a project plan where an expense, consultant, or unit assignment was on a WBS level and that same WBS level had planned labor codes under it on the Labor tab. After you encountered the error, no more project plans were upgraded even if the plans didn’t have the same condition.