Option sets as page data sources

Bugs
1

Hello,

Is it a bug that a page can’t receive an option from an option set as it’s data source?

I want to be able to create all the pages of my app (the app I am building is a PWA) as options in option set called pages, and then navigate to a page called “app” and send the page as the data source. The page “app” will then show or hide the data based on the page.

I am already doing the same kind of thing by using a url variable called “page”, but it would make much cleaner urls to not send the url variable “page” each time a user navigates. It would also make the show/hide logic slightly more readable.

If this isn’t a bug, what is the basis of the decision to not allow a page to receive an option from an option set as it’s data source?

Thanks

2

I don’t think it’s a bug… but you can easily achieve the same thing by just setting the main page container (or any container on the page) to the content type of the Option set, then read the URL path do set the Option.

3

Thanks Adam, that’s a good solution! Still doesn’t make a lot of sense to me not to allow pages to receive option sets as data source though, if that’s an intentional design decision.

4

This topic was automatically closed after 14 days. New replies are no longer allowed.