Known Issues/ Limitations
This topic explains the known issues and limitations of FSA.
• Attachments:
◦ Attachments not downloaded during initial sync
▪ In FSA for Windows, the attachments are not downloaded automatically after the initial data sync. We recommended you perform manual data sync to download all the attachments from the server. You can also choose to download the attachment using the download on-demand option with the cloud icon across the respective record.
◦ Attachments with special characters are not downloaded
▪ In FSA for iPad, attachments with names containing special characters (;) are not downloaded to the client app.
• Smart Sync:
◦ Smart sync not supported for Linked SFM process
▪ Any changes made to the linked SFM processes are not reflected during smart sync and will be synchronized only during the next data sync.
• Smart Docs:
◦ Special Characters Support
▪ Special characters such as O (omega) is not displayed in the generated PDF Output document. As a work around, include the font family (Arial Unicode MS) in a special container tag as shown below within the template designer:<span style="color: rgb(51, 51, 51); font-family: Arial Unicode MS; line-height: 18px;">Ω</span>
▪ In FSA for iPad, the attachment name has a special character
• Checklist Output Docs
◦ The Output Docs include the sections that are skipped based on the defined rule in the Exit criteria. These sections are specified as undefined.
• Salesforce Files versioning
◦ If you enable version control while creating your output document process, only the latest version of the output document exists in the Attached Documents sections of your record. This versioning is user-specific and you can only view the latest version of your output document in the mobile application.
• Restriction with Boolean values in the Output Document template
• If the Output Document template has a custom JavaScript function to check an expression with Boolean data type values, it is recommended to convert Boolean values (true or false) to string values ("true" or "false") in the template.
• Output Document Generation Failure
◦ The Output Document generation fails if the attachment size exceeds the 30MB limit. It is recommended to use the Take Photo option as it compresses the image file reducing the attachment size.
• Checklists:
◦ Checklist Entry Criteria
▪ When Entry criteria are defined on a checklist section with Field = multi-select picklist field and Operator = Include/Exclude and Values = value1; value2 (multiple values) is set in the Form Designer, then the Entry criteria does not work as expected.
• Checklist Number Field Limitation
◦ The number field in Checklist has the following limitations:
▪ Any number up to 16 whole digits is retained as is
▪ Any number up to 18 whole digits is rounded to the closest 16 digit number
▪ Numbers with up to two decimal places is supported
▪ The exponential converted number is not supported
 |
Note:If the entered number is beyond the mentioned length limits, the number displayed on saving is not the same as the entered value.
|
• Checklist Attachments Appear Distorted on Output Document
◦ Images added as attachments might appear distorted or displayed as multiple pages on the Output Documents, based on the size of the image.
• Attachments Might Appear Blank on Checklist
◦ If Completed checklists are viewed immediately after the Initial Sync, then the Image/Downloading status/Cloud icon will not be shown until Attachment Sync completes in the background. The files/download status will be visible when the Attachment Sync completes. Revisit the checklist to view the attachments.
• Maps:
◦ Get Direction on Map View and Work Order Summary View is not Plotting Technician Route. Clicking the Get Direction button opens Google Maps in a browser. If the Current Location of the technician is available, then those values are considered as the starting point for plotting the route. However, if the current location of the technician is not available, then the browser may not detect the correct current location, and will not be able to plot the route. This is a known issue.
• Datetime Fields Type:
◦ The Datetime field does not support hard-coded values and only supports Literals (today, tomorrow, yesterday, and now) and field mapping.
• IB Tree:
◦ In the mobile app, up to 5000 records can be displayed on the Installed Base Tree without impacting performance.
• Drag and drop:
◦ Drag and drop of any unsynced records are not supported while data sync is in progress. You need to wait until sync is completed to be able to drag and drop records in the Installed base tree.
• Search:
◦ Special characters such as &, #, \, ', %, _, + are not supported when a keyword search is performed on the search results screen.
◦ You cannot perform a keyword search using a date field on the Search Results screen.
• Technical Attributes:
◦ Special characters such as '<' and '>' are not supported in the technical attribute name field. If a technical attribute name contains these special characters, a portion of the name between '<' and '>' will be cropped.
• Picklist:
◦ Any changes made to a picklist or the picklist values will be in effect only from its next new instance. That is, if a picklist is already associated as an attribute value in a Technical Attribute Template, then any changes made to the picklist or its value will not be reflected. The changes will be applicable only on a newly installed product where technical attributes are recorded for the first time or in the next new instance of the Technical Attribute Template.
◦ When picklist is added to the Technical Attributes Template of an Installed product through an attribute request payload using the REST endpoint URI, then you will not be able to edit that picklist and its value unless the picklist values are also added as a part of the attribute payload.
• Initial sync:
◦ Initial sync fails with the "Synchronization Failed" error message when the mobile app user's profile does not have permissions for ProductIQ Profile, Page Layout, and Custom Coverage objects. The mobile apps user's profile must have a minimum of reading permission for these objects.
• Locale:
◦ Number formatting is currently supported only for the US locale.
• Setup Field Values Not Refreshed on the Web Page:
◦ If you are using Microsoft Internet Explorer 11, whenever you make changes in the Installed Base App Setup, the values might not be refreshed on the web page when you save the setup values. To resolve this issue:
1. In Internet Explorer, go to Settings > Internet Options > General. In the Browsing History section, click Settings. The Website Data Settings pop-up window is displayed.
2. In the Temporary Internet Files tab of this window, select Every time I visit the web page as the option for Check for the newer version of stored pages field.
3. Save the setting by clicking OK and Apply.
Alternatively, use any other browser.
• Features Not Supported:
◦ The following features are not supported in Field Service App:
▪ FaceTime, Phone, and Email options in Chatter.
▪ ServiceMax Pulse App integration for Push Notifications is not supported.