Defect 1346600: When you specified overrides to the posting account of foreign denominated accounts, the Gains/Losses and Revaluation Posting Log showed that the values were posted to the original system-configured accounts, instead of the specified override accounts. This occurred if previous entries made during the process affected the system-configured unrealized gain account and were from the same company.

Defect 1356897: When you clicked the Test Setup option on the Overhead Allocation form and received an error message you could then, without fixing the error, click the Run option and process overhead allocations successfully. 

Defect 1343703: On the Employee Realization Allocation dialog box, you received an error message when you did the following:

1. You changed the amount in the Employee Specific Unit Realization field, but the amount in the Total Realization field did not update.

2. You then adjusted the amount in the Labor Realization field and clicked Save.

Defect 1242477: This issue occurred when you filtered and then sorted the transactions in the Labor grid on the Labor tab of the Interactive Billing form. When you scrolled through the grid without removing the filter row, the check boxes became misaligned with the rows.

Defect 1295465: On the Invoice History tab in Interactive Billing, when you issued a credit memo, the credit memo showed the date of the original invoice instead of the credit memo date that you entered on the Billing Session Options dialog box.

Defect 1333724: On the Labor tab of the Interactive Billing form, when you changed the status of one or more records, their corresponding values and the total amount in the Invoice Amount field were not updated until you navigated away from the tab.

Defect 1346649: When you had multiple billing sessions open in your browser, you were able to add invoice transactions to an invoice file that was already posted.

Defect 1327952: When you opened an existing bank reconciliation with import records and completed the following steps, the Unchecked filter was incorrectly cleared after you manually cleared an imported transaction:

1. On the Bank Reconciliation form, you selected the Import tab.

2. In the Import Records grid, you clicked the filter and then set the Matched column to Unchecked.

3. You hovered over the end of a transaction line and clicked the Match Transaction icon.

4. On the Match Transactions dialog box, in the All grid, you set the Cleared column to Unchecked.

 

Defect 1360384: This defect applied to cash disbursement transaction entries that you created in Cash Management Bank » Reconciliation. The prefilled values of the Interest Revenue and Bank Fees fields on the Create Bank Transaction Entries dialog box exceeded the field length set in Utilities » Key Formats » Reference Numbers.

Defect 1339321: When you created a new credit card statement and successfully imported a file via Credit Card Reconciliation, the Import Statement dialog box did not display the date and time of the import.

Defect 1340089: When you navigated to Hubs » Activities, if some of the fields in the Attendees grid (for example, the FirstLast and Owner fields) were locked for your security role, you received error messages.

Defect 1334596: When you created a new company but did not add an associated firm name, you could not log in to the new company's record in Vantagepoint and add a firm name.

Defect 1332987: When you created a new firm record and then entered a value in the Number field in the Firm Summary pane, Vantagepoint displayed the number with leading zeros. This issue occurred even if you set the Display Leading Zeros option to No for firm and vendor numbers in Utilities » Key Formats.

Defect 1350987: When you sorted the Projects grid on the Associations tab in the Firms hub, you could not sort the Status field by type (Dormant, Active, or Inactive). 

Defect 1356626: On the Grid Settings dialog box in the Firms hub, the Last Activity Date and Last Activity Subject fields were displayed twice under the Available Columns list.

Defect 1338245: In the Vouchers grid on the Vouchers tab, the values did not display in the drop-down list when you filtered the results in the Pay Terms field. When you entered text in the Pay Terms field, the search was not recognized.

Defect 1346584: This issue applies if you use a CRM-only database. On the Summary pane of the Marketing Campaigns form, the value of the Actual Revenue field excluded the value of the Estimated Fee field for awarded projects (in Hubs » Projects » Project).

Defect 1164266: When you searched for an invoice number on the New Project Search dialog box, search did not return the expected results.

Defect 1348367: When you imported opportunities from the Salesforce application, any opportunities with a status of Lost were created with a status of Active in Vantagepoint.

Defect 1359126: In the Projects hub, when you clicked Other Actions » Add Phase, chose to create a phase from a project or project template, and then clicked Continue, the next screen did not display as it should have and you sometimes received a timeout message. This occurred if your security role did not have full access to all applications and the appropriate record access in Security Settings.

Defect 1363008: In some cases, if your security role gives you only limited record-level access to projects (for example, only access to projects for which you are the project manager), you received the following error when you tried to navigate to an application in the Projects hub: "AppendParameters IEnumerable parameter may not be empty."

Defect 1311627: This issue occurred when you clicked + Add Billing Terms and then created billing terms for a phase-level project. If you selected an existing project without phases as basis for the billing terms, the phase name and number did not display on the Billing Terms form in Edit Mode.

