Share
Report
432Hello All,
Yesterday I posted here
Where I encountered some very odd issues as a result of switching browser..
Today I fire up my app, after we ''fixed'' yesterdays issues and want to try some more tests.
Purpose of the app is to update metadata fields of documents- so i select a document, fill in the fields and select the button to start the flow to update the data. The data includes a date at which this document was sent.
See examples from past flow runs:
In the top 2 pictures we see examples of flow runs before all the issues happened. We see dd-mm-yyyy being accepted as a valid datetime format.
In the 3rd picture we see a flow run from several minutes ago ; where the datetime had been passed as dd-mm-yyyy which caused it to fail.
In the 4th picture we see also a run from several minutes ago but where in powerApps i formatted date time to yyyy-mm-dd before sending it to flow.
What can I do for my system to allow me to pass in dd-mm-yyyy again ? because working with an unnatural datetime format for our region can't be done. it will cause too many confusions for endusers.
All responses (
Answers (
