In 2026 Microsoft will turn off SharePoint add-ons and workflows. This will put many Nintex customers on the crossroad – whether to move to Nintex Automation Cloud or to Power Platform.
In this short post I will help you to build your Nintex for Office 365 workflow that will allow you to copy attachments that were added to a task to a related list item attachments. The list item is of course the one around which the whole workflow is running.
I was seeing this kind of error in Nintex for Office 365 workflows for some time, but actually never had enough determination to check what is the root cause. However when customer started asking, I started digging.
This is a quick tip post. I am facing this problem myself quite often when working with Nintex for Office 365, especially in “Classic forms”. Sometimes, when you click the “preview” icon, the dialog window pops up, covers the designer with an overlay and… freezes. How to solve it?
It’s been quite a long time since I last wrote anything around Nintex platform. Recently however I was involved in my first real project around Nintex RPA (formerly known as Foxtrot, RPA tool in Nintex suite, read its review here). One of the challenges I faced was how to get data out of a repeating section…
On March 4, Nintex announced that it has finalized acquisition of the EnableSoft company. The company behind the Foxtrot suite. Starting then RPA (Roboting Process Automation) software became part of Nintex products, somehow completing the gap between business processes in the cloud and those being done on users’ computers “locally”.
In my daily work over business processes in Office 365, specifically in SharePoint Online, one thing annoys me the most – namely the lack of mechanisms to inform me that the workflow has hung up – that it is in a “Suspended” state.
The solution for that issue is not provided by Microsoft or Nintex – the company with which products I have been working for a quite long time. There are only workarounds, but they are inadequate, and I wanted to be able to react proactively and not reactively to any flow suspension event.
Requirement where a designer has create a workflow assigning multiple parallel tasks to multiple parallel groups of approvers is complex.
Basically, Nintex offers us two approaches: either assign task to a group and wait for the first response or to wait for all responses. But what when we need to have multiple groups assigned a task in parallel?
This post is a “how to” tutorial, showing how can a data from SQL Server table be loaded into a “Repeating section” control in Nintex Forms. Needless to say, having that data inside the control allows then to manipulate it and treat each row as a single record, thanks to the possibility of saving contents of the control as XML.
Ever wondered how to display SQL table inside your Nintex Form? Indeed, there is the “SQL Request” action, but it only allows you to show data from database as a dropdown, list of options, etc… and always – just a single column.