I want to let you know what are the boundaries of this solution. It just repeatedly checks whether an action occurs and in case it's "check" does not happen in the moment, when an event occurs, it might never get triggered.įor the paid version there is no such risk as it works somehow like the Remote Event Receiver.įirst things first. Just be aware, that in the free version Flow does not triggers itself once an event occurs. Recently I have realized, that there is a set of excel actions in microsoft flow! All of us, who has SharePoint Online, has also a free version of Flow available. ![]() ![]() The most common workaround is to convert the XLSX file into a plain, csv file and then to work with the data from the file using collections (I will write about it in second post). So in the end, there is no straightforward way to achieve it. Moreover Nintex products for SharePoint Online (neither nwc nor nintex for office 365) don't have any "ootb" actions that would fill that gap. However, insharepoint online there is no such powerful mechanism. In Nintex 2010, 20 for SharePoint (Standard version even) on-premise of course, there was a possibility to use excel services to query and work with the xlsx and xls files' data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |