I used a list lookup field in Nintex Forms. The input formworks with cascading lookups, but the fields are not showing in the SharePointlist summary view.
See attached PDF of behavior and context.
Ok, following up.I hope this was what Randy looking as well. Once again, this proves that if you believe strongly and stare at your form for long stretch of hours and pray, the problem resolves itself.
So, the Lookup list returns ID & name and for us to bind and save value in our connected list, we'll have to create a single line of text field and connect the lookup list to the field.
I created a single line of text column in the SharePoint list called:DeptSchoolLookupSelected
Connected the dropdown list lookup to the text field and it retains the lookup list options. Saving the form binds value selected to the column.
Is it pretty? No.
Can I do the same for an approver cascaded by the lookup list dropdown selected by department/school? I don't know. But aleast this mini mystery is solved and we can chug along!
Hope this helps.
From the form designer, click on the drop downs, if the "connected to" input boxes are empty, then they are not connected to the list and will not send the selected values to the list to be visible in the view. In the control settings, can you change the Text Connect To, to the list field?
I think this is the case for you as you mention the drop downs are the list lookup feature in Nintex.
Hi Nintex gurus, I have the same question as Randy's.
Thanks in advance for the help! Emily Billing Jeremy Jaya Raj
Thanks for sharing your solution Swetha!
Exactly how does one remove the 87;# in front of it?? That's the biggest problem with parsing these options from cascading drop downs. The parse action doesn't seem to allow you to remove all text up to a delimiter (in this case the # and including that delimiter as one of the items to be removed). The best i could come up with is a remove text option, but it requires you to know the number of characters you need to remove and since that can be dynamic as well (sometimes its 4 or maybe even 10 characters depending on the count of options in the list if you have a lot) it makes it nearly impossible to effectively use that function. Either way, if i remove the number and ;# then when i go to view it later, it jacks the selection window up because it doesn't know what option to select. heaven forbid the selection option numbers change later down the line too. (The source list adds a new selection option to choice #87 and moves the ACTUAL selection to #88 or something).
I'm trying to create a list of "other" selection items that dynamically change as new items are manually entered by users. So when someone wants to choose "blue" as a color, but its not in the list of selection options, they choose "other" and enter "blue" on the new line. Then the next time another user (or the same one comes back) wants blue, its now in the selection list of options.
The problem is the prefix of the drop down menu is getting in the way. I need it to read when the selection is "other" so i can know that it should add the entered item into the external list called "colors". (It also does some counting and comparison to make sure someone isn't duplicating choices that already exist).
What's a good way to do this? Should I post this outside this as its own question? I didn't know if i should since this seems related to the existing problem for this user. If they could parse out the 87;# it would def make it look better...
have a look at parseLookup() function
This is available within the parse action or is this a nintex forms function? I'm not seeing it in the inline functions list.
it's runtime function
I see that but at what point are runtime functions available in a nintex workflow?
Also looking at the parseLookup option you have there, how would you use it? Even if it was available to me at this instance, how would you use that function to remove everything in front of the letter immediately after the #? Its talking about an "optional bool" I don't see how that filters anything and the first variable is the actual item you want to manipulate...?
I found where you have the formula builder, but that's within a nintex FORM, i'm not working in a form. I need this to parse the value in a WORKFLOW.
It would be far simpler if the "if" action had a "contains exactly" option where i could search for "other" and not fail on "another" as well...
the thread discusses form problem and from your post it was not obvious you're talking about workflow.
it's always better to start new question/thread with new topic/problem then hijack existing one...
especially in the cases when the thread is closed resp. when it is one and half year old.
so please do so.
you can tag me in there and I can look on it, if I find a little time.
please explain as well how do you get lookup value in a form ID;#KEY since it's not so usual in workflows once you correctly approaches to data.
I have same question as Randy's.
I have tried swetha's solution too but no solutions.
I have a list which has 4 lookup columns whose data is not being saved in List.
I think there is something wrong with Nintex Form that i had created.
Because when i tried by creating new nintex form it is working fine with new form.
and even i tried by deleting lookup columns from list and recreated it with other names, that worked for some time but after couple of entries in list again lookup data were not being saved in list.
what controls/Jquery on the form which can cause such issues.
Hmm...That doesn't sound good Soyeb.
Does your 4 lookup column values show when you view the item in display mode?
If yes, then your values is being persisted in the form. To have that saved to the list, you have to create a 'Single line of text' field in your list, corresponding to each of the lookup selection. Just connect the lookup dropdown to the 'single line of text' field.
Not sure what you mean by 'when i tried by creating new nintex form it is working fine with new form'. Are you able to save the values back to your list in the new list/form?
@Swetha : Thank you for reply.
In the form multiple controls were binded with single lookup column so last control value was saved to list item.
Great feedback, thanks for sharing.
I have more pain to add to this. Thanks Swetha Sankaran for your post as it has helped me to an extent, but here is my tale of woe.
I have this exact issue, where a form is using a list lookup to associate a Contact with a Company. I save the form and the data does not appear in the list but remains in the form, how frustrating, but thanks to Swetha Sankaran post I better understand why this is happening, however, my tale continues.
I have a third list that is then performing a cascading lookup on my Contact list. So when a user is creating a Note (this is a mini CRM app) they will select the company they met with and then only contacts who belong to that company will appear. At least that is the theory.
Taking the advice above around connecting the lookup to text fields I have my Lookup control called CompanyChoice (source list - accounts) connected to a field called Company. I then have a second lookup control (source list - contacts) and this is filtered. See below.
Now, I've tried all sorts of approaches to get this to work as this simply results in an empty dropdown list when a company is selected in the Company Choice control.
On my form, I also have a bunch of calculated value controls displaying information about the selected company, to get these to work I created another calculated value control using the parse lookup function (CompanyFriendlyName) against my CompanyChoice field and this works fine. I've tried to use that same CompanyFriendlyName control for my "Filtered by control" selection and it doesn't work either. I'll try to lay out clearly the relationships going on here.
This just doesn't work, whether it's anything to do with the CompanyName being the Title field I don't know.
To get this to work I've had to create a new lookup field in the Contacts list called "companylookup" but the using this field in the form wouldn't retain the value (for the reasons mentioned above, so they have to select Company in the form, then switch to datasheet view to select the same company in my companylookup field to get the lookups and filter to work, which is obviously a terrible experience. So I'm now at the point of creating a workflow when a Company is created or modified to populate the companylookup field with the same company the user selected in "Company" field.
There has to be an easier way than this surely?????
Glad my post helped a bit. I will try to setup a cascaded lookup mockup like the way you have sometime tonight and will see if I can reproduce what you are experiencing and will share any findings.
In the meantime, what has also caught me off-guard is that column names in sharepoint online list at times could be something different than what we named. For instance, my column named 'first name' could be 'xy123' and you can check that by clicking the 'Column' in the 'List Settings' and verify the name of the field in the URL '...List=%7B6AA1B4BA-CA60-4434-93D6-F4146D026075%7D&Field=xy123'
If you see that your name for the lookup is different than what you titled it, try giving the field name in the cascaded filtering section of the form.
Trust this works!
Appreciate your time on this.
Yes, I've thoroughly checked all the columns internal names, I'm on SP 2010 for the record.
I've done some more checks again, and when using a lookup control, no matter what field I'm referencing in the source list filter, it seems to want to only filter against a Lookup formatted value, i.e. ID;#Value
If I parse this lookup to only leave the Value element then the lookup control will not successfully filter, even when the column it is looking up is just a plain text column.
I can understand this happening, at the end of the day, a lookup control is probably going to itself this way. However the confusion comes from using the Lookup runtime function, that does work successfully using a parsed lookup value against a text column.
The "bug" I guess is this. In the Contacts list I am trying to build a relationship to the Accounts list by using a lookup control. Nintex Forms would appear to not allow me to store the company in a lookup column (as discussed earlier) and only allows me to store a string so in my Contacts list I can only store "A Company" instead of "1;#A Company". Then when I try to create a Note I'm attempting to filter "1;#A Company" against "A Company" and as such, not getting any results. I need to have "1;#A Company" as a value in the Contacts list which is why my users are forced to manually select this in datasheet view or I create a workflow that builds this as a string. Either way, it's not very elegant and not how I would expect it to behave.
Retrieving data ...