ee8e223aed
This PR is raised to close the issue #13044 But there are some doubts that needs to be approved. If the fields are not custom then we were saving the changes in **standardOverrides** obj in which only three fields are overridableFields **label, icon & description** can be updated for a field. You can see this in _before-update-one-field.hook.ts_ on line 85 ```ts const overridableFields = ['label', 'icon', 'description']; ``` If the field to be updated are from these three we are putting this in a **standardOverrides** obj and passing it However in our _field-metadata.service.ts_ file. We have **updateOne** function inside it we have wrote a condition if **isCustom** is false then the purpose was to build the updatableFields from the **standardOverrides** obj that we got in **fieldMetadataInput** but there was an error in it. As you can see below ```ts const updatableFieldInput = existingFieldMetadata.isCustom === false ? this.buildUpdatableStandardFieldInput( fieldMetadataInput, existingFieldMetadata, ) : fieldMetadataInput; ``` However, the issue was that we were placing the entire **standardOverrides** object inside **updatableFieldInput** again — instead of merging its individual fields (label, icon, description) directly into the update payload. This PR fixes that by correctly applying the overrides into the top-level object. Please refer to the file changes for the full context. But the thing i don't know. [ ] - Is this the correct expected flow?? [ ]- Will this change break anything elsewhere? I still have doubts on these two. Let me know if I missed something. --------- Co-authored-by: Jagss24 <btwitsjagannat12@gmail.com> Co-authored-by: Charles Bochet <charles@twenty.com>
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
Installation
See:
🚀 Self-hosting
🖥️ Local Setup
Does the world need another CRM?
We built Twenty for three reasons:
CRMs are too expensive, and users are trapped. Companies use locked-in customer data to hike prices. It shouldn't be that way.
A fresh start is required to build a better experience. We can learn from past mistakes and craft a cohesive experience inspired by new UX patterns from tools like Notion, Airtable or Linear.
We believe in Open-source and community. Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.
What You Can Do With Twenty
Please feel free to flag any specific needs you have by creating an issue.
Below are a few features we have implemented to date:
- Personalize layouts with filters, sort, group by, kanban and table views
- Customize your objects and fields
- Create and manage permissions with custom roles
- Automate workflow with triggers and actions
- Emails, calendar events, files, and more
Personalize layouts with filters, sort, group by, kanban and table views
Customize your objects and fields
Create and manage permissions with custom roles
Automate workflow with triggers and actions
Emails, calendar events, files, and more
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Recoil, Emotion and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
- Star the repo
- Subscribe to releases (watch -> custom -> releases)
- Follow us on Twitter or LinkedIn
- Join our Discord
- Improve translations on Crowdin
- Contributions are, of course, most welcome!