Has anybody encountered this issue: when downloading the xml definition of a saved search, there are other fields added in the dependencies? I have confirmed that the fields in the dependencies are not used in the search as filters or columns. Example below

<savedsearch scriptid="customsearch_arr_db_cac">
  <dependencies>
    <dependency>[scriptid=custbody18]</dependency>
    <dependency>[scriptid=custbody19]</dependency>
    <dependency>[scriptid=custbody_cust_priority]</dependency>
    <dependency>[scriptid=custbody_nsts_gaw_superapp_approved]</dependency>
    <dependency>[scriptid=custbody_promisedate]</dependency>
  </dependencies>
  <definition>....</definition>
</savedsearch>`

This prevents deployment since SDF will return the following error:

An error occurred during custom object validation. (customsearch_arr_db_cac)
Details: The [scriptid=custbody18] object referenced by the dependencies field is missing.
Details: The [scriptid=custbody19] object referenced by the dependencies field is missing.
Details: The [scriptid=custbody_cust_priority] object referenced by the dependencies field is missing.
Details: The [scriptid=custbody_nsts_gaw_superapp_approved] object referenced by the dependencies field is missing.
Details: The [scriptid=custbody_promisedate] object referenced by the dependencies field is missing.

Did not want to edit the file since it had this comment

<!-- This XML must be system-generated. Do not edit it manually. !-->

There maybe some fields added in

Drill Down Fields