I have a SharePoint list containing three number columns: day, month, year. I would like to create a flow with the following actions: "SharePoint When a new item is created" + "Delay until". Delay until requires input for day, month and year. But I'm not able to use the values from my SharePoint Item. The only thing I can use as reference is the Item-ID. In other actions I can access the content from the SharePoint item. Why can't I use the columns for delay?
Thanks for your help.
@Anonymous
You will find the image here instead
https://drive.google.com/file/d/0ByiGy3MFstuwSkdaWWlhUTVmdlk/view?usp=sharing
Anyway, as I mentioned earlier, I doubt this trick is design intent. I didn't find it documented in Tutorials and nobody from Microsoft staff has answered so far 😞
Sorry, but your picture/screenshot is not displayed. I can't see anything. Would you please post it again?
Thanks.
@Anonymous
This is how I invoked a function from an Action Block. However, I haven't found this approach documented so I'm not sure if it 's officially supported and thus if it will be supported in the future
Hope this helps
Hi @efialtes
sorry, but I don't know how to work with your answer. Would you please give some more details on how to add a function.
Thanks
@Anonymous
I haven't access to Sharepoint List for testing, so not sure if the following suggestion can work
There is a convert function to integer, defined in
https://msdn.microsoft.com/en-us/library/azure/mt643789.aspx
Can such functions be invoked from Action blocks other than Conditions? There is a potential workaround posted in this thread: https://powerusers.microsoft.com/t5/Flow-Forum/Workflow-Variables-in-Microsoft-Flows/m-p/1711#U1711
So following @xrobfox recommendation, I tried to add the following expression "{@replace(item()['Borrow--Date'], '2016-', '16-')}" to OutlookSendEmail.Body and it worked!
Not sure if this can be also used with DelayUntil. Also unsure if this workaround is design intent, I mean , if it is officially supported, or not.
BR
Hi Samuel,
thank you for your fast and detailed answer. That makes sense 🙂 . I will check if I could create a integer column on SharePoint site.
But if you could check the possibilities on your side, would be great to. I think type conversion could be helpfull in many other Flows, too.
Thank you.
The options you get when specifying inputs for an action are filtered by which type of input they support. The "Delay" and "Delay until" actions only support integers. It turns out that when you add a number to a sharepoint list in the UI, it's always a double. There seem to be some pretty involved workarounds to add an integer column to a sharepoint list, but assuming you can do that, this should work.
Otherwise, the delay actions should be updated allow other types as well (as long as their convertible to ints). I'll see if that's feasible on our side, or generically, expose the type conversion functions that the underlying definitions already support.