Minnesota 2019 Tax Update

Minnesota's withholding tax tables for 2019 have been updated for the second time, due to the Minnesota tax law that was enacted on May 30, 2019. Vantagepoint has been updated to use the latest Single and Married tax tables effective January 1, 2019. For more information, see https://www.revenue.state.mn.us/sites/default/files/2019-09/wh_tables_19_0.pdf.

Virginia 2019 Tax Update

The standard deduction amount increased from $3,000 to $4,500. For more details, refer to https://www.tax.virginia.gov/sites/default/files/vatax-pdf/employer-withholding-tables.pdf.

Script for Optimizing Database

After performing major database changes such as migrating to Vantagepoint, database upgrades, or data imports, you should run the script for Optimizing database. The script defragments heap tables together with rebuild indexes and updates statistics.

For more information, see the Deltek Vantagepoint 2.0 Installation and Maintenance Guide.

 

Support for Single Sign-on in Microsoft Azure

Single Sign-on between Vantagepoint and Microsoft Azure has been modified to reflect Microsoft updates to the Azure portal interface. The changes are:

• The new Azure Active Directory » App registration blade replaces the legacy blade.

• You can now use the same app registration for webb/API or native app by registering the respective redirect URIs.

• App registrations that were created in, or displayed in, the legacy blade automatically appear in the new blade.

For more information, see Set Up Single Sign-On for Vantagepoint with Microsoft Azure Active Directory in the Cloud Administrator's Guide.

Updated PHP Version

The Touch Server for this version of the Deltek Vantagepoint mobile application has been upgraded to support PHP 7.3.10.

Defect 1182974: Non-billable units were incorrectly included in the phase total of a billing invoice. This occurred when the Use Rates for Reporting for Draft Invoices check box was selected for the Billing Backup report on the Billing Backup tab in Billing Terms for a project.

Defect 1195880: This issue applies for any projects with billing terms set to show the billed-to-date amounts on invoices (the Project Billed-to-Date check box is selected on the Format tab in Billing Terms for a project). The Billing Limits section of an invoice was missing the Prior Total Billing amount for prior invoices that were entered in Utilities » History Loading » Invoices and Receipt.

Defect 1200027: The Billing Backup report did not calculate the correct billing extensions for the hours billed. The first multiplier used in the calculation was applied correctly. A second multiplier was omitted from the calculation.

Defect 1191459: This issue applies for security roles that have record access to projects in use and the Apply Project Access to Billing check box is also selected on the Record Access tab in Roles Security. Users with this role received the following error message in Batch Billing when they tried to create a draft invoice: "Incorrect syntax near 'PR'. Incorrect syntax near 'LEVEL2'. Incorrect syntax near 'LEVEL3'."

Defect 1200573: When you created a new Batch Billing invoice run and selected the Batch Invoice list option, a "Message: You do not have access" error message displayed in the Queue Manager.

Defect 1177945: On the Units tab in Interactive Billing, when you completed a hold on a partial amount of a unit transaction and later transferred the held amount to another project, the entire cost for the original unit transaction was transferred instead of the partial amount.

Defect 1186340: When you downloaded an invoice record for editing, the subtotal and footer areas were removed and the default invoice format was used.

Defect 1191638: In Billing » Interactive Billing, when you tried to submit invoices for approval at the phase or task level of a billing group, you recieved a message saying that an approval is in process. However, the project / billing group did not display for approval in Hubs » Projects » Draft Invoice Approvals or Billing » Invoice Approvals. You had to submit invoice approvals at the main project level of the billing group.

Defect 1193178: You received a “Field_id does not exist” error when you did the following on the Interactive Billing form:

1. You clicked Other Actions » Download for Editing.

2. You edited the invoice, and then clicked Other Actions » Upload Invoice to load the invoice back into Vantagepoint.

3. You clicked the Accept action and created an invoice data entry file.

4. On the Invoice Accept dialog box, you edited values to match the edited invoice.

5. You clicked the Invoice Accept button on the Invoice Accept dialog box.

Defect 1194689: In Cash Management » Bank Reconciliation, when you associated statement dates with voided payment transactions, the dates were not saved. When you opened Bank Reconciliation again, the statement date of the voided transactions displayed as "New."

Defect 1194690: In Cash Management » Bank Reconciliation, when you voided a check transaction that was part of a larger EFT payment, the amount remained at 0.00. The voided check transaction should have been cleared and a negative offset amount displayed.

Defect 1188064: When you created a new payment run for a vendor and sent an AP email remittance, there was no content in the body of the email message that the vendor received.