Defect 1337995: On the Rates tab of the Billing Terms form, after you selected and saved a rate table in the Rate Table field in the Expense or Consultants sections, the rate table number incorrectly displayed in that field, instead of the rate table name.

This occurred if both of the following applied in edit mode in the Expense or Consultants sections of the Rates tab before you saved the rate table entries:

• You set the Method option to By vendor, By account, or By category.

• In the Rate Table field drop-down list, you selected a rate table that was located after the 54th rate table in the list.

Defect 1340327: The Fees column on the Contracts tab in Projects » Contact Management was shaded (grayed out) and not editable.

Defect 1357062: When you entered values in the Direct Labor and Direct Expenses fields through the Edit Project Structure form, the total amount was not updated in the Compensation field on the Compensation tab of the Contract Management form.

Defect 1346681: This issue occurred when you created a project in Hubs » Projects » Project and Vantagepoint automatically created a plan and associated it with the project, if you then modified the initial plan, the Save Baseline option displayed as disabled and you were not able to save the changes.

Defect 1200575: If you made one of the Billing Client fields on the Accounting tab of the Projects form (the Contact field, for example) a required field using Screen Designer, you received a "Please review values on the Accounting tab" message when you tried to save a project with the Overhead charge type. This message appeared because the required field contained no entry for that project. However, the message should not have displayed because the Billing Client fields do not apply to overhead projects and are hidden for those projects, to prevent data entry.

Defect 1330054: This issue occurred in List View when you tried to filter a project's value either by the Number column or the Name column. If a project's number or name was displayed as part of a breadcrumb (for example, 0000000.00 > 00BOA), the phase and task levels were not listed.

Defect 1345263: If you selected the Enable Overall Revenue Limit option for a project in the Revenue section of the Accounting tab of the Projects form and then selected Accounting » Revenue Generation and ran the revenue generation process for the project, the limit amounts were not applied.

Defect 1357659: This issue occurred when your role had specific record-level view criteria set up for employees on the Record Access tab in Settings » Security » Roles. On the Overview tab in the Projects hub, when you clicked the hyperlink in the Biller field, you received the following error message: "The multi-part identifier 'EmployeeCustomTabFields.CustDirector' could not be bound."

Defect 1358707: When you viewed projects in List view, you received an error message saying that specific multi-part identifiers could not be bound. This defect happened when you created and saved a search that used starts with, contains, or does not contain operators with an employee or string (for example, client)

data type.

Defect 1344612: If you had data displayed on the Project Review form and you selected a different project, the progress spinner disappeared when the new project's header information displayed, making it look as if the new project data was completely loaded. In actuality, the data for the previous project was still displayed, which was confusing. It took a number of additional seconds before the detail area finally displayed the correct project's data. In this Vantagepoint version, the progress spinner does not disappear until all data for the newly selected project is displayed.

Defect 1345610: When you searched for a project with an EAC Planned Billing amount of zero, but with a high Contract/Fee expense amount, you received the following warning: "Expense EAC Billing is higher than Contract."

Defect 1363682: When you reviewed WBS 2 (phase) and WBS 3 (task) level information on the Project Review form, the ETC Planned Cost column was empty. This occurred even if the ETC Cost values for WBS 2 and WBS 3 were displayed on the Plan form of Hub » Projects Hub » Plan and also in the Planning Analysis at Cost section of the Project Review form in Accounting » Project Review (in the desktop application).

Defect 1351347: In the Calendar application, when you used the French (Canada) language, the month title was incorrectly translated for August and some other months.

Defect 1317154: When you clicked the link in an email notification for absence requests, the Approval Center form was displayed but the approval record was not displayed.

Defect 1322713: Items in the Approval Options drop-down list were still available even if you had approved, rejected, or reassigned the records in the grid.

Defect 1340130: When you configured a dashpart with a grouping and that dashpart included a calculated field, the displayed value for the calculated field was incorrect. This occurred if you selected the following options on the Grouping Options dialog box:

• You set the Group By option to Date Range.

• You set the Start option to Specific Date and then selected today's date.

• You set the Scale option to Week.

Defect 1344718: When you created a table dashpart with the project dashpart base and included columns based on drop-down type user defined fields, you received the following error message: "Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <=, >, >= or when the subquery is used as an expression. The statement has been terminated."

Defect 1345267: When you used the navigation buttons to scroll through more than 100 expense reports and you opened the 101^st record, that record was not displayed correctly.

Defect 1264536: In the Columns grid of the Columns & Groups tab for a report, you could not specify how data aligned in the column by typing an initial character (for example, "C" for Center) in the Alignment field. As a result, if you tried to select the alignment in this way, nothing happened.

