New Mexico 2018 Tax Update

The following are the changes for New Mexico effective January 1, 2018:

• The tax brackets have been updated.

• The amount per allowance increases from $4,050 to $4,150.

• Employees are allowed to claim more than 3 allowances on their W-4, but the New Mexico state tax withholding calculation can apply to only 3 of the allowances.

 

Improvements were made so that Audit Trail reports would generate more quickly.

In earlier DPS versions, the overall data entry process using the Labor planning grid of the Projects hub was slower than it should be because there was a lag of a couple of seconds after each entry in a calendar period column before you could make your next entry. One factor contributing to that lag in response was that DPS was updating all related values in the grid each time that you made an entry and tabbed out of a grid cell. Some of those grid cells, such as those containing planned cost and billing amounts, ETC cost and billing amounts, and so on, required that data be sent to the server, the new value calculated there, and the updated value sent back for display.

 

To improve data entry performance, this behind-the-scenes process has been modified in version 1.1.12. Instead of updating those calculated values immediately when you make an entry in a calendar period column, DPS simply displays those values with a strikethrough to indicate that they are no longer current. As a result, you can more quickly enter hours for multiple calendar periods.

 

All grid cells with out-of-date values are automatically recalculated, and the strikethrough removed, when you do any of the following:

 

• Move to a different row in the grid.

• Switch from viewing hours to viewing amounts.

• Go to a different tab.

• Display charts for a work breakdown structure row.

• Change plan settings.

• Change the scale setting.

• Save the baseline plan.

• Revert unpublished plan changes.

• Check in the plan.

• Publish the plan.

When DPS updates all values after you have entered changes to some calendar periods and moved out of the row, you may see minor changes in the hours for other calendar periods that you did not edit. This occurs when the scale at which you make your changes is smaller than the scale at which the hours were previously saved (for example, if they were previously saved in monthly periods, and you change the hours for a weekly period). That, in turn, can change the number of hours to be spread and/or the number of periods over which they are spread, resulting in small differences for individual calendar periods.

Depending on your data and the report options that you select, the number of report rows for a Resource Management report can exceed the maximum rows that the report can display. If that happened in prior versions of DPS, you received this message: "The number of records requested is too large. Please continue to narrow what's included in your report." However, it was often not clear, from that message, what steps to take to resolve the issue and generate the report successfully.

 

Version 1.1.12 includes several changes to address this situation:

• The maximum allowed number of report rows has increased from 2000 to 3000.

• The message that displays provides clearer suggestions for what to do to reduce the number of report rows.

• The gear icon in the upper-right portion of the form is now available when you receive the message so you can display the Report Settings dialog box. There, you can, for example, exclude assignment-level rows, if you do not need that detail, or remove Forecast Range from the list of selected columns, which also reduces the number of report rows. (You can also use a new link in the message to open the Report Settings dialog box.)  

• The default report options and columns for users who have not previously made their own selections have been changed. The default reports now contain fewer report rows than in previous DPS versions.

Support for International English for a Single Language Database

The mobile application of the Deltek CRM/Time & Expense for Professional Services now supports International English for a single-language database. The Language drop-down list on the login screen contains the English (United States) and English (International) options. Selecting English (International), however, still displays most labels in English (United States) on the Touch interface, except for certain words (for example, Authorise and Organisation).

Defect 941089: This issue applies if you use multiple currencies and you configured Intercompany Billing to reclass intercompany suspense as receivable/payable only. When you ran the Intercompany Billing process for expense files, you incorrectly received the following error: "At least one project has no billing terms and the project's Billing currency is different from the Labor Rate or Override Table currency in Reporting Default Terms. To determine the projects that need updated billing terms, run the Missing Billing Terms report with the following option checked: Include only Projects that have no labor terms and cannot use Reporting Default Terms."

Defect 951881: In Interactive Billing, you received the following error message when you accepted an invoice with a 12-digit invoice number format (such as x x x x x x x x x x x x ): "Value was either too large or too small for an Int32."

Defect 937567: In AP Invoice Approvals, when you final approved an AP invoice and an AP voucher was automatically created for it, duplicate line items were created for the voucher. You could see the duplicate records on the Voucher Review tab in Cash Management » Create Voucher from PO. This occurred if the purchase order’s costs were applied to multiple projects on the Default Distribution tab in the Purchase Order application, or the Cost Distribution tab on the Line Detail dialog box, if you use distribution overrides.

Defect 942267: When you migrated from Vision to DPS, any user-defined tab in the Employees info center in Vision was created twice in the Employees hub in DPS. One tab had the correct tab name, but it did not contain the fields and grids that it had in Vision. The other tab had "None" as its tab name and contained the fields and grids from the user-defined tab in Vision.

Defect 941698: When you used a mouse wheel to scroll up and down a screen in DPS and the screen was in Edit mode (for example in the Contacts hub, you had clicked Edit on the actions bar), if you scrolled over a date field, the mouse cursor locked in the date field and then started scrolling through dates.

Defect 951823: While in the List view in the Contacts hub, contact records only loaded as far as names starting with the letter B. Nothing after B loaded.

Defect 950195: You may have been unable to upload an employee photo in the Employees hub.

Defect 945062: On the Professional tab in the Employees hub, when you tried to edit resume text in the Resume grid, you received an error informing you that the text length was greater than the 255 characters allowed, and it reduced the text to fit within the 255 characters limit. You should have been able to enter more than 255 characters of text.

Defect 961251: When you switched to List View in the Employees hub, you received an invalid column name error when you clicked the filter icon on the grid toolbar and then selected a labor category for filtering the list.

Defect 954415: After upgrading from Vision to DPS, the files that were uploaded for vendors using Transaction Document Management/FILESTREAM were not accessible in DPS.