Defect 1158838: In some cases, new hub records could not be saved because the auto numbering function stopped generating and assigning new ID numbers for hub records.

Defect 763870: When the auto numbering feature was enabled and multiple users created new hub records, duplicate opportunity numbers were generated.

Defect 1183668: When you entered an AR comment, the time stamp in the SQL database showed the local machine time instead of the expected UTC/GMT time.

Defect 1186496: On the Summary pane in the Firms hub, when you selected a firm and then clicked the Most Recent Project link, Vantagepoint displayed details for a different project.

Defect 1192042: This issue applies if you do not use automatic numbering for firms in the Firms hub. It applies for all firm types. You received a “Firm Number already exists” error message in the Firms hub when you tried to edit a firm that had the same firm number as another firm. This occurred if you upgraded from Vision to Vantagepoint. You also could not enter a new firm with the same firm number as an existing firm in Vantagepoint, as you could in Vision. Now you can edit a firm record that has the same firm number as another firm. You can also now enter a new firm and give it the same firm number as an existing firm. You will receive a warning message, but you can still save the new record.

Defect 1192177: When you tried to search on Invoice and Invoice Unpaid fields from the AR Review form in the Firms hub, no results were returned, even though invoices had been processed.

Defect 1192673: In Hubs » Firms » Voucher Review, the Vouchers to Include field automatically defaulted to Unpaid when you navigated away from the form, even when Unpaid was not originally selected in the field.

Defect 1166886: If you selected a project record on the Dashboard and then quickly clicked a different form, the cursor started spinning continuously and the record did not load.

Defect 1184259: When using TDM, sometimes files that were linked to opportunities before running a Vantagepoint upgrade were not linked to the associated projects after the upgrade process completed.

Defect 1186481: An error message was displayed in the Projects hub when you used a user-defined workflow if that workflow was configured with an action that used the Expression Builder and the PR.Probability field for an SQL expression, as specifed on the Expression Builder dialog box.

Defect 1190118: When you created a new project record, a Primary Contact Last Name is required error displayed.

Defect 1190662: When a WBS level included amounts on the Compensation tab in the Projects hub, if you added and saved another WBS level at the same level (for example, you added a WBS 2 when there was already a WBS 2 on the project), the amounts were incorrectly added from WBS 1 to WBS 2. This resulted in an incorrect compensation amount for the project.

Defect 1193077: In the Summary pane of the Projects form in the Projects hub, Vantagepoint did not display a warning message when you changed the project stage from Won to In Pursuit. This occurred even when Approved for use in Processing was selected on the Accounting tab of the Projects form.

Defect 1203269: You experienced performance issues when saving large projects (more than 600 WBS rows).

Defect 1191215: In Hubs » Projects » Billing Terms, when you worked on main projects with sublevels and enabled the Phase Terms option on the Sub-Level Terms tab, the corresponding phase options did not display.

Defect 1192679: In Billing Terms, you received the following error message when you tried to add or copy an add-on entry in the Add-ons grid, on the More Calculations tab: "The record you are trying to save has been updated by another user since you first selected it. In order to save your changes, you must reselect your record and make your changes again."

 

This occurred for projects that were converted from Vision or from earlier versions of Vantagepoint.

Defect 1185881: On the Contracts tab in Hubs » Projects » Contract Management, the contract amounts were incorrect for projects that were synchronized from Vision to Vantagepoint.

Defect 1191553: This issue occurred after you created a new project either manually or with a template, and you saved the project without entering any compensation for a phase. When you opened the Contract Management application in Hubs » Projects » Contract Management and tried to enter compensation in the Direct Compensation section for the phase, you received an incorrect syntax error message.

Defect 1173971: When you added invoices in Utilities » History Loading » Invoice and Receipt, their respective amounts displayed as zero (0.00) in the columns on the Invoices form in Hubs » Projects.

Defect 1179978: In Hubs » Projects » Plan, when you made changes to a checked-out plan record and clicked Save Baseline more than once, Vantagepoint took some time to save the record.

Defect 1198564: This issue applies if you use Google Chrome as your browser. After you selected a project on the Plan form and you clicked an action, such as Check Out in the Actions bar, the plan grid on did not display correctly on any of the tabs. The grid lines were not aligned correctly.

Defect 1168035: Vantagepoint automatically added plan assignments to a project plan when it detected that job-to-date (JTD) hours or amounts existed for that project for employees, expenses, or consultants, and no corresponding plan assignment currently existed. In some cases, if you attempted to perform an action that involved retrieving that project record at the same time that Vantagepoint was automatically adding assignments to its plan based on JTD hours/amounts, you received an error similar to the following: "Server Error: Transaction (Process ID 457) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction."

 

