Nintex Connect

We recently restored from our Production environment to a Test environment. The Manage User Defined Actions page shows no items, however, when I attempt to import a UDA, it states that a UDA with that name already exists.

Workflows that use the UDAs execute, but when I attempt to edit the workflows, the UDAs already in the workflow indicate that they don't exist with the message "The User Defined Action is not available. It may have been moved or deleted."

How do we get these UDAs to be available?

Thank you.

Hi Jim,

UDAs are stored in the NW database.

Please open it up using SQL Management Studio and find the table "UserDefinedActions".  Each UDA will have it's own record there and you'll find the Site/Web IDs associated with it.

Check to see if the IDs match the IDs of you Site Collection ID (Site ID) and your Sites ID (Web ID).

If you're prod/test environments aren't clones of each other, the IDs will be different and that is why the UDAs aren't showing up and new ones with the same name fail to publish.  The UDAs with those names exist in the DB but the sites don't exist.

We have SharePoint 2010 with Project Server 2010. We migrated the Project Server Databases and the Content database for Project Server to our TEST environment, but we didn't migrate the NW Database.

We may have problems copying the NW database from PROD to TEST because it impacts a much broader set of users (beyond Project Server's Site Collection). Is there a method to migrate just the UDAs that we want from one to the other?

How can we remove the entries for the UDAs in TEST if they are in the NW database?

Thank you.

Hi Jim,

I'd open the DB  in SQL Management Studio, find the table named "UserDefinedActions" and remove them from there.  Take a backup of the DB first if you haven't already.

Then perform an IISRESET and you should now be able to create the UDAs.

we've subsequently restored the production NW database to the test environment and attached it to that instance, but are still seeing the same result.

Are we going to have to delete the UDA's from the database?

Hi Jim,

Yeah, I think that's your only option at this stage.

The fact is, that the UDAs are linked to a specific site or site collection based on the ID that is stored in the DB.

If those site/site collections are not on the current farm, that's where your issue is stemming from.

Manually removing them from the DB would be the way to solve this, so that you can create UDAs or import them.