I recently was asked a question: how can I use the signature from the Nintex Mobile inside a document being generated by the Generate Document action? Unfortunately this is not yet feasible only using Nintex products. This is because Nintex Workflow for Office 365 is not handling correctly the binary data (it loses null bits) so what I proposed was to use Microsoft Flow.
The Nintex Xchange conference in San Diego has just finished. Although I haven’t had the opportunity to be there myself, our community is sharing fast still hot news from the event. I decided to put them in order facing my personal interests.
Still being under impression from working with Azure Functions, I decided to try finally build a solution for Nintex Workflows for Office 365, where I have a single repository of workflows’ definitions, and from here I am able to publish them across the site, to different libraries or lists. Previously I was only able to do it using PowerShell or tools like Postman or Fiddler. However I wanted to have a single workflow that does all of the magic for me.
When you want to call methods or objects in C# code, you must declare them with “using” statement. But what if the package is not available? Then you must first make a reference to it. When programming in local environment it just require to upload needed dlls into the project. But what when you are not using desktop IDE, but through the Azure console?
Although it has been repeatedly said that the history of InfoPath is over, for many companies still building workflows’ forms using InfoPath is as obvious as using Excel. However, when doing that in Office 365 and SharePoint Online the product’s boundaries are really visible and are becoming a real pain.
I’ve been struggling some time ago with an issue related to the workflow’s instance size (here), what was directly related to the size of the InfoPath form together with attached files. The obvious solution I was thinking then was moving those attachments away from the form, into a dedicated SharePoint library, but I wasn’t able to do that easily mainly because of the algorithm that is used in InfoPath to handle file attachments.
As we all have heard, during the Ignite, Microsoft was planning a lot of cool new features to be rolled out for Office 365 as a whole but even more, and even more interesting, for the connected environment of SharePoint Online, Flow and PowerApps. Post describes the features that I was able to already see and use.
Small disclaimer! Most of these features are still available only for the tenants in First Release mode or even in private preview 🙂
The article is a continuation of the post describing creation of a simple newsletter using SharePoint Designer 2013, written here and the other one using Nintex Workflow for Office 365, written here. This time I would like to show, how the similar solution can be made using Microsoft Flow and SharePoint Online.
I was working on my newsletter’s solution, aimed to automatically send prepared messages hosted in my SharePoint. Naturally, newsletters often contain images. Lots of them frankly speaking. The most straightforward approach was to insert them as a URL to the physical file stored in SharePoint (described here). However, in that approach, if a recipient has no access to the site, where the file is hosted or is not yet logged in, the images won’t show up.
I have recently found myself in a situation, when after creation of a new, Modern Site (it was a modern Team Site) my account, even though that was set to be a SharePoint Administrator (even a tenant one :)) and a Site Collection Administrator wasn’t able to see links to any galleries in the Site Collection settings. Moreover, when accessing them using a direct links and then trying to ex. add a new solution, I was being told, that I have no permissions for that operation.