Defect 1319198: When you ran the Project Planning List report, the values of the Start Date and End Date fields reflected the project's expected start and end dates.

Defect 1323975: This issue occurred when you set the search criteria to include projects with an active status on the phase level. When you ran the Project Earnings report, no values were displayed under the ETC Billing and ETC Amount columns.

Defect 1338313: Accounts Receivable comments appeared twice in the Billing Client and Project Number sections of the AR Aged Report. This occurred when you did the following:

• In Hubs » Firms » AR Review, you entered comments for accounts receivable entries.

  • On the Columns & Groups tab of the AR Aged Report Options, you sorted the report by Billing Client or by Project Number.

Defect 1339319: When you ran the Labor Detail report, the posted hours from disabled tasks (disabled in Utilities » Key Conversions » Disable Phases/Tasks) were not included in the phase level.

Defect 1341496: When you ran the Project Forecast report, it displayed values in the Project JTD Labor Cost and Project YTD Labor Cost columns even if your role did not have access rights enabled for Labor Cost Rates/Amounts on the Accounting tab in Settings » Security » Roles.

Defect 1342495: When you applied Electronic Payment fields as record search criteria and then tried to run Accounts Payable reports, you received the following error message:

"QueryRoutines.GetExpressionEntityDelegate (vendor). vendor is not handled."

Defect 1346597: When you ran the Purchase Order Cost Distribution Detail report (under the Purchasing category), the report displayed incorrect values in the Project Amount column because it used the value in Total Amount as the multiplier instead of the value in Unit Price. This occurred even when the line item details used unit-based distribution on the Line Items tab of the Purchase Orders form in the desktop application.

Defect 1353502: On the Options tab of the Unbilled Summary report, when you set the Bill Thru Date field to Today's Date before generating the report, the consultant's expenses (AP vouchers) were not included in the report.

Defect 1353538: On the Options tab of the Project Earnings report, the Include Overhead check box was not displayed when you set the Report At option to Cost.

Defect 1354311: This issue occurred when you generated the Tax Analysis report. If you selected a tax code with no tax rate in the Tax Code field on the Options tab of the report options, values were displayed in the Tax Amount column were when there should have been none. For affected transactions, a value was also displayed in the Tax Amount field of the Cash Receipts Posting Log (Transaction Center » Posting Logs), even if the tax code associated with the transaction had no tax rate.

Defect 1354319: This issue occurred when your role had record level view criteria set up for Employees on the Record Access tab in Settings » Security » Roles. When you accessed the Self Service form to view a specific employee record, you received the following error message: "The multi-part identifier "EmployeeCustomTabFields.CustDirector" could not be bound."

Defect 1328417: Timesheets were displayed as overdue under Action Items in the Notification Center even when those timesheets were already completed. In addition, when you clicked the timesheet link in the notification, the timesheet record was not displayed.

Defect 1350914: This issue occurred when you logged in using another language (fr-FR- French(France), fr-CA- French (Canada), es-ES- Spanish (Spain), or de-DE- German (Germany)) and then created a new purchase order or modified an existing in-progress purchase order. When you set the Ship To option to Other, the fields on the Shipping tab, from the Name field through the Email field, were disabled.

Defect 1337576: This issue occurred when you ran an advanced project search to find unpaid invoices for a project. If you used the following search conditions:

• In Row 1 of the Search ResultsSection of Advanced Search, you selected the default Status=Active at the project level for the Add Field.

• In the Add Field for Row 2, you selected Invoices (unpaid) and then set the operator to Contains.   

As a result, the Lookup icon was missing in the Add Value field and the records were not updated in the Search Results grid.

Defect 1353626: When you configured a project lookup on the New Project Search dialog box and used the "=" operator in a search criterion, the "=" operator was sometimes changed to "N". This sometimes occurred when the search criterion was a user-defined drop-down field.

Defect 1350711: After migrating from Vision to Vantagepoint, the Project field was blank for existing secondary credit cards in the Secondary Credit Card grid of the Credit Cards settings form. If you attempted to add a new secondary credit card, you could not save the record.

Defect 1346302: This issue occurred when you tried to assign a workflow to a custom button for the Chart of Accounts application in screen designer. The Workflow drop-down field in the custom button's Field Properties section did not display any workflow options, even if workflows for the Chart of Accounts were available in Settings » Workflow.

Defect 1317245: When you updated the password for an existing user, multiple emails were sent that incorrectly implied that the user's initial login had changed.

