I have a PowerApp that uses a Flow called 'SendMeetingRequesttoSSM'. The data that is submitted (specifically the DateTimeDropdown), differs from what is sent in the email. What arrives in the email is a valid possibility for the user to choose, but it is not what was selected when the request was submitted in PowerApps. The DateTimeDropdown is a text field, not a date field.
This is my Run statement:
This is my Flow:
I submitted the info on my form and this is the result, take note of the 'Scheduled For' date/time.
This is what arrived in my email:
Is this a bug? Any tips or info is much appreciated.
Could you please share a bit more about the DateTimeDropdown control within your app?
Based on the screenshot that you mentioned, I think this issue is related to the Date Time String value (DateTimeDropdown.Selected.Value) you passed from your app to your flow.
When you passed the Date Time String value (DateTimeDropdown.Selected.Value) from your app to your flow, this string value would be recognized as a Date Time value to process in your flow. Due to Time Zone issue, the Date Time value would be displayed in different value within your Outlook email.
As an alternative solution, you could consider take a try to wrap the Sendanemail_Body_2 dynamic content with a double quotes ("") as below:
then run your flow again, check if the issue is solved.
I have made a test on my side (send email from an app directly), and don't have the issue that you mentioned. The screenshot as below:
The email sends successfully as below:
Please take a try to re-create your app, then send the email within your app directly, check if the issue is solved.
In addition, please also make sure that the Time Zone of our Outlook service is the same as your local time zone.
If the issue still exists, please consider take a try to submit an assisted support ticket through the following link:
Thank you for posting this thread @taramoe. Are you still experiencing this issue? Also please let us know if the above reply was helpful.
Yes, I'm still having this issue. I've tried using both a Run command in combination with Flow and the Office365.SendEmail functionality with the same result. It always emails the next value in the list, which is very frustrating. I've tried a variety of work arounds with no luck.
Check out the on demand sessions that are available now!
Stay up tp date on the latest blogs and activities in the community News & Announcements.
Features releasing from October 2020 through March 2021
Check out the Power Platform Community Highlights