User Specific Data for Public Apps

Ask for Help
1

We’re using choice components tied to user specific columns in the user table.
Our app is public with the option to sign in.

Currently the choice components aren’t working when we’re not signed into the app.

Any ideas? Should this work or is it because the user specific columns are in the user table?

I read on the forum that user specific columns can be used on public apps and the data is cleared when users close the app/cookies expire.

2

Create a new one row table. Move the usc’s for visitors into this table. Use the one row table as the source of your screens.

3

Thanks Eric, can the new user specific table also be used for logged in users?

1 Like
4

Sure can. I may be a little unconventional but for a public app with optional sign-in I always use a one row table with usc’s as the source of my screens.

An exception to that rule would be attaching the ‘view profile’ screen to the users table… because I know the user would already be signed in :wink:

2 Likes