Forum Discussion
Errors in Power Query with format
Hi,
I'm pulling some data from Jira and I have an "Updated" column which shows date and time something was updated. I've noticed 22% comes through as an error:
DataFormat.Error: We couldn't parse the input provided as a DateTime value.
Details:
2025-04-08T15:14:30.128+0100
The rest seems fine so not sure why this specific 22% is like this, but I am unable to fix it. I've tried changing the format of the column to datetimezone but the errors for those still occur.
Any ideas?
Hi KnucklezZ,
Thanks for reaching out to the Microsoft fabric community forum.
It looks like the error you're seeing "DataFormat.Error: We couldn't parse the input provided as a DateTime value" is happening because some of the "Updated" values are formatted with a timezone offset like +0100, which Power Query doesn’t recognize as a valid datetimezone format. It expects the offset to include a colon, like +01:00.
That subtle difference causes Power Query to fail when trying to convert the value. You can fix this, by adding a step in Power Query to insert a colon into the timezone offset.
* First go to Power Query Editor and add a new column using the following formula:
= try if Text.Length([Updated]) = 28 then
Text.Insert([Updated], 26, ":")
else
[Updated]* Then, convert that new column to datetimezone type. This will normalize the format and allow Power Query to parse all rows correctly.
I would also take a moment to thank Cookistador, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
4 Replies
Hi KnucklezZ,
Thanks for reaching out to the Microsoft fabric community forum.
It looks like the error you're seeing "DataFormat.Error: We couldn't parse the input provided as a DateTime value" is happening because some of the "Updated" values are formatted with a timezone offset like +0100, which Power Query doesn’t recognize as a valid datetimezone format. It expects the offset to include a colon, like +01:00.
That subtle difference causes Power Query to fail when trying to convert the value. You can fix this, by adding a step in Power Query to insert a colon into the timezone offset.
* First go to Power Query Editor and add a new column using the following formula:
= try if Text.Length([Updated]) = 28 then
Text.Insert([Updated], 26, ":")
else
[Updated]* Then, convert that new column to datetimezone type. This will normalize the format and allow Power Query to parse all rows correctly.
I would also take a moment to thank Cookistador, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi KnucklezZ,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.Thank you! This has worked. 🙂
Can you show us an example for which the conversion worked ?
