# New agent forest - define models enum values
**URL:** https://community.forestadmin.com/t/new-agent-forest-define-models-enum-values/7761
**Category:** Help me!
**Tags:** howtos
**Created:** [January 17, 2025, 1:44pm UTC](https://community.forestadmin.com/t/new-agent-forest-define-models-enum-values/7761 "2025-01-17T13:44:55Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Adel\_de\_Clevermate](https://community.forestadmin.com/u/Adel_de_Clevermate)
#### Post date: [January 17, 2025, 1:44pm UTC](https://community.forestadmin.com/t/new-agent-forest-define-models-enum-values/7761/1 "2025-01-17T13:44:55Z")
## Feature(s) impacted
in order to change a gender for EXAMPLE i want to show a dropdown list instead of text input.
I would like to do this on code not on the UI.
## Context
migration from forest v9 to the new nodejs agent.
in the old forest version I was editing in the models files but in the new forest agent I dont find a way to do the same.
- Project name: Clevermate v2
- Agent technology: (nodejs,
- Agent (forest package) name & version: …
- Database type: postges
---
### Author:  [@anon7311026](https://community.forestadmin.com/u/anon7311026)
#### Post date: [January 17, 2025, 1:47pm UTC](https://community.forestadmin.com/t/new-agent-forest-define-models-enum-values/7761/2 "2025-01-17T13:47:24Z")
Hello @Adel_de_Clevermate,
The agent should pick up what is defined in your ORM models or database and use that in the schema.
Do you have an enum in either of those ?
Thanks 🙏
---
### Author:  [@Adel\_de\_Clevermate](https://community.forestadmin.com/u/Adel_de_Clevermate)
#### Post date: [January 17, 2025, 2:05pm UTC](https://community.forestadmin.com/t/new-agent-forest-define-models-enum-values/7761/3 "2025-01-17T14:05:18Z")
Hi @anon7311026
No, I dont have. the field on databse is of type varchar, I dont get where I can see the ORM models.
---
### Author:  [@anon7311026](https://community.forestadmin.com/u/anon7311026)
#### Post date: [January 17, 2025, 2:27pm UTC](https://community.forestadmin.com/t/new-agent-forest-define-models-enum-values/7761/4 "2025-01-17T14:27:17Z")
Ok,
What you can do is use an `addField` customization on the collection. Something like that should work for you:
```javascript
UserCollection.addField('UserGenderWithEnum', {
columnType: 'Enum',
enumValues: ['M', 'F', 'O'],
dependencies: ['UserGender'],
getValues(records) {
return records.map(record => {
switch (record.UserGender) {
case 'M':
case 'Male':
return 'M';
case 'F':
case 'Female':
return 'F';
case 'O':
case 'Other':
return 'O';
default:
return null;
}
});
},
})
.removeField('UserGender')
.replaceFieldWriting('UserGenderWithEnum', async value => {
return { UserGender: value };
});
```
> **[Add fields | Node.js Developer Guide](https://docs.forestadmin.com/developer-guide-agents-nodejs/agent-customization/fields/computed)**
> **[Override writing behavior | Node.js Developer Guide](https://docs.forestadmin.com/developer-guide-agents-nodejs/agent-customization/fields/write#changing-other-fields-in-the-same-record)**
Please note that you may have to enable writing for the field in the UI, as computed fields are readonly by default.
It will effectively replace the `UserGender` field with `UserGenderWithEnum` in your forest schema
Please let me know if this is ok for your use case 🙏
---
### Author:  [@Adel\_de\_Clevermate](https://community.forestadmin.com/u/Adel_de_Clevermate)
#### Post date: [January 17, 2025, 2:57pm UTC](https://community.forestadmin.com/t/new-agent-forest-define-models-enum-values/7761/5 "2025-01-17T14:57:16Z")
Thank you @anon7311026
This looks good to resolve the issue. ✅
Unless there is other simpler way with less code lines, since we have many more fields like this and on many collections.
Thank you 🙏
---
### Author:  [@anon7311026](https://community.forestadmin.com/u/anon7311026)
#### Post date: [January 20, 2025, 8:18am UTC](https://community.forestadmin.com/t/new-agent-forest-define-models-enum-values/7761/6 "2025-01-20T08:18:19Z")
You may want to look into factorizing your enum declarations using plugins.
Here is very similar example in our plugins repo:
>
>
You can take inspiration from there to limit boilerplate in your customization code.
I hope this helps