Okey @taparshi1.  Looking around in the documentation and in the UI this use case does not seem to be supported. Please add it to https://ideas.splunk.com.   However in you situation I would solve it slightly different. You can manage information fields of the entities to achieve the same result.  Service Template: my_database_service_template For example create a service using a service template where you defined a set of entity filters. At the time you run the service import job you will set these filters to match a value from your CSV.  Simple Example:  Service name: my_oracle_db  Service Template: my_oracle_db_service_template  Entity filter: my_entity_type:oracle_db, my_qualifier_info_field:true  With the above setup you can instead manipulate the info field "my_qualifier_info_field" of the entities to activate / deactivate entities from your service. The qualifier for true/false can in turn be managed in a lookup, that in turn are used doing scheduled updates / imports of entities. This decouples the service from fixed list of entity host names and makes it adaptable to entities available that passes the entity filter.    /Seb  ... View more