Defect 1258344: The report type filter only returned the available reports, instead of both available reports and all reports of that type for the security role. This issue occurred when you tried to filter reports for a security role by selecting the following options:

• In the Search field on the Roles form (Settings » Security » Roles), you selected a role.

• On the Access Rights tab of the Roles form, you set the Functional Area option to Reports.

• Below the Reports for this Role grid, you clicked + Add/Remove to display the Reports dialog box.

Defect 1361350: In some cases, when you used a query in Advanced Search to set up record-level access to projects for a security role, the query took a long time to run and sometimes resulted in a timeout error. Other processes occurring in Vantagepoint at the same time also had degraded performance.

Defect 1350832: On the Users form, when you changed a user's status from Active to Inactive and the user had the Windows Authentication check box selected, the change was not automatically saved as it should have been. It incorrectly required you to enter a password in the Password field on the form even though the Password field was not accessible.

Defect 1353534: When you searched for the values of custom fields (for example, Name or Number) from a user-defined hub on the Conditions dialog box, the search was not recognized. This issue occurred when you did the following:

1. You created a user-defined hub and added a record.

2. In the Employees hub, you added the custom field from the user-defined hub.

3. You created a user-initiated workflow for the Employees hub.

4. In Settings » Workflow » User Initiated Workflow, you launched the Conditions dialog box and then, in the Columns field, entered a custom field (such as Name or Number) from the user-defined hub.

Defect 1348934: When you selected a purchase line item on the Purchase Order lookup, the wrong purchase line item displayed in the Purchase Order field on the AP Invoice Approvals form. This issue happened when you did the following:

1. On the Purchase Order lookup, you sorted the PO line items in descending order and selected an item. The PO line item that you selected displayed in the Purchase Order field.

2. You opened the Purchase Order lookup again. A different PO line item was selected.

3. You clicked OK on the Purchase Order lookup.

Defect 1353489: The Approvals Timeline field on the AP Invoice Approvals form displayed an incorrect submitter. This issue happened when:

• You created an AP Invoice, added an overhead project in the Project Detail grid, and then submitted the record for approval.

• The approver rejected the invoice.

• You resubmitted the record.

Defect 1356792: On the Progress tab of the AP Invoice Approvals form, when you exported data from the Assignments grid to Microsoft Excel, the date fields should have displayed in Excel using the local time from a user’s workstation, instead of the UTC time (Universal Time Coordinated).

Defect 1355254: When you tried to post a timesheet on the Time and Expense Posting form (Transaction Center » Time and Expense Posting), approved timesheets were not displayed. This occurred when the timesheet and the approval record had mismatched statuses.

Defect 1346687: This issue occurred when you selected the Payments option and set the Payments to Autonumber field to Electronic Payments for the selected bank in the Bank Transactions grid in Settings » Accounting » Transactions. When you created an AP disbursement in Transaction Center » Transaction Entry » AP Disbursements, you could not enter a check number for the disbursement in the Payment field.

Defect 1354108: On the AP Vouchers form in Transaction Entry, a voucher was missing the tax amount and tax code when you created the voucher from an approved AP invoice in Transaction Center » AP Invoice Approvals that had a tax amount. If you drilled down on the Tax Amount field on the AP Vouchers form in Transaction Entry, no tax amount or code displayed on the Tax Codes dialog box. When you tried to close the dialog box, you received a “Tax Codes are Required for AP Transactions” message. This occurred if you do not maintain separate balance sheets in Vantagepoint (Settings » Organization » General) and you did not require a project to be entered for AP vouchers.

Defect 1334365: The list of import fields that you can select for the contacts data import appeared to contain duplicates (for example, multiple City fields). This was confusing and made it difficult to tell which fields you should map your data to when importing contacts. This occurred because those fields actually do appear more than once in each record in the Contacts hub, but in different contexts. To resolve this issue, some of the field names in the import fields list have been changed to indicate more specifically the data that you should map to them (for example, Firm City).

Defect 1347453: This issue applies if your firm is configured with more than 13 periods per year. When you tried to open a new period (on the Open New Period dialog box) after period 13, but within the number of periods per year established for your firm, an error message indicated that the new period did not fall within the allowed number of periods per year even when it did. For example, if you tried to open a period between 14 and 20, you received the following error message: "Period number must be between 1 and 20."

Defect 1345207: On the Refresh Billing Extensions utility form, the drop-down lists in the fields below the Range of accounting periods from option did not include all periods.

Defect 1350506: When you tried to replace the values in the Hours/Week fields of the Hours/Week Original column, you received the following error message: "Conversion from string "Wed Jan 01 2020 00:00:00 GMT+080" to type 'Date' is not valid."