I’m going to bookmark this question and use it as an example of how to ask a question.
Choice components do not support actions, so it will not be possible to have separate screens. Everything will need to be on a single screen with visibility settings controlling what is seen.
Assumption:
- Both the like/favourite and already purchased components are writing to user specific boolean columns in your items table.
I would probably create a separate working table to drive this screen. In that table, create the following columns:
- Template column that contains the word
true - Multi-relation column that joins the template column to Items->Is Favourited
- Multi-relation column that joins the template column to Items->Already Purchased
- User Specific column to hold the user selection from the segmented choice component
Then on the screen, the following components:
- Choice component, as shown in your screen shot
- Inline List using the first multi-relation as a source. Visibility should be when choice is ‘Liked’
- Inline List using the second multi-relation as a source. Visibility should be when choice is ‘Already have’
- Component for “No Liked Items”. Visible when choice is ‘Liked’ and Liked relation is empty.
- Component for “No Purchased Items”. Visible when choice is ‘Already have’ and Purchased relation is empty.
I think that should do it. Note that Inline Lists will automatically hide themselves when there are no items in the list, so there is no need for an extra visibility condition on those to check if the associated relation is empty.