---
schema_version: "1"
id: b277ebae48e8b86df27c2692d73e7ccf2d7cccc67ccbddc8d384d13cd70389ed
title: Considerations for Vehicle Inventory Search
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/auto_search_prereqs.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.auto_search_prereqs.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a8a2dcdda0d2fb65da14c9c0156866d5ff02f7371c318fa49042925aa2b4b4a8
description: Keep the following considerations in mind while setting up and using vehicle inventory search in Automotive Cloud.
products:
  - Automotive
release: "264"
---
# Considerations for Vehicle Inventory Search

Keep the following considerations in mind while setting up and using vehicle inventory search in Automotive Cloud.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions.</td></tr></tbody></table>

## Permissions and Access

- Assign the following permission set licenses to users with the System Administrator or Analytics Cloud Integration User user profiles.
    - Automotive Foundation User
    - Criteria-Based Search and Filter
    - Data Pipelines Base User
- Assign the Automotive Foundation User and Criteria-Based Search and Filter permission sets to users who perform vehicle inventory search. Make sure you enable the Use Criteria-Based Search and Filter system permission if you’re cloning the Criteria-Based Search and Filter permission set.
- By default, the System Administrator and the Analytics Integration user profiles have the required object permissions and field-level permissions for all objects used in vehicle inventory search. But you must manually edit the field-level security for the Location object for both these profiles and enable Read access on the fields Location and Parent Location.

## Geolocation Fields Numerical Overflows

There are multiple Location fields that are used in the recipe when you run the Data Processing Engine definition. There is a known issue that causes high-precision numbers to result in a numeric overflow during ingestion and in computations.

To resolve the issue, you must adjust the numeric field’s precision or scale to accommodate the numeric value.

Launch Data Manager and select Connections. Complete the following steps:

- Select **Edit Objects** for the SFDC\_Local connection.
- Search for the **Location** object and select the check box beside it.
- Select **Latitude** and **Longitude** check boxes on the Columns tab.
- Click the pencil icon to edit either Latitude or Longitude.
- Reduce the Scale value from 15 to 14.
- Click **Apply to Selected Measures** and save your changes.
- Search for the **Vehicle** object and select the check box beside it.
- Select **Latitude** and **Longitude** check boxes on the Columns tab.
- Click the pencil icon to edit either Latitude or Longitude.
- Reduce the Scale value from 15 to 14.
- Click **Apply to Selected Measures** and save your changes.
- Search for the **Vehicle Searchable Field** object and select the check box beside it.
- Select **Vehicle Current Location Latitude**, **Vehicle Current Location Longitude**, **Inventory Location Coordinates Latitude**, and **Inventory Location Coordinates Longitude** check boxes on the Columns tab.
- Click the pencil icon beside any of the columns.
- Reduce the Scale value from 15 to 14.
- Click **Apply to Selected Measures** and save your changes.

## Object and Record Deletion

- If you consider a vehicle for inventory search, make sure you don’t delete the following records for that vehicle. The Data Processing Engine definition can’t create records in the Vehicle Searchable Field object if the source records are missing for the following objects.
    - Serialized Product
    - Product Item
    - Product
    - Vehicle Definition
    - Location
- If records are deleted from source objects, the records in the Vehicle Searchable Field object get impacted as follows:
    
      
    | Source Record Deleted | Vehicle Searchable Field Record Deleted? | Vehicle Searchable Field Record Updated? |
    | --- | --- | --- |
    | Location | If a Location record is deleted, the Location ID is set to empty on all Vehicle Searchable Field records, but the related attributes from Location are available for search till the next DPE run. | On the next scheduled run, the Vehicle Searchable Field records with the deleted Location values are removed by the DPE definition. |
    | Serialized Product | If a Serialized Product record is deleted, the Serialized Product ID is set to empty on all Vehicle Searchable Field records, but the related attributes from Serialized Product are available for search till the next DPE run. | On the next scheduled run, the Vehicle Searchable Field records with the deleted Serialized Product values are removed by the DPE definition. |
    | Product Item | If a Product Item record is deleted, the Product Item ID is set to empty on all Vehicle Searchable Field records, but the related attributes from Product Item are available for search till the next DPE run. | On the next scheduled run, the Vehicle Searchable Field records with the deleted Serialized Product Item values are removed by the DPE definition. |
    | Product | If a Product record is deleted, the Product ID is set to empty on all Vehicle Searchable Field records, but the related attributes from Product are available for search till the next DPE run. | On the next scheduled run, the Vehicle Searchable Field records with the deleted Product values are removed by the DPE definition. |
    | Vehicle Definition | If a Vehicle Definition record is deleted, the Vehicle Definition ID is set to empty on all Vehicle Searchable Field records, but the related attributes from Vehicle Definition are available for search till the next DPE run. | On the next scheduled run, the Vehicle Searchable Field records with the deleted Vehicle Definition values are removed by the DPE definition. |
    | Vehicle | If a Vehicle record is deleted, the Vehicle ID is set to empty on all Vehicle Searchable Field records, but the related attributes from Vehicle are available for search till the next DPE run. | On the next scheduled run, the Vehicle Searchable Field records with the deleted Vehicle value are created by the DPE definition, but all fields that are derived from the source Vehicle record are set to empty. |
    | Asset | If an Asset record is deleted, the Vehicle ID is set to empty on all Vehicle Searchable Field records, but the related attributes from Asset are available for search till the next DPE run. | On the next scheduled run, the Vehicle Searchable Field records with the deleted Asset value are created by the DPE definition, but all fields that are derived from the source Asset record are set to empty. |
    | Account | If an Account record is deleted, the Account ID is set to empty on all Vehicle Searchable Field records, but the related attributes from Account are available for search till the next DPE run. | On the next scheduled run, the Vehicle Searchable Field records with the deleted Account value are created by the DPE definition, but all fields that are derived from the source Account record are set to empty. |
    | Business Brand | If a Business Brand record is deleted, the Business Brand Name and Business Brand ID fields on the Vehicle Searchable Field records are set as empty. | The DPE definition retains the empty values set for the Business Brand fields on the Vehicle Searchable Field records. |
    | Geo Country | If a Geo Country record is deleted, the Geo Country Name and Geo Country ID fields on the Vehicle Searchable Field records are set as empty. | The DPE definition retains the empty values set for the Geo Country fields on the Vehicle Searchable Field records. |

