# Skip fields when running filter

**URL:** <https://community.mp3tag.de/t/skip-fields-when-running-filter/56715>\
**Category:** Support\
**Created:** [March 17, 2022, 9:35am UTC](https://community.mp3tag.de/t/skip-fields-when-running-filter/56715 "2022-03-17T09:35:15Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\
**Post date:** [March 17, 2022, 1:49pm UTC](https://community.mp3tag.de/t/skip-fields-when-running-filter/56715/11 "2022-03-17T13:49:50Z")

</div>

I think that this would not lead to the same result.  
If, as in the original example the sought after words would be

> [@susoft](#):
>
> 'train' and 'rollin'

and "train" would be part of any field (like TITLE) and also be part of the unsyncedlyrics then with this condition exactly those files that should be found would not appear - as UNSYNCEDLYRICS would not be ignored but would also return a true or false.

---

_[View the full topic](https://community.mp3tag.de/t/skip-fields-when-running-filter/56715)._