---
schema_version: "1"
id: 19d54216610a4533458864e1f918b98384430933f5e85fc1bba1e2b2d08d21e3
title: Refine Record Selection with Enhanced IN Operator Support
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_batch_management_operator.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_batch_management_operator.htm&release=262.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4438592b496e238d6c2c5e292ee5790f94113bc51fa5eb7d7fe6b7e57850314d
description: Process specific records directly from business workflows by passing a collection of record IDs into a batch job. Replace simple text variables with dynamic collection variables by using the IN operator to increase filtering precision and target only the records selected for the business workflow. Pass a list of up to 200 selected records directly into a batch job run to make accurate data updates and reduce the risk of unintended changes.
products:
  - Cross Cloud
release: "262"
---
# Refine Record Selection with Enhanced IN Operator Support

Process specific records directly from business workflows by passing a collection of record IDs into a batch job. Replace simple text variables with dynamic collection variables by using the IN operator to increase filtering precision and target only the records selected for the business workflow. Pass a list of up to 200 selected records directly into a batch job run to make accurate data updates and reduce the risk of unintended changes.

**Where:** This change applies to Lightning Experience in Professional, Enterprise, Unlimited, and Developer editions where Batch Management is available.

**Why:** Eliminate the need for complex, predefined filter logic by limiting the job to selected records. For example, rather than running a job for every asset in Damaged status, an inventory manager can select 5 specific devices and use the IN operator to process only those unique IDs.

**How:** When configuring the batch job, set the condition to use the IN operator, for example, assetId IN assetIds. Map the condition to a flow input variable that uniquely identifies each record being processed.