Have you ever been struggling with a lack of the possibility to clear a number, person or lookup column using PowerApps? Well, I recently found myself in a situation, where I needed to be able to clear such columns in my application, but found out, that this is not possible (maybe not yet).
Building an intranet using modern SharePoint I was asked by a customer, if this is possible to show information from their facebook @workplace portal. I started digging and reading the documentation only to realize, that no matter if I were using modern or classic approach, still there are no ready-to-use scripts from facebook, allowing to copy-paste and then be able to display ex. information from Newsfeed.
This may seem trivial, but if you want to create a Flow, that is parameterized, where a name of a group and list of members is passed as the request parameters then it turns out it is not that straightforward.
In Microsoft Flow there is a set of actions, that allow to work with Office 365 Groups. There is also one dedicated to adding new members (only “Members”. There is no way currently to add “Owners”).
Recently my customer asked me to create a dashboard, to monitor completion of tasks in a workflow. The idea was to highlight completed, on track and overdue tasks with different colors. First I thought about using SharePoint list with Modern Experience, and column formatting. But then I was asked, not only to highlight rows for tasks, but also their grouping header – as there were many tasks created per each group of tasks and the customer wanted to see status of a whole group ad-hoc, without a need to drill down.
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 🙂