FieldFX Base Package Updates

We fixed the Ticket save/status transition error after managed package upgrade.

Resolved an issue where editing or transitioning a Ticket could produce a "Duplicate id in list" error, preventing the save from completing. Users who encountered this after upgrading to Base MP 1.720+ can now edit Ticket fields and transition statuses without error.

We fixed an issue with the Scheduling & Dispatch – Equipment double-booking indicator on the Job Timeline.

Equipment that has conflicting work order schedules is now flagged as double-booked on the Job Timeline. Hovering over a double-booked equipment record displays the conflicting work order name and job, giving dispatchers immediate visibility into scheduling conflicts when dragging and assigning resources.

We fixed an issue when a mobile user was assigned a syncable job, the sync link record was only being created for the Job itself — not for the associated Price Book or Quote. This meant the mobile user would not receive the Price Book and Quote data on-device, preventing them from completing job-related workflows in the field.

The Sync link creation has been updated so that:

This is available in FX5 package version 725 and above.

We fixed an error in Crew Planning when shortening Job Activity date range.

Previously, updating a Job Activity’s End Date to an earlier date could fail with an "Apex heap size too large" error when the assigned crew member had many overlapping Crew Planning records. This has been resolved — shortening a Job Activity’s date range now completes successfully regardless of how many overlapping crew planning records exist for that user.

We fixed an issue so Users and administrators now have accurate visibility into the delivery status of document notifications.

This update ensures that when a file notification is sent, the system correctly marks it as "Sent" and maintains a clear record of all successful recipients. If a notification fails to send, the status will accurately reflect that failure, allowing users to identify and resolve delivery issues (such as invalid email addresses) more quickly.

We have changed Stock issue transactions to now support an Override option allowing the transaction to proceed even when the issued quantity exceeds the on‑hand quantity for a stock item.

This change resolves intermittent failures caused by concurrent transactions affecting the same stock item.

On mobile, users see a warning — “The Quantity Entered exceeds the Quantity on Hand for this Stock Item” — but can still save and continue.

We resolved an issue where users with Salesforce Platform licenses were unable to render reports in Back Office. The report template engine previously attempted to query Profile object fields that Platform license users do not have permission to access, causing an error.

Report rendering now works correctly for all supported Salesforce license types. No action is required by administrators or end users. Available in FX5 versions 709 and later.

We fixed an issue where rollup fields using currency conversions could fail to sync. The data compression step encountered errors due to excessive decimal precision (38 decimal places), causing the SyncDataService to fail. Rollup fields with currency conversions will now compress and sync as expected.

We have updated the static resource files for the ASPE and DataGuide Migration Tool to their latest versions. No action is required by end users — when launching these admin tools without specifying a version, users will automatically receive the most current versions of both ASPE and the DataGuide Migration Tool.

This is a behind-the-scenes update, so end users and admins should see no change in workflow — just updated underlying resources. Want me to adjust the tone or detail level for your release notes format?

We resolved an intermittent server error that occurred when converting HTML reports to PDF from FX5 tickets.

See Use Convert HTML to PDF section for details.

Fixed an issue where completing a job could generate a Return Ticket that duplicated items already included on existing open Return Tickets. The auto‑generated Return Ticket now includes only remaining return quantities.

We added a new Salesforce “Sync Analytics” report based on the FX5__Mobile_Sync_Log__c object so admins can review mobile syncs (time, type, user, duration, sync profile, and errors) sorted by Sync Time.

We fixed an issue where child items on Delivery Tickets created with parent‑child items were not correctly linked to their Job Resources.

The fix now ensures consistent Job Resource tracking across parent and child items.