# Feature request - column names in filter

**URL:** https://community.mp3tag.de/t/feature-request-column-names-in-filter/15193
**Category:** General Discussion
**Created:** [November 11, 2013, 11:07pm UTC](https://community.mp3tag.de/t/feature-request-column-names-in-filter/15193 "2013-11-11T23:07:01Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![chrisjj](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/a698b9/32.png) [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [November 11, 2013, 11:07pm UTC](https://community.mp3tag.de/t/feature-request-column-names-in-filter/15193/1 "2013-11-11T23:07:01Z")

</div>

Please could the Filter's field ID accept column names e.g. Path, and the names of my user-defined columns? Thanks.

---

<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: [November 12, 2013, 6:33am UTC](https://community.mp3tag.de/t/feature-request-column-names-in-filter/15193/2 "2013-11-12T06:33:27Z")

</div>

I think that \_path is already in the list of filter criteria.

You are free to name your columns whatever you like. So if you rename them so that they are just like fields you want to filter, there you are.

As the columns may be named whtatever you like certain keywords have to be blocked to avoid ambiguities. I wonder whether other users want to be bossed around like that.

---

<div class="post-metadata">

### Author: ![chrisjj](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/a698b9/32.png) [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [November 12, 2013, 11:56am UTC](https://community.mp3tag.de/t/feature-request-column-names-in-filter/15193/3 "2013-11-12T11:56:17Z")

</div>

> [@ohrenkino](#):
>
> I think that \_path is already in the list of filter criteria.

%\_path% is.

> [@ohrenkino](#):
>
> You are free to name your columns whatever you like. So if you rename them so that they are just like fields you want to filter, there you are.

🙂

> [@ohrenkino](#):
>
> As the columns may be named whtatever you like certain keywords have to be blocked to avoid ambiguities.

Indeed. That would not be a problem if the column names showed in a drop-down list... like the one removed from the app after V2.44.
