Trying to use Create or Update Record workflow node, but need a Composite Key for uniqueness.
I'm a relative noob, so forgive me if I'm missing something.
I have a custom object, FXRate, which holds conversion rates for each month to be used for forecasting Opportunities, etc. It has fields like so:
Name : eg. AUDUSD
Year : eg. 2026
Month : eg. 02
Rate : eg. 0.664
These fields are not marked as unique, because individually they are not. I can have multiple records with a Year of 2026, for example. However I can only have one record that has the combination of Name : AUDUSD, Year : 2026 and Month : 02.
Basically I want Composite Uniqueness/Keys.
Why? Because I'm trying to use the Create or Update Record node in a workflow to automatically fetch the next months rate to be used and populate the necessary records, however it matches on fields based on whether they are marked as Unique.
Is this possible?
You might say "just use an if/else and separate Create and Update nodes", and that's what I started with, but putting an if/else inside an iterator seems to break my workflows and stops them from completing properly https://github.com/twentyhq/twenty/issues/17611
So, I'm seeking solutions to either issue. Happy for you to point out that this is all my mistake (in fact, I'll be thrilled if that's the case)
Cheers
Malcolm
PS: Oh, I'm on paid/hosted twenty, so I assume that means I'm on the latest version?
I have a custom object, FXRate, which holds conversion rates for each month to be used for forecasting Opportunities, etc. It has fields like so:
Name : eg. AUDUSD
Year : eg. 2026
Month : eg. 02
Rate : eg. 0.664
These fields are not marked as unique, because individually they are not. I can have multiple records with a Year of 2026, for example. However I can only have one record that has the combination of Name : AUDUSD, Year : 2026 and Month : 02.
Basically I want Composite Uniqueness/Keys.
Why? Because I'm trying to use the Create or Update Record node in a workflow to automatically fetch the next months rate to be used and populate the necessary records, however it matches on fields based on whether they are marked as Unique.
Is this possible?
You might say "just use an if/else and separate Create and Update nodes", and that's what I started with, but putting an if/else inside an iterator seems to break my workflows and stops them from completing properly https://github.com/twentyhq/twenty/issues/17611
So, I'm seeking solutions to either issue. Happy for you to point out that this is all my mistake (in fact, I'll be thrilled if that's the case)
Cheers
Malcolm
PS: Oh, I'm on paid/hosted twenty, so I assume that means I'm on the latest version?
GitHub
Bug Description If you have an iterator in a workflow, it will have loop, return and completed branches. If you then add an If/Else node to the loop branch, it will remove the return and completed ...
