cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Nintex Workflow - create list item setting Lookup Field

I have been implementing a workflow on a Parent Site List A. The workflow is then instructed to create a list item on an existing List B on a subsite. I have been able to create an item on List B using a field from List A, and fill in a text field successfully, however I have not been able to create an item in List B which fills in the lookup field (lookup to a Site Column).

With a lot of googling and also reading on the Nintex community site, I have not been able to resolve the issue. I was hoping you might be able to assist.

In my investigation I have used the following reference documentation:

Nintex Create List: http://help.nintex.com/en-US/O365/Default.htm#O365WorkFlow/Workflow Actions - INT/Office 365 Create ...http://help.nintex.com/en-US/O365/Default.htm#O365WorkFlow/Workflow Actions - INT/Office 365 Create ...

Nintex working with Lookups: http://help.nintex.com/en-US/O365/Default.htm#O365WorkFlow/Creating workflows/Lookups.htm?Highlight=...

Below are the core details of the components used in  my implementation – hopefully sufficient explanation to resolve the issue

LIST A (Project Register)


Nintex_create_new_item_1.png

Nintex_create_new_item_2.png

LIST B (Test)

Nintex_create_new_item_3.jpg

Nintex_create_new_item_4.jpg

Nintex Configuration – Create List Item (the Nintex workflow is running on List A)

Nintex_create_new_item_5.jpg

Nintex_create_new_item_6.png


   
Workflow error:

Nintex_create_new_item_7.jpg

I know that the list name is correct because when I only set the Title1 field then the item is created successfully.

I also know that the list field name Link to Project is correct because when I have the following configuration:

Nintex_create_new_item_8.jpg

Workflow error:

Nintex_create_new_item_9.jpg.png

In the first scenario where the value was set to VariableSmiley TonguerojectRegisterLookupItemID (Integer) which is equal to 60, then I get the error Lists does not exist…

If you would be able to offer some insight, advice it would be much appreciated.

Many Thanks,

Duane


 
 
 
 
 
 
 
 
 
 





Labels: (1)
Reply
8 Replies
Not applicable

Re: Nintex Workflow - create list item setting Lookup Field

I have done a test doing the same as in the above post with one difference, move/create List B to the Parent Site (i.e. same site level as List A). In this scenario, the item is created successfully.

In my initial post i was able to create an item in the subsite, setting a text field to a text field from a list in the parent site. However I was not able to create a list item, setting a lookup field (List B), using the ID from the Current Item (List A)

In this post I have confirmed that when List A and List B are on the same site, then I am able to create an item in List B setting the value of a lookup field in B to be the Current Item ID in A.

Is it correct to say that there is a limitation in creating an item a subsite (List B), when setting a lookup field to the ID of the current item in List A? If so, then this is strange that we have the option to select the field item type in List B as a Lookup...

If my hypothesis is correct then what is the best way/alternative to create an item in List B, by setting the Lookup field to the current Item ID of A?

Please assist.

Many Thanks,

Duane

0 Kudos
Reply
lkchiang
Nintex Newbie

Re: Nintex Workflow - create list item setting Lookup Field

Hi Duane Stavropoulos​,

You're right. It's not supported if Type = Lookup is selected.

As we know the configuration in "Office 365 Create List Item or Document Set" action, we are providing the child site URL, but not parent site URL. So it failed to refer and get the lookup value from parent sites

Or you can try to use Type = Integer

0 Kudos
Reply
Not applicable

Re: Nintex Workflow - create list item setting Lookup Field

Thanks for the feedback

I'm Sure that I attempted the suggestion Field LookupFieldName with Type integer, but I cannot confirm this.

I managed to achieve my goal by using a Web Request:

https://sparza.sharepoint.com/sites/retailops/development/‎‏{Current Item:ID}‌/_vti_bin/Lists.asmx

Method (Soap Action): http://schemas.microsoft.com/sharepoint/soap/UpdateListItems

Body:

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>    <UpdateListItems xmlns="http://schemas.microsoft.com/sharepoint/soap/">    

<listName>LinkToProjectRegister</listName>    

<updates>    

<Batch OnError="continue" >                

<Method ID="1" Cmd="New">     

<Field Name="Title">‎‏{Workflow Context:Workflow name}‌</Field>

<Field Name="LinkToProject">‎‏{Current Item:ID}‌</Field>     

</Method>             

</Batch>     

</updates>  

</UpdateListItems>

</soap:Body></soap:Envelope>

Reply
Not applicable

Re: Nintex Workflow - create list item setting Lookup Field

@KuanChiang Lui I was not able to get the desired result with setting the LookUpField on the sub-site to be of type integer and setting this to be the ID of the item running on the ParentList.

0 Kudos
Reply
Not applicable

Re: Nintex Workflow - create list item setting Lookup Field

@KuanChiang Lui, when the internal List name is used then your suggestion works. May I suggest that you update the Nintex documentation to be explicit in the description of how to set this configuration up:http://help.nintex.com/en-US/O365/Default.htm#O365WorkFlow/Workflow Actions - INT/Office 365 Create List Item.htm%3FTocPath%3DNintex%2520Workflow%2520for%2520Office%2520365%7CActions%7COffice%2520365%2520workflow%2520actions%7C_____6

Strangely enough when I set the field Name, then the internal name is not required. So when does one use the internal name?

0 Kudos
Reply
lkchiang
Nintex Newbie

Re: Nintex Workflow - create list item setting Lookup Field

Duane Stavropoulos​,

Thanks for the feedback. that's interesting.

By right, we do not required to provide internal list name because the action gets the list by Title.

Besides, the action is supporting field title and field internal name. If it's failed to find the field by field title, it will find it with field internal name to ensure that the field is exists in the list.

Since the internal data type of lookup is an integer, so we are allow to create the field with correct integer value.

0 Kudos
Reply
Not applicable

Re: Nintex Workflow - create list item setting Lookup Field

Thanks

0 Kudos
Reply
gman
Nintex Newbie

Re: Nintex Workflow - create list item setting Lookup Field

Duane,

A possible simpler option occurred to me while reading your post. Since List A resides on the root site collection, you could then create a Site Lookup Column to that list and the column you want to relate to. The sub-site list will then have access to this site column. If added as a column to List B, you should then be able to set the lookup when creating the item.

Hope this makes sense.

Reply