The scenario is a flow triggered by a form submission. The flow adds the form responses to an Excel file in SharePoint and then invokes a script in the file to do some additional processing.
Because the anonymous respondents can be located anywhere in the world, I needed to convert the form submission date and time stamp to Eastern Standard Time. Looking online I found the required timezone conversion function, but the example used a Compose action to invoke the function and then used the output from that to set a variable.
I don't like adding extra steps in my flows, so instead I used the Initialize Variable action to define a variable to hold the result and in the initial value field for the action I created an expression with the timezone conversion function. In the "Add a Row to an Excel file" action, I used the resulting variable for the corresponding field in the SharePoint Excel file.
This works, but I'm wondering if there is some hidden gotcha to this approach?
