LambChoptheKid
New Member
- Joined
- Dec 10, 2022
- Messages
- 35
- Office Version
- 365
- Platform
- Windows
Hey everyone,
I'm experiencing a problem with Power Query making a mistake in pulling an hour from a datetime.
In the original table, the "Hour" column (2nd from left, in 24 hour format) is not there. I added that column by highlighting my datetime column in Power Query, going to the "Add Column" section in Power Query, going to the "Time option" and selecting "Hour > Hour" from the dropdown list. Screenshot of the what I mean below.
The problem I am running into is that it has made a mistake in row 3131 which has caused all subsequent rows to be incorrect as well. Screenshot below.
I could easily draw up a different non-Power Query solution to this problem, but I am trying to make better use of these tools and am wondering: 1. Why would Power Query incorrectly parse this information? 2. What can be done within Power Query to correct this? I would love to be able to use this Power Query function in the future but errors like this in a relatively small data set would make that very challenging.
I hope that I have adequately explained my problem here, but I would be happy to offer any clarification that would be of use in the comments.
Thanks for any assistance!
I'm experiencing a problem with Power Query making a mistake in pulling an hour from a datetime.
In the original table, the "Hour" column (2nd from left, in 24 hour format) is not there. I added that column by highlighting my datetime column in Power Query, going to the "Add Column" section in Power Query, going to the "Time option" and selecting "Hour > Hour" from the dropdown list. Screenshot of the what I mean below.
The problem I am running into is that it has made a mistake in row 3131 which has caused all subsequent rows to be incorrect as well. Screenshot below.
I could easily draw up a different non-Power Query solution to this problem, but I am trying to make better use of these tools and am wondering: 1. Why would Power Query incorrectly parse this information? 2. What can be done within Power Query to correct this? I would love to be able to use this Power Query function in the future but errors like this in a relatively small data set would make that very challenging.
I hope that I have adequately explained my problem here, but I would be happy to offer any clarification that would be of use in the comments.
Thanks for any assistance!