Defect 954293: When using the List View in the Projects hub, if you opened the Select Columns dialog box but did not make any changes, when you navigated away from the Projects hub and then returned to the Select Columns dialog box, the Available Columns list was empty.

Defect 944926: In the Projects hub in the desktop application for a multicompany DPS implementation, you could not select an employee for a key role (for example, as the principal or project manager) if that employee's home company was not the same as the project's company. (This problem did not occur in the Projects hub in the browser application.)

Defect 949438: Intermittently, when you were working in the Projects hub, DPS would freeze up.

Defect 942039: When you were creating a new project by copying an existing project, fields that were normally locked for your security role using Screen Designer appeared to allow you to enter data for the new project. However, your entries were not actually saved when you saved the new project. With this release, those locked fields now correctly display as locked, and you cannot make entries in them. If a locked field needs to be updated for the new project, a user with the proper security access must do that.

Defect 953213: If you created a new project based on both an opportunity and a project template, and the project template had a work breakdown structure with more than one level, and the opportunity contained a user-defined grid that contained data but the corresponding grid in the template was empty, that user-defined grid in the new project was incorrectly populated based on the template and thus was empty. The grid contents should have come from the opportunity's grid instead.

Defect 941311: In rare cases, the role for an employee on the Team tab of the Projects hub was incorrectly set to undefined. As a result, you received the following error message when you attempted to add a phase to the project's work breakdown structure: "Code undefined does not exist. The value for field Role will not be set."

Defect 945625: When the project work breakdown structure (WBS) is displayed, the WBS elements (for example, phases or tasks) at each level should be displayed in alphanumeric sequence by element number/ID. However, when you were in Plan mode and viewing the planning grids, they were instead displayed in the order in which they were added to the WBS.

Defect 954278: If you added a record from the Credit Card Charges pane to your expense report and copied the row containing that record, the primary card value was incorrectly populated with the secondary card value in the Credit Card field in the newly copied row and any subsequent rows. You received an error when attempting to post the expense report.

Defect 944883:  When updating Expense Report grid records, the Total Expenses and Company Paid amounts beneath the grid did not update unless you exited and reopened the report.

Defect 954284: If you created an expense report, added a record from the Credit Card Charges pane, and then added another row and manually selected a credit card in the Credit Card field, you received an error when saving the expense report.

Defect 941852:  When you opened an expense report that was previously submitted, reopened, or rejected, and then you updated one or more lines on the record and submitted it again, the approval workflow did not restart for the updated lines.

Defect 962106: If an expense report included a very large number of credit card charges, you could not update, delete, or submit the expense report. Instead, you received a system error: "Error during serialization or deserialization using the JSON JavaScriptSerializer...."

Defect 952878: When you opened a timesheet, selected Other Actions > Floor Check, selected a timesheet, and then selected Other Actions > Open Selected in Timesheet on the Floor Check dialog box, the timesheet sometimes could not be found and did not open.

Defect 944004: When you opened a timesheet that was previously submitted, reopened, or rejected, and then you updated one or more lines on the record and submitted it again, the approval workflow did not restart for the updated lines.

Defect 951208: When you opened a timesheet and selected the Unit Table lookup, a blank line displayed instead of <default> at the top of the drop-down list.

Defect 945618: When an employee processed the payroll payment for another company in the enterprise, an error message displayed and the employee was not able to email remittances for the company that was not his own. 

 

Defect 953131: There was slow performance when entering hours in calendar cells in the Labor grid in Project Planning.

Defect 937378: On the Activity List Report, Project Planning Tasks were displayed when they should not have been displayed.

Defect 941601: In the DPS desktop version, a blank report was printed when running the Labor Resource Forecast report. This issue occurred if you selected the Include Budgeted Employees option on the Options tab of the Labor Resource Forecast Options dialog box, used "is me" as the operator for the Employee Number search field on the Employee lookup, and then clicked the Apply button.

Defect 954283: When you created a favorite report based on the Timesheet Audit Detail report, you received the following error message when you ran the report: "System.IndexOutOfRangeException: There is no row at position 0."

Defect 942346: DPS incorrectly assigned the default cost and billing rate methods specified on the Rates form (Settings > Resource Planning > Rates) to opportunity plans, with the result that planned cost and billing amounts appeared on Resource Planning reports for those opportunities. Opportunity plans should not have planned amounts, only planned hours.

Defect 954149: If you selected the option in the Column Settings & Selections dialog box to sort resources by name, scrolling the contents of the Resource View grid was slow.

Defect 954498: In the List View of User Security, if you removed the Disabled selection for all logins except your own, when you saved the form and re-opened it, different accounts then had the Disabled option selected.

Defect 948398: When you upgraded from Vision to DPS, any user-defined fields, grids, and tabs for the Chart of Accounts were not brought into DPS.

Defect 948126: When you used the Import utility in the browser application (Utilities > Imports & Exports > Imports) to import opportunities from a .CSV file, you could not import values into the Responsibility field. That field was not listed under Deltek Field on the Import Opportunities from CSV dialog box, so you could not map the responsibility field in your import file to the DPS Responsibility field.

Defect 953134: In some cases, when you tried to import units using the Data Import utility in the desktop application (Utilities > Utilities > Data Import), you received this error: "Violation of PRIMAY KEY constraint 'UNTablePK'. Cannot insert duplicate key in object 'dboUNTable'."

Defect 941106: On the Opportunities hub form, when you used a user-defined button that triggers a scheduled workflow, and the scheduled workflow is configured to create a project based on the displayed opportunity, the Responsibility field's value in the summary pane of the Opportunity hub form was not applied to the Responsibility field in the summary pane of the Project hub form for the created project record.