My Hours to Yellowfin Integration
AI-first ETL from My Hours into Yellowfin. Governed entities, incremental sync, typed landing tables.
How Datrise loads My Hours into Yellowfin
Datrise syncs My Hours's time logs, projects, tasks, clients, team members, and billable rates into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.
Ideal for dashboards with automated data storytelling.
Endpoints
My Hours: Time tracking and billable hours for projects.
Yellowfin: BI suite with dashboards, automated insights, and data storytelling.
How My Hours entities map to Yellowfin
| My Hours entity | Yellowfin object | Notes |
|---|---|---|
| time logs | my_hours_time_logs | id PK · custom fields → flattened columns |
| projects | my_hours_projects | id PK · linked to my_hours_time_logs |
| tasks | my_hours_tasks | id PK · linked to my_hours_time_logs |
| clients | my_hours_clients | id PK · linked to my_hours_time_logs |
FAQ
How does Datrise handle My Hours's custom fields in Yellowfin?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Yellowfin types.
How does the My Hours to Yellowfin sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for My Hours
Early access
Connect My Hours to Yellowfin the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.