Hi there !
I have been using flows recently and I noticed a strange behavior about the “unique” field attribute.
In my opinion, the role of such an attribute is to prevent the field value to be duplicate among the entries. Then it should return an error when trying to create an entry using a field value that is already existing so the client can handle the fact that the value is already existing (not sure if I am understandable).
The current behavior seems to move the value from the old entry to the new one but without responding by any error.
In my case I want to generate an unique random code and associate it to an order entry so my customers can have a user-friendlier order code than the order id. But if the api does not return any error I can not know if the code was already existing.
Can you confirm the current behavior and what workaround could you propose ?
Thank you !