Has the method of registering data in Powers Date and Time fields changed from Power Automate?
Until 2 days before
addHours (utcNow (), 9, 'yyyy / MM / dd')
I was able to register with
I started to vomit a conversion error now
Hi @mukie ,
I have made a test on my side and don't have the issue that you mentioned.
My flow with expression that you provided works well on my side.
Please take a try with your flow again and let me know if your issue still exists.
Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
New_date field that is created when a custom entity is created automatically in Dynamics365
There was a difference in the setting of this field in my development environment and production environment.
The difference was in “action”.
In a production environment, the new_date field only works with dates,
If you add addHours (utcNow (), 9, 'yyyy / MM / dd') to this field in Flow, a conversion error will occur.
In the development environment, the operation of the new_date field is user-local, and if you add addHours (utcNow (), 9, 'yyyy / MM / dd') to this field in Flow, registration was successful.
Previously, registration and updating were possible even in a production environment.
An answer was returned from MS.
In the above case, addHours (utcNow (), 9, 'yyyy / MM / dd')
I was told that by setting addHours (utcNow (), 9, 'yyyy-MM-dd') instead, no error occurred.
I asked why it happened.
To be honest, I felt uneasy about the MS system.
There are too many bugs and we don't accept them.
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
Check out the community blog page where you can find valuable learning material from community and product team members!