To address this problem in 2.0.9 and later versions, Vantagepoint no longer automatically adds assignments based on JTD hours or amounts when you display a project on the Plan form in the Projects hub, or when you generate planning reports that include a project with such pending assignments. Instead, an Add JTD Assignments option displays on the Actions bar on the Plan form if pending JTD assignments exist for the selected project. Click that option to add those assignments to the project plan. You do not need to explicitly check out the plan to add the assignments, but if someone else has the plan checked out, you cannot add the assignments until it is checked in. If no pending JTD assignments exist for the project, the Add JTD Assignments option is not visible.

 

As before, JTD assignments are still added automatically when you access a project plan in Project View or Resource View in Resource Management.

 

Note that even if there are pending assignments that you have not yet created, JTD hours and amounts for WBS elements in planning grids and on reports will be correct. However, if you display data at the assignment level, the sum of the JTD hours and amounts for those detail rows may not match the JTD values for their parent WBS rows because of the missing assignments.

Defect 1192184: When you created a new project and selected a primary client with an ampersand in the client name, you received a bad request error message.

Defect 1189634: When Vantagepoint was not set up to use labor codes, Budget Worksheet was incorrectly listed as a selectable option in the Budget Source field under Budget Validation on the Accounting tab of the Projects form in the Projects hub. That option should have only been available if labor codes were used. 

 

Note that if Vantagepoint was not set up to use labor codes and you selected that invalid Budget Worksheet option in Budget Source for a work breakdown structure (WBS) element, it was ignored, and no budget validation occurred for time records entered for that WBS element. In effect, it was as if you had selected None in Type of Validation. For such cases, the update process for 2.0.9 automatically removes the invalid budget source selection and sets Type of Validation to None.

Defect 1025082: Employees with staff level role access were able to view the absence requests of other employees even when the staff level role access did not have access rights to view the absence request of other employees. Employees with approver role access were also able to view the absence requests of other employees, even if they were not the assigned approver for those absence requests.

Defect 1198708: If you were not granted access rights to Settings » General » Options on the Overview tab of the Roles form in Settings » Security » Roles, you could not access the calendar when you selected My Stuff » Calendar.

Defect 1186363: The Organization column in Project dashparts displayed the organization for the project level in the rows for phases or tasks. The Organization column for phase and task rows should display the  organization for the phase or task, respectively, rather than the project organization.

Defect 1188591: When you edited a Project dashpart, an error message displayed if you selected a custom grid as a search criteria and also selected "on Phase Level", "on Task Level", or "on Any Level" to refine the search criteria in the Advanced Search Settings section of the New Project Search dialog box.

Defect 1194396: On the Date Range dialog box, when you tried to configure the Start and End fields by fiscal period and edited the number increment option to select the next or previous fiscal period, the number value needed to be 2 increments apart to display the next or previous fiscal period. The number value should not need to be 2 increments apart to display adjacent fiscal periods. To display the Date Range dialog box, click the edit option for the matching row item under the Date Range column on the Dashpart Designer form.

Defect 1098278: This issue occurred if you use approvals for expense reports. When you created and saved an expense report and quickly navigated to another application, you were prompted to save the expense report again. This caused duplicate approval records to be created, and you were unable to approve the expense report and/or the expense report line items.

Defect 1176575: When you ran a project report with report options and search criteria that should have limited the search results for the project structure (WBS), Vantagepoint instead returned data for all WBS levels, rather than only those phases and/or tasks that met the search criteria that you specified. For example, if you ran a Project List report designed to include only the projects, phases, and tasks associated with a specific project manager, Vantagepoint returned data for all phases and tasks in the project structure, whether or not they were associated with the project manager that you sepcified.

 Defect 1177194: When you ran the Role Summary report, you received the following error message: "String or binary data would be truncated. The statement has been terminated."

 This occurred when the following applied:

• You have a user-defined hub and reports for that user-defined hub. The name of the user-defined hub combined with the name of the report type for any of the user-defined reports is more than 30 characters.

• The user who tried to run the Role Summary report has the following setting entered for their security role in Settings » Security »  Roles: On the Access Rights tab, the Reports functional area has group access set up for the user-defined report whose report type name, when combined with the name of the user-defined hub, is more than 30 characters.

