Infoveave Data Automation — Date & Time
A transaction date column becomes Transact_Year, Transact_Month, Transact_Day, and Transact_Weekday in one step — the exact time dimension columns your dashboards and pivot tables need without any formula work.
Date columns store a complete point in time, but reporting and analysis always operate on date components — year for annual trends, month for monthly comparisons, day of week for traffic patterns, week number for weekly KPI tracking. Building these components in a BI tool or spreadsheet requires formulas or calculated fields applied per column. Extract Date Component produces all the time dimension columns you need in one pipeline step, using a configurable prefix to keep them organized, and ensures the same date decomposition logic applies consistently on every scheduled data refresh.
Extract individual date components — Year, Month, Day, Week, DayOfWeek, and more — from date columns in Infoveave as separate named columns. Build time dimensions for reporting, enable date-based grouping and filtering, and prepare date breakdowns for dashboards.
Extract Date Component is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
Real scenarios where this transformation saves hours of manual work.
A retail analytics team processes daily sales transaction data with a single transaction date column. Extract Date Component adds Transact_Year, Transact_Month, Transact_Day, and Transact_DayOfWeek columns from the transaction date. The team's dashboard can then group sales by month, compare year-over-year trends, and identify which weekday generates the highest transaction volume — all from column-level groupings without any formula work in the dashboard tool.
A finance team processes a general ledger dataset with a posting date column. Extract Date Component adds PostDate_Year, PostDate_Quarter, and PostDate_Week columns. The team can then aggregate journal entries by financial quarter for period-close reporting, rank weeks by posting volume for workload analysis, and filter the dataset to a specific fiscal year without date parsing logic in the reporting layer.
A manufacturing operations team processes machine production logs with a timestamp column recording the event time. Extract Date Component adds ProductionLog_Year, ProductionLog_Month, ProductionLog_Day, and ProductionLog_DayOfWeek columns. With the day-of-week column added, the team can compare production throughput across weekdays versus the Monday start-of-week pattern, and filter logs to specific months for maintenance window correlation analysis.
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
DateMondayYear, Month, DayTransact_TrueInput Data
| ID | Date |
|---|---|
| 1 | 2023-09-15 |
| 2 | 2022-05-20 |
| 3 | 2021-12-30 |
Output Data
| ID | Date | Transact_Year | Transact_Month | Transact_Day |
|---|---|---|---|---|
| 1 | 2023-09-15 | 2023 | 09 | 15 |
| 2 | 2022-05-20 | 2022 | 05 | 20 |
| 3 | 2021-12-30 | 2021 | 12 | 30 |
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Date column
Select the column containing the date or datetime values to decompose. The column can contain dates in any standard format — ISO 8601, slashed, or other recognizable patterns. Each row's date value is parsed and decomposed independently. Select the date column that represents the time dimension most relevant to your reporting or analysis use case.
Components
Choose one or more date components to extract from the date column. Available components include Year, Month, Day, Week (ISO week number), DayOfWeek (numeric or name), and additional components depending on the date scope. Select only the components your downstream reporting or aggregation actually needs — each selected component produces one new output column.
Prefix
Define a prefix applied to the name of each output component column. If the prefix is Transact_ and you select Year and Month, the output columns are Transact_Year and Transact_Month. Using a consistent prefix that reflects the source date column name keeps extracted component columns organized and easy to identify when the dataset contains multiple date columns with their own extracted components.
Start Day Of Week
Configure which day is treated as the first day of the week for week number calculation and DayOfWeek ordering. Select Monday for ISO week convention used in Europe and international reporting, or Sunday for US calendar convention. This setting only affects week number and day-of-week component values — other components like Year, Month, and Day are not affected by this setting.
Everything you need to know about Extract Date Component in Infoveave.
Transformations in the same family as Extract Date Component, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
Extract Date Component is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?