@tlarsen7572, @neeleshapatil and @DavidP,
Personally, I would use a TREE. If the issue with the tree is the need to know how to setup the tree, that can be solved as a workflow reading the option data worksheets. The tree is dynamic in that any update to the options available could be made readily available to the application (instantly if the tree build is the first of a chained application).
Now, given the constraints I offer you a way to achieve what you want. It is less flexible and requires a minor change to the ask.
Radio buttons can be configured as GROUPs in the designer view. Furthermore, they can collapse. You can setup the options (tree) as separate radio buttons so that you can know SERVER/SITE/PROJECT/WORKBOOK. This won't easily scale, but it is a possibility (given your dislike of trees).
Alteryx ACE & Top Community Contributor
Chaos reigns within. Repent, reflect and restart. Order shall return.
to my youTube channel.