Defect 1180151: On the Options tab for the Timesheet Audit Detail report: If you set the Only Include Timesheet for Projects option to Search and then used the Advanced Search dialog box to select projects that are Dormant, Vantagepoint did not return any dormant projects in the search results list, even though dormant projects were available.

Defect 1187263 and 1188747: When you opened the report options for a saved favorite report, any changes that had been previously made to the options reverted back to the Vantagepoint default settings for the report.

Defect 1188743: When you opened an Office Earnings report, the list for the Budget Source option on the Options tab did not include the Project Planning Budget or Project Baseline Budget.

Defect 1189538: An error occurred when you viewed favorite reports with names that included certain non-alphanumeric characters, which were allowed in Vision. This occurred for favorite reports that were initially created in Vision and were converted when you upgraded to Vantagepoint.

 

The following characters continue to be prohibited: \ / : * ? \ " < > | #. Vantagepoint allows all other characters in report names.

Defect 119013: When running Employee reports, you could not search for employees with an Employee Status set to Terminated in the Employees hub.

Defect 1191381: You were unable to add user-defined fields to some data export type reports. The user-defined fields did not display on the Select Columns dialog box that opens from the report's Columns tab.

Defect 1193846: When you ran the Labor Resource Planned and Actuals report, it showed no data.

Defect 1102945: This issue occurred if you use approvals for timesheets. When you created and saved a timesheet and quickly navigated to another application, you were prompted to save the timesheet again. This caused duplicate approval records to be created, and you were unable to approve the timesheet and/or the timesheet line items.

Defect 1108395: If you used an Edge browser to open Vantagepoint and viewed submitted timesheet records in My Stuff » Timesheet, you were unable to scroll down to the last entries.

Defect 1180900: When you opened a submitted timesheet and hid the Approval Timeline, the Approval Timeline reappeared after you edited one of the timesheet fields.

Defect 1185834: When you clicked the record link in an email notification that was sent by the workflow, the link displayed the appropriate hub for the linked record, but did not display the record.

Defect 1193986: When a user-defined field was included in an email alert for a workflow (user-defined workflor or scheduled workflow), and the user-defined field was configured to display a client link (CustUDFClientlink), the email alert that was sent to the recipient displayed the client ID instead of the client name.

Defect 1195828: When you generated a work file for electronic filing for Indiana on the Quarterly Processing form (Payroll » Quarterly Processing in the desktop application), the generated file displayed the ZIP code of the personal address from the employee's hub record. The ZIP code in the generated file should display the ZIP code of the employer's address, as specified in the City/State/Zip field on the General tab of the Quarterly Processing form.

Defect 1180163: The Resource View in Resource Management did not sort the labor category list alphabetically.

Defect 1191304: This issue applies if you converted from Vision to Vantagepoint and during the conversion, planning hours were added to Vantagepoint, but the corresponding tasks were not. When you selected Resource Management » Resource View in Vantagepoint, and you used a search in Resource View, you may have received a "Server Error: the given Key was not present in the dictionary" error. Now you will not receive the error message in this scenario.

Defect 1198689: If all of the following were true for a plan in Vision, you received errors when trying to access the plan in Resource View after it was converted from Vision to Vantagepoint:

• The Vision plan had labor assignments on labor code rows.

• The work breakdown structure (WBS) of the Vision plan did not contain the entire project WBS. For example, the project WBS contained phases 0001, 0003, and 0007, but the plan WBS only contained phases 0003 and 0007.

• The labor code rows with labor assignments in the Vision plan were under the plan's first WBS element for a WBS level, but the project WBS had a preceding WBS element for that level. Using the example above, if phase 0003 in the plan (the first element for the phase level) had assignments for labor codes, and the project had phase 0001 as its first element at the phase level, errors occurred when you tried to access the plan in Resource View.

Defect 1191796: When you selected Advanced Settings on the Projects Advanced Search, saving the advanced search resulted in the Project Level changing to Any Level.

Defect 1193938: On the Revenue form, when you enabled or disabled revenue categories, you received an "Account <xxx.xx> is inactive" message even if the account specified in the message was not selected for any of the revenue settings.

Defect 1165657: After you added a new report column to the Time Analysis tab in Settings » Accounting, sometimes you could not associate a project with the new report column if you navigated away from the form and then returned to it.

Defect 1194013: When you tried to create an SQL expression on the Expression Builder dialog box for a scheduled workflow for the Projects area, the PRSUMMARY fields were not available in the Field list.

Defect 1189117: You encountered the following issues in the mobile application even though your security role's record access was set to Modify Only or Add/Modify on the Roles form in Vantagepoint:

