FieldFX Base Package Updates

We added user permissions for the new ServiceMax DataGuide Migration tool available in the FieldFX Admin Portal for the FX25R1 release.

We fixed an issue for customers where Deep Copy is now accessible to Salesforce Flow or recurring events.

For more information, see FXL Deep Copy.

We added the ability to enforce Hierarchy Price Book Compliance and added a note that the Price Book Item must be from the Job’s Price Book hierarchical family.

We fixed an issue where the FX5__Allow_New_Ticket__c field on the Status object is defaulted to unchecked.

We fixed an issue where when performing a Deep Copy for a Price Book into a process, cleared the frequent lock row error that occur during the deep copy process.

Now, copying from 2 different price books with price book items linked to the same catalog items doesn’t trigger a lock row error.

We fixed an issue for EAM Meter-Based PM Group Schedules:

We fixed an issue in the Convert HTML to PDF functionality that if no HTML reports are found, the dialog box says [Object object] and not the error message.

We fixed an issue where the clear error message is not displayed when there is a mismatch in field types with the same name on the ticket/quote items.

We fixed an issue where existing Sync Events were duplicated causing errors.

We fixed an issue where only the new status was shown in the Status History report where both the old and new status should appear.

Now, ticket status changes recorded on the ticket status history tab and in the status history report show both the old and new status.

We fixed an issue in EAM where the Search screens appear in Salesforce Classic not the Salesforce Lightning Experience screens.

We have reconfigured the Search screen to appear as a Lightning page.

See FFX-2136

We fixed an issue in the Base package where the OverrideBatcher is triggering when the Override Configs aren’t active.

We fixed an issue in the Quote to Job Lightning component where the settings weren’t sent to the controller even when the Send Platform Notification checkbox was selected resulting in no notifications when a job from a quote was created.

Now when setting the Send Platform Notification checkbox, notifications are created and appear in the notifications panel when a job from a quote is created.

We fixed an issue where a user had sync events not processing and a Record Not Found error was returned.

We fixed an issue where the most recent FX5 Base Managed Update modified all Equipment records' Last Modified dates with "FieldFX Base Package" install date.

This patch fixes the issue so the Equipment last modified is not touched by the package install date.

We have corrected an issue where an e-mail notification is sent out notifying the customer to schedule a Sync Stage Meta Data Apex job.

We fixed an issue where a customer was running test classes in their sandbox environment encountering the following error:

Error: System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION You do not have permission to insert Job (Sync Errors): []

We fixed an issue where the Form and Question columns weren’t populated in the table of Form Responses.

We fixed an issue to fix the time it takes for a Deep Copy to validate.

We have enhanced PM Group Schedules to now include Meters. Before PM Group Schedules were based on calendar-base PM Schedules. With this addition, you can generate multiple PM group details and work orders that are meter-based. You won’t have to generate multiple PM Schedules each with its own work order.

For more information, see EAM PM Group Schedules Introduction.

We have enhanced the meter replacement process to enable the meter replacement while also retaining the accumulated meter readings to display these readings on the new meter.

For more information, see Add a Meter section in FX EAM Meters topic.

We added validation for meter replacement in EAM that corrects the date a user can use for the Install Date and Revision fields.

This change prevents:

For more information, see Add a Meter section in FX EAM Meters topic.

We fixed an issue where Work Task Steps randomly don’t get created from a Preventive Maintenance that is link to a Model Work Order with Work Tasks and Work Task Steps. Now they do.

We fixed an issue when updating a date for a meter reading, the Last Reading Date on the meter wasn’t being updated.

This version fixes the issue so updating a meter’s reading to a past date, it’s reflected in the Last Reading Date. Also, when entering new meter readings, the field is correctly updated. This applies to both continuous and counter meters.

We have added a new managed Custom MetaType called FX5__Notification_Config__mdt and the IsActive and IsDeleted fields. This is needed for the new Email Notification Console Admin tool coming in a future release.

We fixed an issue if the user clicks on the Create Job button on the Quote to Job screen, the button appears on the blank screen.

We have made an enhancement to Sync Fail Notifications for Job, Tickets, and Ticket Items.

Now, if something fails in the ticket or job, there is an indications (on a ticket item, notification appears on the ticket and then on the job containing the ticket) and the ticket or job has related sync issues.

See New note in Sync Upload Errors topic > Sync Upload Errors vs. Sync Failures section.