How to create a new column in kanban, how to do upsert and conditional boolean in workflows
Hey Community,
I’ve noticed some gaps in the documentation (including a few 404 errors) and was hoping to get some clarification on the following:
How to create groups (columns) in the Kanban view
How to perform an upsert to check if an object exists before creating or updating it
How to handle conditional booleans in workflows (should this be done with code?)
Thanks in advance for your help!
23 Replies
Hello @Lucas
How to create groups (columns) in the Kanban viewYou need to create a new option to the enum field metadata ( MULTI_SELECT | SELECT ) one which the kanban view is based
Can i edit the default objects?
How to perform an upsert to check if an object exists before creating or updating itUnless I'm mistaken and unfortunately we don't have a
findOne resolver for the moment
So you will to get the whole object metadata items and search in them
What's your need here exactly ?
How to handle conditional booleans in workflows (should this be done with code?)You can enable the workflows filters in the LAB ( latest twenty version ) Without them you would have to create your own filtering serverless nodes
on selfhosted or managed?
I’ve noticed some gaps in the documentation (including a few 404 errors) and was hoping to get some clarification on the following:Please feel free to share outdated docs or playground examples Both
It's to create leads/contacts eg... without having duplicates
The API won't let you create colliding object/fields within the same workspace
It's guarded on name and identifiers
It might be a redundant check to be done on your side, to double check.
So I'm forced to use code if I want to create an object and fallback on update?
Are you talking about records or object metadata and field metadata definitions ?
Records are on upsert
Object and fields models aren't
So if I create a record in an object it's equivalent to upsert? or update op
I'm sorry I'm not sure to understand the question
These are company's records rows
upsert = insert fallback on update
This the company data model definition
I'm not understanding your need
If you try updating a record that does not exist it gets created ( upsert )
Not the case for metadata model -> no upsert
If i create a contact and don't want to have 10 contacts of the same person if I ingest many sources
It's then unrelated to metadata definition but to record collision
sorry i don't have all the vocabulary of Twenty CRM
No worries all good
Just making things clear for both of us 👍
thanks so I can focus on update
You're welcome
Will soon be introduce custom uniqueness constraint on field
There's already some on standard fields such as emails and so on
Wow I just checked, there is new stuff in Lab
exactly the stuff I was looking for thanks
Cool ! feel free to reach out for feedback or some help regarding these features in any new help thread