I have a collection set up that allows me to have editable text and a rich-text side-by-side.
I would like the column being edited/displayed to be dynamic.
How can I add a selector to the top that allows the user to select which column is being edited?
The data is literally just one row – and I’ll probably end up with dozens if not hundreds of columns.
Well I’m not sure if the target column of a text entry could be dynamic in that way. Instead you could put your data into rows and then choose which row you are editing by ruling a filter with your selector
Thanks but based on an earlier conversation. They need to be in columns because of the way that they are going to be used. Basically setting up a wordpress type presentation.
I had them in rows and it just wasn’t going to work.
I have a theory “with enough ITE columns… anything is possible” 
Let me think about it. I’ll be back later
With both tables I tried to think of ways to do it with relations. I still have the table by rows set up.
It’s weird that one type of component needs them to be in columns and another type of component needs them to be in rows.
Perhaps a helper table type of situation?
I had a nightmare last year when I try to do some sort of a front end like this.
Basically, what I understand is you want to allow your users to dynamically change what is displayed on the screen and what columns should be available for edits?
I think you can have a choice component with the values being column names.
Then, have an if-then-else column based on that value and display the if-then-else value on your screen.
For editing, use conditional visibility but you will have to add components for all your columns.
It’s actually just to put a screen together to allow me to have one central place to manage the content of all the pages. I would never dream of allowing my users to do that.
I have other options. I could maintain all the rich texts formatting in documents. And just paste them in when they’re changed. But this seemed like a really cool suggestion that @Jeff_Hager made.
I’m starting to feel like I should’ve left this thread under the original post.
I always push the limits of tools that I use.
Yeah, I didn’t realize to scope of potentially hundreds of columns. You could stick with everything in rows, which would make it easier to build your maintenance screen, but then you will still need a bunch single value columns to pull from each row and get everything on a single line for the front end user’s view. Either way it’s going to be a bit ugly, but once it’s set up you hopefully don’t have to add a bunch additional columns and logic.
I’ve been kind of following both of your related threads without making comment so far.
As I understand it, this for the maintenance of some sort of FAQ list, yes?
I really don’t understand why you wouldn’t just keep everything in rows, use a collection, and make the collection item details screen the side by side layout?
That seems the simplest and most obvious solution to me 
In this particular case there’s maybe a dozen screens. Each one is formated differently and so my idea Was to use rich text to make it look nice. But each page has submenus that lead to Other pages that may also Have some menus.
And the org that wants this is really not familiar with Glide but he knows wordpress like the back of his hand so I want the layout to look familiar and similar.
@Darren_Murphy , I suppose you got that impression because the page that I screenshotted Looks a bit like an f a q but it also has a menu at the bottom that leads to Other pages that do different things. I purposely left off the menu so as not to confuse the issue at.
Thank you everyone for your input.
I should add that this is not a data driven app but a Companion website to a book and will have all the content of the book. He used wordpress to create his website and wanted them app that works like it.
