Asset 360 Suite > Known Issues and Limitations > Product Service Campaigns Limitations and Known Issues
Product Service Campaigns Limitations and Known Issues
The following are the current known issues and limitations:
Technical Attributes Search Criteria Known Issue: When you add technical attributes based search, and the selected technical attribute is of data type Boolean, you must select the operator value as Equals only. For example, Machine Working?– Equals– False. The Unexpected Token error is displayed when you select Not Equals as the operator.
Limitations in bulk load of asset criteria:
The file must be in .csv format. Only the comma-separated and comma-delimited .csv files are supported.
The file must not exceed the size limit of 3 MB.
The .csv file must contain fewer than 3000 rows. If you upload a .csv file containing more than 3000 rows, Product Service Campaigns functionality might display performance issues. Uploading .csv files containing more than 6000 rows is not supported.
The Asset fields of following data types are not supported while matching the asset fields with column headers in the .csv file: Formula, Rich Text Area, Text Area, Long Text Area, and Time. Asset fields of these data types do not display for selection.
The Date and DateTime information is the .csv file must be in the following formats:
Date: YYYY-MM-DD
Date Time: YYYY-MM-DDThh:mm:ss.sssZ
The time in the DateTime data is not considered. Only the date is considered.
The Address fields are not supported in the .csv file. Do not upload .csv files containing address information.
Matching Asset fields to file columns containing null values is not supported.
Page Layout Update Limitation: Page layouts are not updated by default upon Asset 360 version upgrade because of a Salesforce limitation. You must add the SVMXA360__SM_DeliveryMethod__c field to the A360 - Product Service Campaign page layout after upgrading the Asset 360 org from the 10.0 version. For information about updating the page layouts manually, see Updating Page Layouts.
Also, ensure that the post-installation script is run after the upgrade.
Was this helpful?