This may sound elementary but what are some good use cases for this feature?
I’ve been so dumbfounded lately with the amount of awesomeness that’s been shipped today haha
1 Like
SO many use cases…but really it’s anytime you want to update a row ANYWHERE with a user profile column. My immediate use case was the need to add which “day” a user was on based on their start date of a program to a log. The log was filtered so I couldn’t use a relation/lookup/template/SingleValue—only an addRow>UserProfile columns would work. Now it does!
Ahh! So user-specific, time-based, conditional visibility has now been “activated”? haha
(Thanks too!)
1 Like
My use case is to make a value ‘true’. I absolutely despise creating semi-useless template columns.
4 Likes
Agreed! Or assigning a user role upon onboarding…if this button push then assign “Registered” if that button then “Guest”
6 Likes
@David, when might we see “Screen” added to the “Add Row” action? I want to allow my users to add ingredients to a recipe by clicking them from within the edit page but the Recipe ID and Ingredient ID are on separate glide sheets 
4 Likes