This article applies to Aiwyn Practice.
Where the New Time Entry dialog is stored in the external data warehouse. Use this when building a report or query against timesheet data.
Screen: Timesheet → New Time Entry
Table: time_management_entry
Entry type, date and duration
| UI element | Table | Column | Notes |
|---|---|---|---|
|
Time / Expense / Operational / Time Off (tabs) |
time_management_entry |
entry_type |
The tab chosen sets the entry type; each tab shows a slightly different set of fields |
|
Start Date & Time |
time_management_entry |
logged_at |
Entered local, converted to UTC before save. Day-boundary reporting has to convert back before grouping |
| Duration | time_management_entry |
units |
HH:MM converted to decimal units. raw_units is a separate derived column this form does not write directly |
Client and project
| UI element | Table | Column | Notes |
|---|---|---|---|
| Client | time_management_entry |
client_id |
|
| Project | time_management_entry |
job_id |
Labeled "Project" in the UI, but the underlying record is a job |
| Task | time_management_entry |
task_id |
Optional. Selecting a task auto-fills Work Code from the task's task type |
| Work Code | time_management_entry |
entry_code_id |
Notes and comments (scroll 2)
| UI element | Table | Column | Notes |
|---|---|---|---|
| Notes (Client-Visible) | time_management_entry |
internal_notes |
The column name is the opposite of the label. This field is the client-facing one |
| Comments (internal use) | time_management_entry |
comments |
Internal only, despite the neutral column name |
The label-to-column mapping for notes is inverted relative to the names. Notes (Client-Visible) writes internal_notes, and Comments (internal use) writes comments. Anyone assuming the column names describe visibility will publish internal text or suppress client-facing text.
Related
- Data warehouse field reference: Settings
- Data warehouse field reference: Projects
- Timesheet screen and field reference