FieldFX Base Package Updates
Introduction
This section contains the release notes for FieldFX Managed Package. For previous years, see the dedicated pages for those years in Older Releases.
For more information on Push Upgrades, see Push Upgrade process and when versions were pushed to Sandbox and Production Salesforce Instances, select the year section.
Release Table
Consult this table for the latest and previous release numbers. Click the version link to jump to that version and click the "Back to Release table" link to return to this table.
| Version | Released | Notes / Issues | ||
|---|---|---|---|---|
Latest Release |
2/6/26 |
The only change is to revert the change made for FFX-4789. |
||
12/19/25 |
This version addresses security issues. There are no customer facing issues. |
|||
12/15/25 |
This version was pushed to the 25R2 Release to custom Sandbox environments.
|
|||
10/28/25 |
This version has added the existing FieldFX connected app to the package. No other changes were made. |
|||
10/27/25 |
|
|||
8/26/25 |
||||
7/16/25 |
This release fixes and prevents sync errors that aren’t customer-facing. Pushed with the 25R1 Sandbox and Production Push Upgrades. |
|||
7/14/25 |
This release resolved deployment issues that aren’t customer-facing. Pushed with the 25R1 Sandbox and Production Push Upgrades. |
|||
6/24/25 |
Pushed with the 25R1 Sandbox and Production Push Upgrades.
|
|||
5/14/25 |
This version updates internal code libraries that are not customer facing. |
|||
5/2/25 |
|
|||
3/24/25 |
|
|||
1/7/25 |
|
Release Notes
Version 1.685.1 (2/6/26)
The only change is to revert the change made for FFX-4789.
Version 1.684 (12/19/25)
This version addresses security issues. There are no customer facing issues.
Version 1.682 (12/15/25)
| This version was pushed to the 25R2 Release to custom Sandbox environments. |
| Functional Area |
Type | Issue | Summary | ||
|---|---|---|---|---|---|
Enhancement |
FFX-3042 |
We added the where the customization of the Deep Copy email that is sent when a deep copy of a job is complete. A custom email template can be used and can be linked to the deep copy process. |
|||
Enhancement |
FFX-4185 |
We added the function of editing a UOM field in a Job Resource only if the status is "NOT SHIPPED".
For more information concerning Price Book Items, see Add a Job Resource > Change UOM on a Job Resource or Edit a Job Resource > Change UOM on a Job Resource. |
|||
Enhancement |
FFX-3041 |
We added where the customization of the Quote-to-Job email that is sent when a job is created from a quote. A custom email template can be used and can be linked to the quote to job process. |
|||
Enhancement |
FFX-5004 |
We updated the admin dashboard to add a button for access to the Sync Profile Manager admin tool. |
|||
We added the feature where if the sync profile is set up to sync jobs/price books only for crew members, an option was added to sync jobs/price books only as long as the crew planning record is active. A system administrator can enable or disable this setting. For example, if the job is scheduled for the whole month of October, but the Mobile user has a crew planning record valid from 10/1 to 10/8, sync the job/price book for this user only for the period 10/1 to 10/8. Past 10/8, the job/price book should not sync for this user anymore as he does not have an active crew planning record anymore. |
Version 1.676 (10/28/25)
This version has added the existing FieldFX connected app to the package. No other changes were made.
Version 1.675 (10/27/25)
| Functional Area |
Type | Issue | Summary |
|---|---|---|---|
Enhancement |
FFX-4569 |
When creating a new log, the stop time of the previous log is copied into the start time of the new log, regardless of record type. The copy is in the context of the job. There is no impact on the ticket. The source (template) log might be linked to a ticket. Also a new log on ticket B might pull values from log on ticket A. RecordType or Ticket would not be used as a context to find the last log with stopTime value. For JobLog clone, there is no carrying over values. |
|
Bug Fix |
FFX-4638 |
The UOM field ( Users can pick only unit of measure records in the UOM field on the PBI that are linked to the |
|
Enhancement |
FFX-3271 |
A user can create a SFDC report against what shows for each movement of the job resource by date. Users can see when items were delivered and returned for each job, grouped by part number (catalog item). |
Version 1.663 (8/26/25)
| Functional Area |
Type | Issue | Summary |
|---|---|---|---|
Bug Fix |
FFX-4716 |
We fixed an issue with Email where emails are automatically sent to |
|
Bug Fix |
FFX-4605 |
We fixed an issue where sequence numbers in the invoice item grid don’t work. |
|
Bug Fix |
FFX-4432 |
We fixed an issue on the edit sync profile page where the Back button is disabled and the Save button doesn’t load the changes. |
Version 1.642 (6/24/25)
| Functional Area |
Type | Issue | Summary |
|---|---|---|---|
Bug Fix |
FFX-4307 |
We fixed an issue where the Price Book search criterial didn’t filter the list properly. |
|
Enhancement |
FFX-3276 |
We added the feature for a user to add bundled items from a price book or quote to a job resource. When adding the bundled items, preserve the item’s parent-child relationship at the job resource level. When shipping the bundled items, maintain the relationship and only allow shipping of the parent and ship all bundled items together. |
Version 1.616 (5/2/25)
| Functional Area |
Type | Issue | Summary |
|---|---|---|---|
Enhancement |
FFX-3985 |
We’ve added a new field called FX5_ffx_Last_used__c on the catalog item object. The purpose is to reduce the total number of price book items that are synced. The field is stamped with the date when the catalog item was last used on a ticket item. Even though using this field is optional, admins with price book items that have not been in use for a long period of time, can remove these from the sync. For example, an admin can configure the Sync Admin Profile to only sync price book items where the associated catalog item has been used on a ticket item in the past 2 years. For more information, see |
Version 1.604 (3/24/25)
| Functional Area |
Type | Issue | Summary |
|---|---|---|---|
Bug Fix |
FFX-3524 |
We fixed an issue and added a validation rule to check a Price Book Item or a Ticket Item. These both have lookup values, but aren’t required on both of them. This new validation rule checks each one to verify which one has a lookup field. |
|
Enhancement |
FFX-3431 |
We have made an enhancement to Shift Scheduling where if a contact or equipment is copied, the planned start and end dates from jobs are copied to the new records. |
|
Bug Fix |
FFX-3569 |
We fixed an issue in the Sync Wizard Admin Tool that when the Sync Staged Data option is executed by the user who presses the button. It will be a specific user just for the purpose of Setting the Sync Staged Data. For more information, see Run Staged Sync Data As. |
Version 1.591.2 (1/7/25)
| This patch was automatically pushed to Sandbox orgs and will be pushed to Production orgs as part of the FieldFX 24R3 Push Upgrade. The patch fixes non-facing customer issues. |
Older Releases
To see a particular version from an older release, find the version number in the table below and then click on the year link for that page.
| Year | Version Numbers |
|---|---|
1.159.2, 1.591, 1.588, 1.579, 1.575, 1.569.2, 1.569.1, 1.569 |
|
1.545, 1.529, 1.516, 1.515, 1.507, 1.501, 1.492 |
|
1.483, 1.482, 1.476, 1.473, 1.470, 1.469, 1.468, 1.463, 1.454, 1.448, 1.447, 1.437, 1.429.1, 1.429, 1.428 |
|
1.425, 1.414, 1.405, 1.402, 1.399, 1.398.4, 1.398, 1.396, 1.395, 1.392 |
|
1.378, 1.371, 1.361, 1.354, 1.346, 1.339, 1.331, 1.324, 1.309, 1.295 |
|
1.275, 1.265, 1.258, 1.248, 1.243 |
|
1.214, 1.211, 1.192, 1.187, 1.181, 1.179, 1.178, 1.176, 1.174 |