|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00183563
|
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.
|
March 2026 Patch,
April 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00184985,
00183629
|
The list views for the Service Request object disappeared after the user deleted the custom Service Request object tab and upgraded the org from version 25.1 to 25.20001. During the upgrade, the packaged Service Request object tab blocked the upgrade because the org already had a custom Service Request object tab.
|
Core 26R2
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00184156
|
The governor limit error occurred when the system processed large volumes of Technical Attribute Templates.
|
April 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00184212
|
An error occurred and the delete action failed when the user attempted to delete a Work Plan Assignment using the Remove option. The error message remained on the page and cleared only after a browser refresh.
|
March 2026 Patch
|
|
00184208
|
The Work Plan Template page closed abruptly due to a validation error when the user saved a modified Service Task. This prevented the user from correcting the validation error on the same page and caused loss of unsaved changes.
|
March 2026 Patch
|
|
00184210
|
The Work Order page remained in a continuous loading state after the user attempted to delete a Service Task using the Remove option. The system blocked the action due to missing delete permission, but the spinner did not stop after the error.
|
March 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00180840
|
Unrelated warranties were assigned to multiple installed products after warranty data was interfaced from SAP. The system tagged a single warranty to multiple installed products instead of assigning the correct warranty to each product, which resulted in incorrect warranty associations.
|
March 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00179989
|
The error log was attached to successfully processed PM Plans when other qualified PM Plans failed during PM engine execution.
|
December 2025 Patch,
February 2026 Patch
|
|
00180023
|
Product documentation for PM Schedule behavior when using Adjusted Sequence and Adjusted Start Date in PM Plans is now updated with accurate information and examples. This update resolves user confusion during PM Plan creation. For more information, see Adjusting PM Schedule Sequence to Align With Existing Maintenance Cycles.
|
January 2026 Patch
|
|
00185765
|
An error occurred when a user tried to edit a Preventive Maintenance Template that had a large number of associated Task Templates.
|
May 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00179033,
00179402
|
An error occurred when the user clicked an Expression in the Wizard properties. This issue occurred when the user configured the Date field with the Is Null or Is Not Null operator in the expression.
|
December 2025 Patch
|
|
00179680
|
The Scheduled SFM did not process all the qualified records when the advanced expression was configured for the Scheduled SFM.
|
December 2025 Patch
|
|
00178318
|
The Finalise SFM failed to load for work orders with a large number of work detail lines, which prevented users from completing and finalizing installation work orders. The failure occurred after users selected Finalise SFM on work orders with high line counts, where the screen became unresponsive due to limits in handling large record volumes, unsupported on-load script execution, and repeated data retrieval attempts triggered by the detail record batch setting.
|
January 2026 Patch
|
|
00181842
|
Service Flow Wizards displayed excessive empty space above the wizard area after the upgrade to ServiceMax 25.2. Users encountered the issue while viewing records with Service Flow Wizards in the web browser, which disrupted the layout and reduced usability across multiple objects.
|
January 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00178283
|
The Event Start Date and Time, and End Date and Time changed by one hour when the user modified the Work Detail Lines through an SFM.
|
December 2025 Patch
|
|
00179184
|
The Dispatch Response field did not update to a blank value when the user clicked Reopen Background SFM from a Work Order.
|
December 2025 Patch
|
|
00182488
|
The code snippet was removed from the Events in the Child Section of a page layout after the user cloned the source SFM and its associated page layout. This caused the source SFM to lose the code snippet configurations.
|
February 2026 Patch
|
|
00184463
|
The governance limit error occurred when the user configured an Installed Product lookup filter for a Case Line item.
This issue occurred as the user defined multiple expressions with an AND condition on the same object, which exceeded system limits.
|
March 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00176516
|
A redirection error occurred, and the user could not return to the Work Order record after the user opened an SFM from the Work Order.
|
December 2025 Patch
|
|
00178220
|
The dependent picklist failed to populate any values when invoked from an SFM even though it was correctly configured with a controlling field. Salesforce interpreted uppercase and lowercase representations of true differently, treating one as a boolean and the other as a string, which led to inconsistent dependent picklist behavior.
|
December 2025 Patch
|
|
00183371
|
After upgrading to version 25.2, users with Chinese (Simplified), Japanese, or Korean locale settings were unable to select morning hours in the SFM Time input field. The available time options started at 12:00 instead of 00:00, which prevented accurate time entry. The issue affected date-time and time fields in both header and detail lines across 12-hour and 24-hour formats.
|
February 2026 Patch
|
|
00181827
|
A white screen appeared and the SFM stopped responding after users selected multiple lines and applied a bulk update on the Required Parts tab in the Create Parts Request SFM from a work order. Users could not proceed with updating the selected records and had to exit the page, which interrupted their work and prevented completion of the parts request.
|
February 2026 Patch
|
|
00181571
|
Text color did not apply to selected content in the Response Description rich text field after users selected text and applied a color in the Manage Action Request SFM. Users had to repeat the action to see the color change, which caused confusion and slowed content entry.
|
February 2026 Patch
|
|
00182391
|
Field values appeared with inconsistent formatting after a user opened the Debrief and Follow Up screen in the browser. Some read-only fields appeared darker and more prominent than others, while the same fields appeared consistent on the mobile app, which caused confusion. The browser UI did not align with the standard SFM Delivery design, which caused inconsistent visual behavior across platforms.
|
March 2026 Patch
|
|
00183798
|
Duplicate lines were added after a user updated a text field in a detail line and then pressed Enter. The system created an extra line instead of updating the existing one, which resulted in incorrect records and required manual cleanup.
|
March 2026 Patch
|
|
00184941,
00183875
|
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.
|
April 2026 Patch
|
|
00184075
|
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.
|
April 2026 Patch
|
|
00183486
|
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.
|
April 2026 Patch
|
|
00184218
|
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.
|
April 2026 Patch,
May 2026 Patch
|
|
00186342,
00185768
|
The code snippet entered a continuous loop and displayed an error after the upgrade to version 25.2. This issue occurred when a user added a Start Date and Time value in a field on the SFM transaction and exited the field. This issue prevented the script from completing and blocked the action from finishing successfully.
|
May 2026 Patch
|
|
00187120,
00186791
|
The DATEVALUE function in an SFM formula returned incorrect results for date and time comparisons after the upgrade to version 25.2. The function did not use the organization's configured timezone for date calculations, which caused incorrect comparisons and fields displayed inaccurate data.
|
May 2026 Patch
|
|
00187270,
00186957,
00186647
|
The text cursor jumped to the end of the Work Description field on the Debrief SFM transaction after a user placed the cursor at a specific position and entered text. Only the first character appeared at the intended position, then the cursor moved to the end of the text and all subsequent characters appeared there, which made inline editing difficult.
|
May 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00183708
|
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.
|
April 2026 Patch
|
|
00185294
|
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.
|
April 2026 Patch
|
|
00182977
|
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.
|
April 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00180887
|
The Screen Flow page did not scroll for large forms and remained stuck, which prevented the user from accessing all fields. This occurred after users configured a Screen Flow as a Custom Action on a Work Order and launched the flow from the wizard, where the scroll bar did not appear for large form layouts.
|
January 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00184517
|
An exception error occurred when the user clicked Resume Travel SFM in a Work Order.
This issue occurred as the system could not resolve literal values used in expressions.
|
March 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
||
|---|---|---|---|---|
|
00178177,
00181039
|
The Timesheet engine created a Timesheet header only for the current week and did not create one for the future week. This issue occurred after the user configured a weekly Timesheet.
|
January 2026 Patch,
February 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00179632
|
An error occurred when the user scheduled a work order on 9 March 2025 or 2 November 2025. This occurred only when the work order's start or end date fell exactly on these daylight-saving transition dates.
|
December 2025 Patch
|
|
00181397
|
The Dispatch Console did not highlight weekends, and the time marker disappeared. This occurred after the user edited the Start or End date to view more than one week of data in the Scheduler.
|
January 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00186696
|
An error occurred when the user executed Field Change Order for a large number of records via Execute Change Order SFM.
|
Core 26R2
|
|
00181031
|
The Product Line picklist field did not display during change order creation, which prevented users from selecting the required field. The issue occurred after users navigated to the Field Change Order flow and searched Installed Product fields, where only the Product Line multi-select field was available and the picklist field was missing.
|
January 2026 Patch,
February 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00182177
|
An error occurred and Checklist result generation failed when the user generated Checklist results via scheduled SFM using an Apex class due to Salesforce governance limits.
|
January 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00177594
|
The Get Price function failed to calculate prices for parts in environments with Salesforce Connect enabled. Users encountered the issue after creating a work order linked to an external object and attempting to add parts, which resulted in missing line item pricing. This prevented accurate price calculation for parts associated with work orders that referenced external data.
|
January 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00182443
|
Formatting issues appeared in the generated output document due to non-breaking spaces. The issue occurred after the user saved a document template with spaces in the tags in the new editor.
|
March 2026 Patch
|
|
00183167
|
Formatting issues appeared in the generated document output due to non-breaking spaces. The issue occurred after the user saved the document template with spaces in the tags and then saved the script in the new editor. This added non-breaking spaces and removed meta tags.
|
March 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00184124
|
An error occurred when the user launched the Generate Invoice SFM to create a proforma record for a Case record in the Turkish locale.
|
April 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00182803,
00180558,
00177554
|
Formatting inconsistencies occurred in the final delivered XML document when the user migrated DataGuide Document Templates that were configured in a non-English language and contained images.
|
February 2026 Patch
|
|
00182010,
00183609,
00181929
|
The migration failed when the user attempted to migrate the DataGuide Form. This occurred as the form contained an empty page, and the migration process attempted to read elements on that page. Since no elements existed, the migration failed.
|
February 2026 Patch
|
|
00182604
|
The migration failed when the user attempted to migrate an item. This occurred when the user did not have an assigned ServiceMax AI extension package license. This prevented the tool from accessing the package components and caused the validation to fail.
|
February 2026 Patch
|
|
00183100,
00183288
|
The migration tool failed to process the Wizard Access record when the user migrated SFM Wizards to a sandbox environment. This issue occurred as the configuration profile assigned to the Wizard already existed in the target org.
|
February 2026 Patch
|
|
00183375
|
The Checklist export included questions from a previous session instead of exporting only the questions from the selected Checklist.
|
March 2026 Patch
|
|
00184201,
00185081
|
The Migration Tool encountered an error while processing a field-mapping record when the lookup field in the source org contained a value with a single quote.
|
March 2026 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00185494
|
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.
|
April 2026 Patch
|
|
00184981
|
The SF Plugin failed to deploy the Parts Usage Settings to the target org as the new fields were not included in the SF Plugin.
|
May 2026 Patch
|