Hi,
Is there a simple way to add a “date created” in the user sheet. Obviously to record the date the account was created? I thought “currentdatetime” would be available but it isn’t.
If you have any tips, not to complex thanks
Stan
HI,
If you have many records you need add manually the date, and for the new users, set the currentdatatime
A default value on a date column would be amazing!
3 Likes
currentdatetime isn’t availble in the layout editor on user profil page
How are you adding users? You can use an app interaction / workflow to set the column value where the Current Date is an available option?
1 Like
thanks but where is this screen coming from? sorry still a bit rookie
How are you adding users to your app? Are you getting them from some other table, or are you manually entering their information?
user table is only populated by login, no manual work or database involved.
If you are just using the “Invite Users” from the Share button, then you most likely won’t be able to do this because you aren’t telling it what you want from there.
For all of our apps, we have a screen (admin) that allows us to add users so we can set other fields like this including date, images, employee ids, etc.
2 Likes
User log in because they want to use the app. they are not invited, they are “suggested” to do so by subscribing 
therefore i need a creation date for their “account creation”.
If you have some sort of onboarding process for new users, then you could have a final button that sets the date.
6 Likes
This ^^
1 Like
This approach sets a date-time value when the user performs a specific action during the onboarding flow. The date-time is set by the end user, and it is that of when the specific action is taken (presumably when the onboarding flow is finalized).
This first approach has a higher likelihood of giving the signup date than the next approach, though it’s no guarantee, because a user could sign up on one day and go through the onboarding flow days later.
This approach also requires at least one screen and one action from the end user that otherwise might not be needed or desirable.
This approach sets a date-time value when an admin performs a specific action during an internal approval (or data enriching) process. The date-time is set by an admin of the app, and it is that of when the internal approval is done, not necessarily the date-time when the end user truly first signed in to the app.
Unless admins check daily for users in the waiting list to be approved internally, there is a good chance user signup and admin approval don’t happen on the same day. Either way, this date-time doesn’t truly represent the user signup, it’s a proxy at best.
This approach requires manual work from the admin.
In both approaches, the date-time values written to the table aren’t the true values of user signups.