## General Considerations

- Vehicle Name is not a text-indexed field and if you use it as a search criteria, make sure you select at least one more field as a criteria to view results. If you only select Vehicle Name as a search criteria field, no results are displayed because at least one text-indexed field is required for a successful search. We recommend you use Vehicle Name as a search result field and use the result field mappings to convert the field into a hyperlink.
- The following types of fields can be configured for vehicle inventory search. Select fields of specific data types for criteria, results, and aggregation.<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
            <colgroup>
              <col style="width:50%">
              <col style="width:50%">
            </colgroup>
            <thead class="slds-text-title_caps ">
              <tr class="">
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d89377e324">Configuration</th>
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d89377e326">Supported Field Types</th>
              </tr>
            </thead>
            <tbody>
              <tr class="">
                <td data-label="Configuration" class="slds-cell-wrap" style="vertical-align:top;" headers="d89377e324 ">Search Criteria</td>
                <td data-label="Supported Field Types" class="slds-cell-wrap" style="vertical-align:top;" headers="d89377e326 ">
                  <ul>
                    <li>Text</li>
                    <li>Lookup Relationship</li>
                    <li>Numeric</li>
                    <li>Picklist</li>
                    <li>Boolean</li>
                  </ul>
                </td>
              </tr>
              <tr class="">
                <td data-label="Configuration" class="slds-cell-wrap" style="vertical-align:top;" headers="d89377e324 ">Search Results Display</td>
                <td data-label="Supported Field Types" class="slds-cell-wrap" style="vertical-align:top;" headers="d89377e326 ">
                  <ul>
                    <li>Text</li>
                    <li>Picklist</li>
                    <li>Boolean</li>
                    <li>Date Time</li>
                  </ul>
                </td>
              </tr>
              <tr class="">
                <td data-label="Configuration" class="slds-cell-wrap" style="vertical-align:top;" headers="d89377e324 ">Search Results Grouping and Aggregation</td>
                <td data-label="Supported Field Types" class="slds-cell-wrap" style="vertical-align:top;" headers="d89377e326 ">Text type fields</td>
              </tr>
            </tbody>
          </table>
- Composite, formula, and encrypted fields are not supported for vehicle inventory search.
- The search works on the find clause of SoSL capabilities. When you select search criteria fields, make sure you select text-indexed fields that can yield only up to 4000 records when used in a combination.

## Search and Filter

- When you create Criteria Field Mappings and Result Field Mappings for a searchable object configuration, the mappings are applied to all configurations that use the same searchable object. So, if you create field mappings for a searchable object configuration for Vehicle Searchable Field, the mappings are applied to all configurations created for Vehicle Searchable Field. If you delete the mappings for one configuration record, the mappings are deleted for all other searchable object configurations using the same object.
- The search results display panel can show up to 2000 records. So, let’s say a search generates 2500 results and 2000 records are displayed. Now you apply the aggregation criteria where the value for one of the grouping fields shows 1500. This means 1500 out of the 2000 records match that value, and not 1500 out of 2500 records. This limit is also applicable for API search.
- You can view up to 10 groups when you apply the grouping and aggregation criteria.
- Filter Field Display Format and Filter Field Parsing on a Searchable Object Configuration are not available for vehicle inventory search.
- For the Relative Location Field, the display text shows a city name. But you can also search by street name, pin code, and other attributes of an address that Google maps can extract information from.

## Image Display in Card-Based View

- For the card-based display format for vehicle inventory search, make sure that the Display URL field on Product records related to specific vehicles are populated. Add the Display URL field to the Product record page layout and enable Files as a related list for the Product record page layout.
- To make images visible to partner and customer users who use Experience Cloud for searching vehicle inventory, make sure you configure sharing settings and make the files available to the users. For more details, see [Make Files on Records Visible to Customers](https://help.salesforce.com/s/articleView?id=experience.networks_files_on_records_visible_to_customers.htm&type=5&language=en_US).

## Product Transfer

- Each Vehicle Searchable Field record that’s displayed as a search result has a related Serialized Product record. When you use the Product Transfer action, the application only creates Product Transfer records for those serialized products that are in Available status.
    
    There can be a situation where you view a specific search result record and select it for transfer, but you can’t proceed with the action because the underlying serialized product for the search result record is already in Sent status.
    
    To avoid this, ensure that the admin runs the Update Vehicle Searchable Field Values Data Processing Engine definition frequently so that the data gets refreshed.
- Each Vehicle Searchable Field record that’s displayed as a search result has a related Serialized Product record. When you use the Product Transfer action, make sure you select a destination location that’s different than the source location of the serialized product related to the search result.
- You can transfer up to 20 serialized products at a time, but if you transfer more than 3 serialized products at a time, you can experience a delay in executing the action.