# Asset View Columns - Adding existing fields

**URL:** <https://farmos.discourse.group/t/asset-view-columns-adding-existing-fields/2024>\
**Category:** Using farmOS\
**Created:** [May 22, 2024, 7:17am UTC](https://farmos.discourse.group/t/asset-view-columns-adding-existing-fields/2024 "2024-05-22T07:17:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![marlonv](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/marlonv/32/1873_2.png) [@marlonv](https://farmos.discourse.group/u/marlonv)\
**Post date:** [May 22, 2024, 7:17am UTC](https://farmos.discourse.group/t/asset-view-columns-adding-existing-fields/2024/1 "2024-05-22T07:17:51Z")

</div>

Morning  
I realised that some of my animals have missing birthdates, and this slipped by us because we never noticed the missing data in asset list view. Now I can’t help but notice the missing columns in asset view, and could not for the love of oats find a way to add/modify the displayed columns. Can anyone give me a pointer?  
I looked through the forums, and couldn’t find much about this, so I think it might just be my setup.

Ie:

 ![image](https://global.discourse-cdn.com/free1/uploads/farm_os/original/2X/9/9bfe327e61cd59d0b0ca343c8a0341fa8054f6d6.png)

There are fields like owner (which we don’t care about here) but birthdate would be useful as a column. Also can’t filter on it. Is this a config thing?

This ties in with my “so much data, but can’t see it” problem. I am not sure if I messed up my FarmOS instance here tbh. 🤔

---

<div class="post-metadata">

**Author:** ![Symbioquine](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/symbioquine/32/284_2.png) [@Symbioquine](https://farmos.discourse.group/u/Symbioquine)\
**Post date:** [May 22, 2024, 3:46pm UTC](https://farmos.discourse.group/t/asset-view-columns-adding-existing-fields/2024/2 "2024-05-22T15:46:07Z")

</div>

Sorry if this doesn’t answer your actual question, but maybe it will help…

Fields that are specific to a particular kind of asset - like birthdate - only appear on the asset view that only shows that kind of asset.

So if you go to `/assets` (e.g. [https://example.farm/assets](https://example.farm/assets)) it will only show the fields that all assets have, but if you go to `/assets/animal` it will show more columns including the birthdate.

**/assets**

 ![image](https://global.discourse-cdn.com/free1/uploads/farm_os/original/2X/2/2902ab27d38b0b206d5fc3c1c61e09a43b7a5ebe.png)

**/assets/animal**

 ![image](https://global.discourse-cdn.com/free1/uploads/farm_os/original/2X/0/097bf3fdc7135009aec3efe6a04d02bf9f91a5f2.png)

The same concept applies in your screenshot. There are two views of the assets under than animal type term. If you change from the “All” tab to the “Animal” tab, yo should see the additional fields that apply only to animal assets.

---

<div class="post-metadata">

**Author:** ![Symbioquine](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/symbioquine/32/284_2.png) [@Symbioquine](https://farmos.discourse.group/u/Symbioquine)\
**Post date:** [May 22, 2024, 3:49pm UTC](https://farmos.discourse.group/t/asset-view-columns-adding-existing-fields/2024/3 "2024-05-22T15:49:44Z")

</div>

> [@Symbioquine](#):
>
> in your screenshot. There are two views of the assets under than animal type term. If you change from the “All” tab to the “Animal” tab, yo should see the additional fields that apply only to animal assets.

@mstenta I think this is definitely an area for improvement. What do you think about hiding the “All” tab in this case - or at least automatically selecting the “Animal” tab?

---

<div class="post-metadata">

**Author:** ![marlonv](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/marlonv/32/1873_2.png) [@marlonv](https://farmos.discourse.group/u/marlonv)\
**Post date:** [May 22, 2024, 4:56pm UTC](https://farmos.discourse.group/t/asset-view-columns-adding-existing-fields/2024/4 "2024-05-22T16:56:38Z")

</div>

Well… shoot.  
I did not notice that or try it before. I use these shortcuts to “display all XYZ” and then filter (and birthdate wasn’t even a filter).  
Thank you very much. I am almost ashamed to only learn about the tabs now.

---

<div class="post-metadata">

**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\
**Post date:** [May 22, 2024, 5:16pm UTC](https://farmos.discourse.group/t/asset-view-columns-adding-existing-fields/2024/5 "2024-05-22T17:16:19Z")

</div>

> [@Symbioquine](#):
>
> @mstenta I think this is definitely an area for improvement. What do you think about hiding the “All” tab in this case - or at least automatically selecting the “Animal” tab?

Yea that makes sense, at least in theory! I wonder if it will be a simple change in the code. 🤔

---

<div class="post-metadata">

**Author:** ![RUros](https://avatars.discourse-cdn.com/v4/letter/r/eb9ed0/32.png) [@RUros](https://farmos.discourse.group/u/RUros)\
**Post date:** [July 9, 2025, 12:43pm UTC](https://farmos.discourse.group/t/asset-view-columns-adding-existing-fields/2024/6 "2025-07-09T12:43:18Z")

</div>

What if I would like to have aditional column in Land assets ? It would be convenient for me if i could see land area [m2, ha, acre] in preview of lands. Or is there another solution i do not see.

---

<div class="post-metadata">

**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\
**Post date:** [July 11, 2025, 8:50pm UTC](https://farmos.discourse.group/t/asset-view-columns-adding-existing-fields/2024/7 "2025-07-11T20:50:11Z")

</div>

Welcome to the forum @RUros. There has been some discussion about what you describe in this topic:

> [@Adding calculated or user inputted area to API and stored data model](https://farmos.discourse.group/t/adding-calculated-or-user-inputted-area-to-api-and-stored-data-model/2052):
>
> This issue came up in the FarmOS Element. Here’s the discussion. Hey all! I won’t be able to make the dev call today. I’ll catch up next week. slight_smile In terms of next steps in core, there’s an open feature request for adding a manual-entry measurement field to allow users to override the auto-computed measurements (in case they are incorrect). [https://www.drupal.org/project/farm/issues/3051971](https://www.drupal.org/project/farm/issues/3051971) It seems like that would be the first step… and then that field could be filled it automa…
