00183563

067154

Issue: An error occurred in the Search Results stage of a Field Change Order when the user executed a Field Change Order using the Execute Change Order SFM. This prevented the user from viewing FCO result lines. Also, an error occurred when the user accessed the Field Change Orders list view page, which failed to load records. This issue occurred due to system limits when processing a large volume of Field Change Order result lines.

Resolution: The FCO now supports large volumes of FCO result lines, up to 22000 records, allowing users to view results in the Search Results for the FCO.

The Field Change Orders list view page now includes pagination, which allows users to view a large number of records without errors.

For more information, see Viewing Field Change Orders.

Field Change Order

25.10000.65,

25.20000.27

00184156

065074

The governor limit error occurred when the system processed large volumes of Technical Attribute Templates.

Installed Base Management

25.20000.27

00183708

067137

The AI action modal closed before the action completed when users triggered the same AI action multiple times in quick succession. This issue occurred when the AI action launched an SFM transaction to update the current record. For example, users launched the AI action a second time to run an SFM transaction that created a Case and Work Order from an Installed Product record. This happened because the system refreshed the record during the action, which interrupted and closed the modal.

Online: SFM Custom Actions

25.10000.65,

25.20000.27

00185294

067685

The Team Technician Management console did not list technicians alphabetically and did not highlight the selected technician’s team at the top when the user launched the Manage Technicians SFM. The system did not sort technician records and did not prioritize the selected technician’s team in the console.

SFM Custom Actions

25.20000.27

00182977

067369

The custom LWC component did not appear in the Name dropdown, which prevented the user from selecting it during Custom Action creation for a Work Order object. This issue occurred due to a Salesforce platform limitation on querying exposed custom LWC components, which resulted in some components not listed in the dropdown.

SFM Custom Actions

25.10000.65,

25.20000.27

00184124

067472

An error occurred when the user launched the Generate Invoice SFM to create a proforma record for a Case record in the Turkish locale.

Services Proforma Invoice Process

25.20000.27

0000184941,

00183875

067272

Japanese text displayed incorrectly after the user entered text using a Japanese input method in certain fields. The application did not convert the input correctly, which caused mixed or incorrect characters to appear and affected data entry accuracy.

SFM Delivery

25.20000.27

00184075

067402

The validation error remained on the screen after the user corrected the start and end date and time values in the work order. The application did not clear the error after the values became valid, which caused confusion and blocked further updates.

SFM Delivery

25.10000.65,

25.20000.27

00183486

067433

The State field retained the previous value instead of clearing it after the user changed the related account to one without a State value and saved the record. The application did not update the field to blank, which caused incorrect data to remain on the record and affected data accuracy. Empty values were not saved, so existing values were not cleared.

SFM Delivery

24.20000.69,

25.10000.65,

25.20000.27

00184218

067526

The work order start and end times decreased by one hour after the user entered the time and saved the record during a daylight saving time change. The application did not retain the entered time, which caused incorrect scheduling information to display and affected planning accuracy. This issue occurred due to daylight saving time adjustments for the selected timezone.

SFM Delivery

25.20000.27

00185494

067699

An unexpected error occurred when the user migrated the SFM Transactions with formula to the target org. The deployment logs showed success but the formula processing replaced all single quotes, including those required for picklist values.

Core Plugin

NA