Issues Fixed in Vista Field Service 2022 R5
The following issues were fixed in the Vista Field Service R5 release.
To view customer suggestions and enhancements for this release, see the What's New page.
General
| Issues Fixed | Issue # |
|---|---|
| The portal update to version 22.4 failed for customers who attempted to update from versions prior to 22.2. The following error message was generated: Invalid column name 'DateCreated'. | 107790 and 108001 Note: Resolved in an update after release 22.4+. |
| Windows Authentication failed for users if the Active Directory domain had more than 1,000 user objects. | 107045 |
| Portal setting fields that allow rich text formatting are now limited to 20,000 characters. Previously, in rare cases in which customers had rich text entries beyond this limit, the web portal failed to launch and generated the following error message: Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property. | 107664 |
| Portal settings that have a password or an encrypted key now have a Clear button that you can use to clear an existing value from that setting. | 108002 |
Close a Trip
| Issues Fixed | Issue # |
|---|---|
| When generating a PDF of the trip completion summary, the Create/PDF Email window was not pulling any scopes into the Scopes to include section during trip closeout. | 107992 Note: Resolved in an update after release 22.4+. |
| If the portal setting Do not send email confirmation when completing trips had not been enabled for any SMCos, the Work Order Dashboard would not load. Setting location: . | 107994 Note: Resolved in an update after release 22.4+. |
| When the portal setting Mark the scope complete when the last trip is marked completed was enabled, scopes were not being marked complete automatically at trip closeout. Setting location: . | 107993 Note: Resolved in an update after release 22.4+. |
If a user entered a
reason code for the last trip on a scope, the scope was
automatically closed even if:
|
107996 |
| For trips with multiple signers, trip notes were being duplicated on the PDF of the trip summary. | 107999 |
Work Order Dashboard / Work Orders
| Issues Fixed | Issue # |
|---|---|
| The Work Order Dashboard was not loading any work orders for technicians who were assigned to multiple companies under different SM Technician names. | 107752 Note: Resolved in an update after release 22.4+. |
| Budgeted Labor Hours were not showing the correct value in Work Order Details. | 107657 and 107991 Note: Resolved in an update after release 22.4+. |
| Quantities entered for miscellaneous work completed lines were pushed to Cost and Billable sections of the SM Work Order in Vista instead of just the Billable section. Attempting to mark these work completed lines as Ready to Bill in Vista generated the following error: A total value is required if a quantity or rate is supplied. | 107601 |
| When creating a Purchase Order for a cost type or phase not set up on a job, an error similar to the following displayed and a reserved PO was created in Vista: Cost Type: 1 not set up on Job:1000 - cannot insert PO Item Distribution Lines. The transaction ended in the trigger. The batch has been aborted. If the user attempted to create the PO again after seeing the error, an additional reserved PO was created in Vista. | 107810 |
| Improved overall loading speed for the Work Order Dashboard. | 107810 |
| When creating a new work order, the Lead Technician drop-down was blank if there were no open timecard batches in the portal. | 107990 |
| When a user completed a required form, a duplicate of that form displayed on the Work Order Details page. | 107995 |
| SM Tax Rates with more than two digits after a decimal (for example, 0.065) were not calculating correctly for work completed lines in Vista. | 107998 |
