Hi all,
Initially, everything functioned smoothly, but abruptly, my search criteria failed because the choice component isn’t writing to the first row in the Users table. Can this be resolved?
Hi all,
Either your screen isn’t attached to the first row (possibly due to a filter on the screen or you explicitly navigates to that row in the table), or you are writing directly to the signed in user’s row, or you have row owner enabled in that table. How are you writing values to the user table?
Generally for things like custom filter or search functionality, I prefer to have a separate single row table to hold all of those values and to be used as the driver for the screen.
1 Like
Thank you Jeff. I’ll give it a try. However, I do have two questions:
- Does it have to be user-specific to function properly?
- Sometimes the choice itself forces you to write to a non-single row table, does that mean I must change source of the tab from beginning?
If you go the single row table route, then yes all input values need to be user specific if multiple users will be using the app.
If your intention is to utilize the user profile, then you need to ensure that you are both writing to and retrieveing from the user profile row instead of always looking for the first row in the user table.
3 Likes
Thank you Jeff, it makes sense.
Helpful as always.
1 Like