We are trying to find the easiest way to setup a date time stamp field, that is, either when creating a new record or triggered by filling in one of the others cells in a new record. that time/date stamp field is populated with the current date and time and it would be static, that is, would not update to tomorrows date if it is accidentally clicked again.
What is the easiest way to do this?
We are looking for a way to auto-populate the date field for our Interactions table. Our sales team needs to take notes of every call and each manual step that gets in the way is one more block to completing the data entry. Is there some non-zapier way of doing this? Forms? Default input values for formulas? We’d like the sales rep to be able to change a date after the fact if they are logging calls from prior days.
+18We are looking for a way to auto-populate the date field for our Interactions table. Our sales team needs to take notes of every call and each manual step that gets in the way is one more block to completing the data entry. Is there some non-zapier way of doing this? Forms? Default input values for formulas? We’d like the sales rep to be able to change a date after the fact if they are logging calls from prior days.
@Bill_Sewell, @syd_Levy - I think you should be able to use the “created time” field type for both of these scenarios. It is automatically created when a record is created and is static:
If you use a form to populate your table it doesn’t even appear as a field in the form (no need as it is autopopulating).
JB
@Bill_Sewell, @syd_Levy - I think you should be able to use the “created time” field type for both of these scenarios. It is automatically created when a record is created and is static:
If you use a form to populate your table it doesn’t even appear as a field in the form (no need as it is autopopulating).
JB
is that in the regular field drop down list?
+18is that in the regular field drop down list?
Yes, although it isn’t available as an option in the primary field of the table, just the other fields.
JB
@Bill_Sewell, @syd_Levy - I think you should be able to use the “created time” field type for both of these scenarios. It is automatically created when a record is created and is static:
If you use a form to populate your table it doesn’t even appear as a field in the form (no need as it is autopopulating).
JB
Hi Jonathan, if you are still there.
In this posting you mentioned that records created with a form are automagically time-stamped. That is handy to know. Can you tell me how one would be able to search for a range of records between any two dates through the use of these automatic time-stamps?
All help much appreciated.
Thank you.
+18Hi Jonathan, if you are still there.
In this posting you mentioned that records created with a form are automagically time-stamped. That is handy to know. Can you tell me how one would be able to search for a range of records between any two dates through the use of these automatic time-stamps?
All help much appreciated.
Thank you.
Hi @Teacher_Lin - you can filter a view where the created date is greater than X and less than Y, as long as you have added a field with created date/time. If you don’t want to see this field in your views you can hide it (but it will still be available in the filters).
+2@Bill_Sewell, @syd_Levy - I think you should be able to use the “created time” field type for both of these scenarios. It is automatically created when a record is created and is static:
If you use a form to populate your table it doesn’t even appear as a field in the form (no need as it is autopopulating).
JB
thanks so much for that great tip!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
