@merwan what's the status on this feature? I'm trying to do some simple calendar event creation and am not able to leverage the same syntax I see in existing templates.
Any updates? This seems like a more fundamental and essential business feature for minimal workflow, much more than connecting to twitter!!!
Adding a first class function editing experience in Flow continues to be on our backlog and something we plan to address in the future. However, in the meanwhile, here's a workaround you can employ.
1. In your flow, add a compose card.
2. In the Compose card, you can execute workflow functions specified here: https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-workflow-definition-language
3. An example to get today's date in the format of 2017-05-16, I would do: "@utcnow('yyyy-MM-dd')"
I just found new actions: "Initialize variable", "set variable" and "increment variable". When initializing a variable, the following fields must be filled: name, type (boolean, integer, floating, string, object, matrix) and optionally value. I guess "Increment variable" is only valid for integers and floats, according to https://flow.microsoft.com/es-es/blog/error-handling/
However, when dealing with "set variable" there seems to be a bug according to https://powerusers.microsoft.com/t5/I-Found-A-Bug/Error-Variables-Set-Variable-quot-The-request-cont...
SetVariable is currently bugged and isn't really working for anyone right now, unfortunately. We're hoping to get a fix out with next week's deployments starting on June 5th.
I'll be bumping the following thread with updates on the issue:
Thanks for letting us know about this issue! We appreciate the help!
There has been some time passed since the last post in this discussion, but I managed to make my WDL expression work in InitializeVariable by putting a space symbol before it.
Without the space before the expression it doesn't work at all. God, this is so buggy product 😞
"God, this is so buggy product"
One does get the feeling that there is a huuuuge (with much Trumpian emphasis) disconnect between the MS development teams and the senior management.
The senior management even have to ask partner organisations like Lenovo to discover that MS developer output is rubbish, and the developers have been lying and blaming others to cover their tracks ...
"A diificult computer sicence problem", my rse.