Fix #17711 ### Reproduce steps 1. import this xlsx file [test-import.xlsx](https://github.com/user-attachments/files/25156642/test-import.xlsx) 2. import company worksheet at first and then import people worksheet 3. you will see an error <img width="324" height="101" alt="Snipaste_2026-02-07_19-22-04" src="https://github.com/user-attachments/assets/bf2703da-a57a-4795-805b-6ddcc689c621" /> And I found neither the frontend nor the backend applies lowercase normalization to the query value. Although the standard UI input always displays company links in lowercase, user might mixed the case in their xlsx/csv bulk import. So I did a simple check in frontend. ### Additional findings: 1. Email has the same case sensitivity issue when opportunities import. You can test same as in test-import.xlsx file (I created a opportunities worksheet. It will have same issue: <img width="330" height="101" alt="email error" src="https://github.com/user-attachments/assets/db36b19b-2abe-4c61-a661-f8d1eb357a5e" /> 2. API also has: I also tested via the GraphQL API Playground and confirmed that createOnePerson with a mixed-case URL fails to find an existing company. <img width="1419" height="513" alt="Snipaste_2026-02-07_23-33-56" src="https://github.com/user-attachments/assets/c189f1fd-9793-42d5-a1a9-616cffd2592e" /> ### Approach: 1. Only change it in frontend, and I will add email check later; (my current commit) 2. Or backend: Normalize values in computeUniqueConstraintCondition in twenty-server/src/engine/twenty-orm/utils/compute-relation-connect-query-configs.util.ts (which handles connect.where queries, and this will cover xlsx import and api import: createone, createmany, updatemany, updateone. And much better for future extension. (Personally, I'd prefer the backend approach. But I'd love to hear your thoughts on which approach you'd prefer, and whether my analysis is on the right track. --------- Co-authored-by: Etienne <45695613+etiennejouan@users.noreply.github.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!




