Is there any way to emulate a default value for choice component outside a form?

Answer is likely no. Threads on this topic pre-date default being an option in forms themselves. I’m wondering if anyone has found a a trickaroo.

If you can set an action to fill the column on the way to that screen, then that would essentially be like setting a default. I do this with one of my apps where I have a custom made form. I have a compound action that sets the columns values before performing a link to screen action to open the “form”.


I was going to give you a tip but Jeff wrote almost the same I was thinking.

This is the way!



This may work. It’s an inline list > view details > choice component. So I’m thinking the default view details action would have to be replaced with a custom action to (a) set the default, (b) open detail view.

Thanks Jeff and @gvalero.

1 Like

Correct, and if needed, you could probably add an IF statement to only set the default if it’s empty. Else it would keep any previously set value.

1 Like

I would want the default to reset every time a user navigates to that detail view. So to use an example from the table in this thread, Choice 1 - Dockage should always show Anchorage as default value. I think that can be achieved with an ITE as well…


Exacely! I have asked @JackVaughan and @Mark for this very thing just last week. In fact, would love a “default value” for every entry-type component regardless of whether it’s in a form or in a details page.


How would a default value in a details screen work? Let’s say the default value for column Name is “Alice”. I open the page for a row where Name is empty. Do I see “Alice”? Does it write “Alice” to the table?

1 Like

My use case for this is details page where I dynamically show the user two sets of things. Let’s say a 1v1 chat where one can choose to chat via the comments component, or make a booking via a Webview component.

1 Like

Hm…well…perhaps… :no_mouth:

Using this example to explain what default could look like:

*ignore red square

In a scenario where all 3 options (Anchorage, Mooring, Dock) for choice 1 are available, the default displayed to the user would be Anchorage (“Alice”). If Anchorage is unavailable as option 1, the default could be Mooring, and so on. The “default” is conditional depending on the use case and not static (e.g. first row, à la single value column). Else if Alice is empty as you suggest, nothing would display. Same applies to Choice 2 and 3.

Cascading, conditional defaults (with Jeff’s tip) are achievable but amount to ~25 columns for 3 option groups.


The “why” is worth mentioning: A pre-populated choice component drives action and minimizes decision fatigue in apps that are input heavy by nature. Every little bit helps.