Hi there, @AAL… your post caught my eye, and I have been trying to come up with an example that works exactly as you have described, and I must admit I can’t do it. Well, I can’t do exactly what you have described, but I do have something working that is similar and might do the trick.
First, it’s not all that hard to remove options from a dropdown when they have already been selected. You could have a custom state that’s a list, and as options are selected, you add them to the custom state. Then, with the dropdown’s Choices source defined as the entire list minus the custom state’s list, you’re all set. Well, sort of.
The problem with the above, of course, is that as options are being removed from the dropdown, they can’t be shown as selected in the dropdown for each employee, and there is no way to save the selections to the database because the dropdowns don’t have values.
So, all of the above being said, the only thing I could come up with is that through auto-binding or the An input’s value is changed workflow action, you save the selections to each employee as they are selected, and you show the
Current employee's asset (assuming you name the field
asset) in another element in the repeating group. Then, with the dropdown’s Choices source defined as the entire list minus a list that is a search for employee’s asset, you get an experience that is very similar to what you have described.
If it helps, here is a screenshot of the dropdown configuration where I used an option set to define the assets and I used the
User data type instead of a data type called
Who knows… maybe I am missing something simple on this one, and someone else will be able to provide a much more straightforward solution. That being said, I hope this response is helpful, even if it’s just food for thought.