Skip to main content

I will start off saying that using the lookup() function within a calculated field will not work in this scenario. I require the ability to complete the form using Nintex mobile, unfortunately the app does not support lookup() functionality for whatever reason. I've got SharePoint 2010 on prem.

Here is the desired outcome, but I need help to get it working on mobile devices:

Desired Outcome

Currently, the first drop down menu is a list lookup which gives the option to select an existing report to edit. Once a report has been selected, the second section, "Selected QC Details" auto-populates based on the report number that was previously chosen. This works beautifully and smoothly on the desktop!

The idea I have is to get around the lookup() function by using some JavaScript (or any other idea you may have). I searched online and found an article by jeremy.jayaraj titledHow to query a SharePoint list from another list in Nintex Forms for O365. This has the right idea, but I was not able to replicate the desired results. I do not feel comfortable enough with my experience to get this working correctly on the form.

In the end, I essentially need the script to create variables that I can then use to place in the calculated field. The variables I will need are: Created, Status, and Observation. Any assistance would greatly welcomed!

javascript is not supported on nintex mobile either.

I'm affraid of you will not be able to design it this exact way on mobile.

but considering an approach I've proposed here https://community.nintex.com/message/68108-how-do-i-create-a-form-to-view-from-and-update-to-another-list-on-the-same-si… , you might be able to achieve it to some extent.

if you created a task for each QC report, users could open respective task on mobile device to edit source item. since each report would have its own task no lookups would be needed, since al the data would be fetched from current item.


Hi Marian, I will look into assigning tasks. I have not used them before but from what it sounds like, it will be my best option until Nintex updates the app to support lookup() functionality.


Reply