Forum Discussion
Program execution reached an invalid state
I solved the issue.
After looking more in details it appeared that the problematic columns changed for type date/time were already in date/time format before the "Changed type" step.
And it looks like Power Query doesn't like when we change a column for a type it already has !
It makes no sense but that's the way it is
Have a good day
Cado
Hi Cado_one
Thanks for reaching out to us.
May I ask what type of field are you trying to convert to date/time format? And in order to better troubleshoot, I need to confirm the following problems first
(1) I read the link you posted, and some users said that there is also a problem with the report on the service. Could you please reconfirm whether the SQL data can be updated to the report on the service?
(2) Was the report created before and worked fine on both desktop and service before? Then are there any changes to the report, such as privacy level settings.
(3) Regarding this error, it is usually due to "Your database connection has timed out, or your database has been closed. You may need to retry the query, or reconnect the session." If you create a new pbix file, and establish a connection, then change the type in power query, will you still get the same error?
(4) If none of the above helps, please let me know, I will investigate further.
Best Regards,
Community Support Team _Tang
If this post helps, please consider Accept it as the solution to help the other members find it more quickly.
Hi v-xiaotang
(1) In my case it's just on the Desktop (I didn't republished the report to service ever since because I'm afraid it won't work anymore if I do)
(2) The report is not new, it was working perfectly and this error suddenly appeared without any change from my hand.
(3) I just tried to create a new connexion in a new report, it's okay at first but as soon as I change a column type to Date/time in the query editor the same error appears.
(4) Thanks for helping me, I'm looking forward to read from you !
Thanks again,
Cado
I solved the issue.
After looking more in details it appeared that the problematic columns changed for type date/time were already in date/time format before the "Changed type" step.
And it looks like Power Query doesn't like when we change a column for a type it already has !
It makes no sense but that's the way it is
Have a good day
Cado