> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.syncspider.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to Apply Filters to Collection Fields

In this Article, we will be going over the ways you can filter out the [collection fields](https://syncspider-support.freshdesk.com/en/support/solutions/articles/3000115807-create-a-custom-collection-field-with-syncspider), along with some tips.

But first, let us define what Filtering is and how it can help you achieve the desired results.

Filter application is the 3rd step in [task](http://help.syncspider.com/en/articles/3638789-what-is-a-task) [creation](https://syncspider-support.freshdesk.com/en/support/solutions/articles/3000115449-how-to-create-a-task-), regardless of the Integrations used.

The important thing to note is that it is **completely optional** and that you can **apply as many filters as you wish.**

**Additionally, when a Filter is applied, only the Data affected by it will get sent over during the task execution. A common misconception is that the filtered values will get left out.**

The criteria for Filtering will vary based on:

• Source Integration  
• The Entity (Data Type)

You can find a step by step guide on how to integrate any of our native Integrations on the following [hyperlink](https://syncspider-support.freshdesk.com/en/support/solutions/folders/3000021047).

With the Filters defined, we can proceed with filtering out the **Collection Fields**:

First of all, we need to understand the term "**Item**" which represents a sort of **entity.**

**E.G.** If there's an entity called "car", then **one item would be one car**.

Items can have various fields in themselves such as Name, ID, etc.

Items can also have the so-called Collection field.

**Collection fields contain multiple values in them, and they are always of the same type** (e.g. number or text, etc.)

To better illustrate this, let's imagine two items arriving at SyncSpider, and both of them having collection fields:

**1st Item's collection field:**

Item1.collection = [  
"apple",  
"red apple",  
"green apple",  
"orange"  
]

**2nd Item's collection field:**

Item2.collection = [  
"orange",  
"orange",  
"orange"  
]

**Now, if we wished to export the items that have the value "orange" at least once, we would apply the "only one item needs to pass filter"** **option, and set the value to "orange".**

![](https://storage.crisp.chat/users/helpdesk/website/-/1/2/3/0/12307a5a5c12ce00/4a2a6d38-d0ce-4ba9-8677-720aed_1g09sql.png)

In that case, both Item 1 and Item 2 would get exported.

However, if we go with the **"all items need to pass filter"** **option** and set the **value to "orange",** then **only Item 2 would get exported.**

![](https://storage.crisp.chat/users/helpdesk/website/-/6/3/f/a/63faa10ecc98f000/dd880613-d021-4af7-b408-c68bef_ucuttv.png)

We hope that this example helped you understand how Collection filtering works and gave you some ideas that you can apply to your own tasks that migrate Items with collection fields. :)

---

To check the list of the tools and features we support please click [here](https://syncspider.com/integrations/)!

If you don't see your favorite tool on our list, please take the time and send us the request [here](https://roadmap.syncspider.com/boards/integrations?sort=cached_votes_up) to create an integration for you or UP-vote if it's already on the list :)

We develop integrations based on the requests and up-votes :)

We hope that this covers everything. If you have any further questions or need additional clarification please reach out to us via [[email protected]](/cdn-cgi/l/email-protection#780b0d0808170a0c380b01161b0b08111c1d0a561b1715) or our chat widget!