"Created on" date column
A "date created" column allows you to keep track of when each record or entry in a table was initially created. This information provides a timeline and helps you understand the sequence of events or the order in which items were added. Tracking creation date can be utilized for data analysis and trend identification. You can identify patterns, assess growth rates, or track changes in certain metrics. Additionally, you can easily sort or filter the table based creation dates, enabling you to focus on a particular time period.
Use this when what you care about is always the day that the row was created. Example: The results table of a feedback form. The “created on” column will always be the same as the date the row was created, aka the date the response was submitted.
Add a calculation to your column. Configure your calculation to calculate from “Row property” and use the property “Created on”. . Your settings will look like this:
If you prefer to use the formula builder, use the thisRow.Created() formula.
Use this when the date you care about is usually the date that the row was created, but not always. Example: An action item table in a meeting notes doc where action items are usually added during the meeting, but sometimes users add action items after the meeting and need to back date. Users are using the “created on” column to keep track of the date of the meeting, and don’t really care about the exact date the row was created.
In the column options, set the “Value for new rows” field to “Date created”. It should look like this:
When a new row is created, the field is left blank. The user would manually go in and add the date.
Use this when your useful metric isn’t tied to when the row is actually created. Example: A company wiki table where new entries ideas are added all at once during a planning meeting, and the “created on” column should display the date work started on it, not the date the row was added to the table.
One of the risks of having a manual field is that users may forget to add a date to the date field. One way to combat this is to set up some conditional formatting to flag a missing value to the user, such as coloring blank fields red. For assistance with setting up conditional formatting, check out this help article.
Configurations
There are three ways to approach adding the created date for each row. The best approach depends on if the date you actually care about is the same as the date the row was created.Option 1: Calculation
The date is automatically set using the metadata of the row based on the exact time the row was created and cannot be changed.Use this when what you care about is always the day that the row was created. Example: The results table of a feedback form. The “created on” column will always be the same as the date the row was created, aka the date the response was submitted.
Pros
- Fully automated: Coda keeps track of when things are created without you having to think about it
- Clean data: the field is uneditable so you can be confident the value was not accidentally changed.
Cons
- Non-editable: you cannot decide to go in and adjust the date in the future
Setup instructions
Step 1: Create a new column Step 2: Add a calculationAdd a calculation to your column. Configure your calculation to calculate from “Row property” and use the property “Created on”. . Your settings will look like this:
Option 2: Preset
The date is automatically preset to be the exact time the row was created, but the user has the option to override/update it.Use this when the date you care about is usually the date that the row was created, but not always. Example: An action item table in a meeting notes doc where action items are usually added during the meeting, but sometimes users add action items after the meeting and need to back date. Users are using the “created on” column to keep track of the date of the meeting, and don’t really care about the exact date the row was created.
Pros
- Fully automated: Coda keeps track of when things are created without you having to think about it
- Editable: you retain the ability to change the value should the need arise
Cons
- Data integrity: because the field is editable, you cannot be certain a value has not been changed, either intentionally or by accident
Setup instructions
Step 1: Create a new column Step 2: Add a preset valueIn the column options, set the “Value for new rows” field to “Date created”. It should look like this:
Option 3: Manual
When a new row is created, the field is left blank. The user would manually go in and add the date.Use this when your useful metric isn’t tied to when the row is actually created. Example: A company wiki table where new entries ideas are added all at once during a planning meeting, and the “created on” column should display the date work started on it, not the date the row was added to the table.
Pros
- Flexibility: The date is completely independent from when the row was created, allowing you to make rows in advance/after the fact.
Cons
- Time consuming: Every row needs will need to be manually set
- Data integrity: users may forget to set the field, set an incorrect date, or accidentally change the date after the fact.
Setup instructions
Step 1: Create new column Step 2: Set column type to “date” Step 3: Consider adding conditional formattingOne of the risks of having a manual field is that users may forget to add a date to the date field. One way to combat this is to set up some conditional formatting to flag a missing value to the user, such as coloring blank fields red. For assistance with setting up conditional formatting, check out this help article.
Was this helpful?
YesNo