We have a workflow attached on a subweb list containing two FlexiTasks with Nintex Forms. The Forms on this tasks contains lookup fields targeting lists on the SiteCollection.
If we want to deploy the workflow from our dev environment to the integration environment (Export/Import) we cannot publish because the lookup field are loosing the connection to the SiteCollection (yellow warning mark on boith flexi tasks) . We always have to delete and recreate those lookup fields... There is also a Nintex Request Review Task containing the same lookup fields. This task is working without any issues...?
The Name of the site collection and subweb is the same in both environments
Is there a solution to this?
Solved! Go to Solution.
Hi Roman, if i understand well the lookup fields depends on list items ID when you publish for to different site collection there are other list with other list ID's. And a lookup fields always need to be reattached to a new list. What i see you could use is Enterprise feature lookup to sql or webservice. This should work with your functionality.
It is one of the bigest SP problems that there is no dev to prod export functionalities like in SAP or other ERP systems.
The problem could be somewhere in flexi task black box functionality. A request data task is just a task with custom fields, where flexi has a lot of internal logic, like permissions, delegation.
Maybe Nintex support could help and give more detailed answer to this question.
Just had a call with Nintex Support. This is a normal behaviour of Nintex Workflows. They recommend to change the ID’s (WebID, SiteID, AppID) from the source Site to the Target. I will see how we can manage this on our end and post my solution asap.
We just managed to replace the Ids using a powershell script and PnP powershell commands. All I do for the moment is replace the ListID's with a replacment string containing the list name in the nwf files and put them back on the target environment.
somewhat creepy but it works for me...
I have two powershell scripts using pnp Powershell provisioning (OfficeDev/PnP-PowerShell · GitHub). The first script we run from the source system to replace the GUID's with the list name. The second script does the opposite on the target system. The Variables script is for configuration.
Hope this helps...