SharePoint Online + Nintex Workflow: Add a List Column Link to Edit Document Set Form

NOTE: This can be added as separate list WF that starts on item creation or as part of another list WF that starts on item creation.

Filter out Retweets in a Microsoft Power Automate Flow

The Requirement

Create a flow within Power Automate to automatically retweet posts from a specific Twitter account. Only original posts should be retweeted—i.e. exclude posts that are retweets.

ProcessFest 2019 – Implementing Scalable Solutions with Nintex Workflow and Forms

In case you weren’t able to join us at the Nintex ProcessFest Training Conference a few weeks ago, you can check out the recording from my breakout session on the Abel Solutions website.

My breakout session, titled “Implementing Scalable Solutions with Nintex Workflow and Forms”, walks you through a client case study with a large utility industry customer.

Query Cross Site Collection with Nintex

Sometimes the data that you need for your business process lives in a separate site or site collection than the one where you are building your Nintex Workflow. Fear not! You don’t have to get up to your neck in the CAML Editor of the Query List action to extend the functionality. Allow me to show you how!

Update Managed Metadata (MMD) column with Nintex Workflow

When you search the web for “nintex update managed metadata field” you will find many posts with potential solutions to this challenge. However, you may also find that all of these posts only get you a part of the way there. So, this post is intended to aggregate all of the great information that’s already out there, but hopefully make it simpler for you to combine it all together into one cohesive solution.

Capture Workflow Approval History on SharePoint Items

This post walks you through the steps I use to surface key Workflow History details onto a SharePoint list item. So, rather than having to navigate down into the Nintex Workflow History page to see who has Reviewed/Approved/Rejected/Completed an item and any associated comments, all of those details are more readily available on the Nintex form for the SharePoint item itself. This is also a good solution to make sure that these details are not lost with the workflow history when recommended database cleanup actions are performed—automatic, scheduled, or otherwise.

Can’t Delete SharePoint Online Site

This one’s a quick one…

We got a call from a client recently who was running into an error when attempting to delete a site from their SharePoint Online environment. The error message referenced “Sites that have subsites or certain apps can’t be deleted. Please try again after deleting all subsites and removing the apps” (see screenshot below).

Nintex xchange Conference Recap

Last month I was able to attend the 3rd annual Nintex xchange Customer and Partner conference in sunny San Diego, CA. The conference focuses on accelerating business with process automation and this year’s theme was all about ushering in a new era of Intelligent Process Automation. Over the course of three days, the conference included three stellar keynote presentations and about 40 breakout sessions. The conference also offered tons of opportunities to network with Nintex staff, other partners, and customers; and there was never a shortage of happy hours 😉

If you weren’t able to attend this year, have no fear!

Allow Attachments on NWC Web Form

I had a requirement from a client recently for an anonymous form that would allow attachments and then push all data captured (including attachments) into SharePoint Online. My colleagues tried several non-Nintex solutions to no avail, because there seems to be a limitation with allowing attachments on anonymous SharePoint forms.

Nintex Workflow Cloud (NWC) to the rescue!

Replace a Stubborn InfoPath Form with a Nintex Form

I am working with a client on converting all of their old InfoPath forms into Nintex Forms and recently ran into an odd issue. On the list that had an InfoPath form, I created a new Nintex form and published the Nintex form. I assumed that the Nintex form would take over and appear as the list item form after publish. However, this was not the case. Instead, the InfoPath form persisted.