I have a data type from which I’m selecting a random item. After an item has been selected, I’m adding it to a list of used items. From there I have a conditional set to NOT run the workflow when a used item is chosen. However, I don’t want the workflow to just end when the condition isn’t met.
My objective is to have the workflow run until a fresh item has been selected. I’m guessing I’ll have to use recursion here, but I’m not sure what to use for the conditional.
Hi there, @sydney22… is it by design that a used item can be chosen even though you have a list of used items and could remove that list from the main list before selecting the random item? In other words, why not avoid the situation where a used item can be chosen?
Best…
Mike
why not avoid the situation where a used item can be chosen
Ideally I’d do exactly this, but the data set is publicly available so I don’t want it manipulated by other users. I probably should have used Option Sets for this, but it was faster for me to bulk upload the data into the DB.
Sorry, but I don’t follow what any of that means. You probably need to share more details (including screenshots) of what you are trying to accomplish. I still think you should be able to remove the used items before selecting a random item, but again, I don’t understand your reply, so maybe not.
Oh I was referring to privacy rules- I didn’t want one user to delete a used item from the database. I’m brainstorming this out before I build it. I believe the answer is to run the recursive workflow until the selected random item is not on the used list.
Well, it still seems to me that you should be able to do something like this, but again, I don’t really understand your replies, so I could be way off.
This is interesting- I like how you nested everything. I will try that out- beats having to schedule a WF.
