Replies: 6 comments 5 replies
|
Yes that would be super cool 😍 |
|
Sorry I missed this topic when adding the feature request. I searched for a few terms, but somehow 'computed' was not one of them 😅. |
|
+1 here. It's the only thing stops me from using this CRM. You can see the open-source EspoCRM formulas (it's on php 🙄 and sometimes broken...), it allows to link different entities, e.g Opportunities + Accounts, so I can calculate all the related opportunity.amount to some Account and show the result in some field. And also the missing thing here is to create different (custom) entities, where I can later also use some formulas. E.g. in data-models, after I create a new Objact(page) I expect it to have many-to-many or many-to-one, etc.. relationships to create some custom fields with links to different Objects @Bonapara
|
|
@eshut Thanks for sharing! there are multiple ways to do computed fields. For "cached" computed fields that are re-computed when the source value changes (it seems that's what Espo does), we will release a major feature "Workflows" in early beta end of October which should allow hacking that kind of things. It will force you to call the API in a workflow step at first but as we iterate we will make it easier to build things like that without technical knowledge |
|
@FelixMalfait Wow, that sounds great. I would be happy to test this out and share my feedback on it. |
|
Is a workflow still the right way to accomplish this? Testing out twenty and I'm creating a setup for an annual school program. I have a many to one relation between annual programs (many) and schools (one), and want to show the most recent program in the school view. |
|
@timdmackey yes unfortunately we aren't there yet. It's still 100% something we want to get done but it will take time. |
|
+1 — running into this for a school admin use case (tracking which academic year(s) a person is linked to, via a custom object related to Person). Without a computed Name field, every record shows as "Untitled" until someone manually types a label — an extra step and a source of inconsistent titles across staff. Tried the Workflows route, but the "record created" trigger explicitly warns against manually-created records (fires before the user finishes the form), and the Code step for updates seems undocumented right now. Really impressed with Twenty otherwise — this is the one thing standing between us and adopting it. |
|
You can work around this for time being with Code node |
Uh oh!
There was an error while loading. Please reload this page.
Scope & Context
Currently, on objects we can only add txt/number/boolean and date field.
It woould be great to add a computed field that use the value of other fields to calculate it's own value.
For instance a field calculating the estimated opportunity value following the number of employees on the company.
Or, using the same use case as illustrated in #2534, a field that count the numbe of opportunities or closed deal by referer.
A notion like approach could be inspiring :
All reactions