There is a workaround to get what you want.
You need a helper table with enough rows to cover the maximum number of images you’d expect to store in a single row in a multiple images column.
To set it up:
- In your User Profile row, create a Single Value column that addresses first->whole row of your Helper Table
- In your Helper Table, number your rows starting at zero (see here)
- Add a User Specific Text column. This will store the RowID of the row you are currently viewing.
- Add a Single Value column that applies the previous column to all rows.
- Add a Single Relation column that matches the Single Value column with the RowID in your Wardrobe table
- Add a Lookup column that fetches the Multiple Image array via the relation.
- Add a Single Value column that takes N from start of the Lookup column, where N is the helper table row number/index.
- Finally, modify the action that’s used to navigate to an item by firstly setting the selected RowID in the Helper Table, via the User Profile Single Value column.
If you get all that right, you can use the Helper Table as the source of a Collection on your details screen, filtering it where the final single value column is not empty.