- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Generating timestamp for each hour problem
Context:
I have a table with timeshifts of people working with an hourly gross rate associated with it. In it's original form, the timeshift entries only contain daily timestamps indicating:
- On what day did the shift take place
- Employee name
- Timeshift started
- Timeshift ended
- Hourly gross rate
What I want to achieve is a graph that shows labour costs per hour within a 24h day. Something like this:
Since I don't have a row per hour in my data set, I followed THIS tutorial to create an "hourly timestamp" to be able to visualise that graph.
Everything looked fine because I got this result:
As you can see, this employee has an hourly gross rate of 30,26 which in Power Query always shows 30,26 (which is correct).
Now, when I add this to a graph/table, that hourly gross rate starts to go crazy. Instead of getting 30,26 per Hourly Timestamp of a shift date, that number grows the further we go down. So on Mar 10, the hourly gross rate is okay, but the day after it doubles for every single row.
I have my Shift date connected to my main date table. I also tried disconnecting it to see if that's the problem, but it isn't. I am really puzzled why does Power Query show one set of numbers and on the dashboard I get something else. I know that I "artificially" generated those timestamps so is that perhaps the problem?
Could someone let me know what the issue is or how to do this without generating those artificial Hourly timestamps? Many thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Found the issue. Once I added the source file name (since these are multiple CSVs appended from blob storage) I was able to identify that the issue was in the CSV exports.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Found the issue. Once I added the source file name (since these are multiple CSVs appended from blob storage) I was able to identify that the issue was in the CSV exports.

Helpful resources
Subject | Author | Posted | |
---|---|---|---|
01-03-2025 02:49 AM | |||
12-17-2024 02:05 PM | |||
11-20-2024 12:10 AM | |||
10-27-2022 12:31 AM | |||
01-09-2025 10:16 AM |
User | Count |
---|---|
141 | |
115 | |
84 | |
63 | |
48 |