• If you selected a qualified contact and tapped the menu on the Contact screen, you would not be able to tap the Revert to Lead and Disqualify a Contact options.

• If you selected a lead, you would not be able to tap the Qualify button on the Contact screen.

Defect 1177106: If you selected an account with the Asset, Liability, or Net Worth account type for an expense line, a project would be required even though the Maintain separate balance sheets by Organization option was not selected on the Organization General Setup form.

Defect 1177107: If you did not enter or tap any values in a new expense line and then tried to tap the Account or Account Name field, nothing would happen. As a result, you would not be able to add an account.

Defect 1180142: When you sorted by Approval ID in Transaction Center » AP Invoice Approvals, the records did not display in correct numerical order.  

Defect 1191685: When you tried to sort on the Vendor column, the column showed vendor numbers, but sorted by vendor name.

Defect 1195930: This issue occurred in the AP Invoice Approvals application when you created an AP invoice and you associated purchase order line items with the AP invoice. If the purchase order had multiple line items and you selected one line item from it for the AP invoice and then saved the invoice, you were unable to associate the other line items from the same PO with a different AP invoice. The PO and its line items would not display in the Select Purchase Orders dialog box in the AP Invoice Approvals application.

Defect 1200690: When you viewed approved vouchers in Transaction Center » Transaction Entry » AP Vouchers, the Total Tax Amount did not display in the Project Details grid. This happened when you processed AP Invoice Approvals and did not include the associated account number for the transaction entry in Transaction Center » AP Invoice Approval.

Defect 1182891: In Transaction Center » Posting Review, when you wanted to view or print a posting log and selected Other Actions » Show Report Options on the grid actions menu, Vantagepoint continued loading and did not display the report options.

Defect 1191666: When you posted timesheets, unit postings were duplicated if you selected a group to post and then selected another group to post without refreshing the application between the postings.

Defect 1201393: Payroll processing included timesheets that had a status of In Progress and/or timesheets that were not yet posted.

Defect 1201413: This issue occurred if you selected timesheets in the Timesheet grid on the Timesheet tab of the Time and Expense Posting form, changed the period ending date in the Period Ending field and/or selected an employee group in the Employee Group on the tab, and then selected other timesheets in the Timesheet grid. The timesheet posting correctly contained the timesheets that you selected after changing the period ending date and/or employee group, but it also incorrectly included the timesheets that you selected before you changed the entry in the Period Ending field and/or the Employee Group field.

Defect 1191361: When you created a new AP Disbursement file and set the Payment Method option to Credit Card, you were not able to view the attached supporting document using any type of browser. You also received a "Message":"File Not found" error message.

Defect 1182236: When you created and saved an invoice that was associated with a specific project in History Loading » Invoices and Receipt, the invoice number was not available when you searched by the Invoice field on the Cash Receipts form in the Transaction Center.

Defect 1188693: In Transaction Entry » Cash Receipts, if a Retainer cash receipt was entered with a project number and the Maintain Separate Balance Sheets by Organization option was not selected in Settings » Organization in the desktop application, you received the following error: "Project is not permitted with a balance sheet account."

Defect 1191546: When you selected Interest from the drop-down list in the Invoice Section column on the Project Information grid, you received an incorrect "Account is required" message.

Defect 1182913: When you added a user-defined hub in Settings » General » Screen Designer and then associated the user-defined hub with a scheduled workflow, the record name displayed as None when the workflow was was fired using the workflow button.

Defect 1200568: This issue occurs in user-defined hubs that have a user-defined grid, with the Include in Report Total check box selected for the grid column properties. In the hub, when you are at the top of the user-defined grid, the totals at the bottom of the grid show one value. Then, when you scroll down the grid, the totals at the bottom change.

Defect 1195572: When you changed the values for one of the currency fields under Unbilled Revenue and clicked Save, you received an error message: "ImportRecordValidateChanges attempt to process more than one record."

Defect 1190873: When you opened projects, you received the following error: "Your change was saved in Vantagepoint, but not synced with PIM." This occurred when you synchronized employee information to PIM in Utilities » Integrations » PIM and the synced employees had multiple roles for a project.

Defect 1190767: On the Projects' Organization form of the key conversion utility in the browser application, the Account and Account Name fields were incorrectly displayed even when the Maintain separate balance sheets by Organization option was not selected in Settings » Organizations » General in the desktop application.

Defect 1190667: When you set the Application Area field to Project and performed a lookup in the Select Records field, no search results were displayed on the New Project Search dialog box if you used the additional search options to add a search criterion of Inactive or Dormant for Project - Status.