I’ve seen another post on preventing duplicate data creation here (Prevent from create duplicate data?). The solution suggested is to add a constraint at the event condition level.
However let’s say you have a really long flow of actions (only one of which is to add a new thing) - that would mean that you need to maintain that set of actions twice in every case where you want to prevent duplicate data from being added. That can become a pain if you make changes to an action or set of actions because you now always need to do it twice.
Instead, what I’ve been doing to prevent adding duplicates is to rather just use “Make changes to thing…” instead of “Create a new thing…” and select the “Create if doesn’t exist” option.
However, where that is breaking down for me is when I need to add something to a collection - because typically the collection is on an object. So if you select the “Create if doesn’t exist” option it will apply that to the base object rather than the collection. What I want is for the “Create if doesn’t exist” option to apply when adding to the collection so that I don’t add a duplicate to the collection.
Any suggestions on how I should be doing this?