cancel
Showing results for 
Search instead for 
Did you mean: 
Nintex Newbie

Form Rules do not work as expected

Nintex for Office 365.  Form for a Sharepoint Online List. Trying to get Form Rules to work.  

 

I am trying to use Form Rules to control the enabled (Read Only) state of various form controls.  This flat out does not work when I try to include in the rule the value of a variable is set based on a lookup function.  The value of the variable is looked up from another list.  If the value of the variable equals a certain value, then the rule should apply.  

 

The rule works just fine when I set the variable to a literal value of "true".  However, as soon as I switch to a variable that is looked up from another list, the rule will not work, even though the value of this variable is also confirmed to be "true" (because I am displaying it on the list).  

 

This makes me wonder whether the setting of the variable value from the list lookup is happening asynchronously in relation to the the execution of the rule, such that the variable is not getting set when the rule executes.  

 

Is that the case?

Any input / suggestions?  

Labels: (1)
0 Kudos
Reply
8 Replies
Highlighted
Nintex Employee
Nintex Employee

Re: Form Rules do not work as expected

Hi,

I have tested this functionality based on your description and it worked as expected. What browser are you using?
0 Kudos
Reply
Highlighted
Nintex Newbie

Re: Form Rules do not work as expected

I am using Chrome Version 78.0.3904.108.

0 Kudos
Reply
Highlighted
Nintex Newbie

Re: Form Rules do not work as expected

I'll add a little more clarification:

I am looking up a value from a reference list.  The http request returns just fine, returing a boolean false in the json data.  Because the Nintext lookup function only returns a string value, my text variable gets assigned a string value of "false".  For debugging, I'm displaying this on the form in a label control to verify that I'm getting the correct value, and I am.  

The rule is set such that if this variable has a value equal to "false", then a field on my control will be disabled (readonly = true). 

 The control only ends up being disabled if I substitute in the same rule a "dummy" text variable that I assign a literal value of "false", rather than using the lookup for the assignment.  

As soon as I switch back to the actual variable that is assigned based on the lookup, the rule does not work (the control is not disabled), even though it has exactly the same value of "false".  

0 Kudos
Reply
Highlighted
Nintex Newbie

Re: Form Rules do not work as expected

I found extracting the value from a List Lookup control takes some extra logic because parseLookup with true doesn't handle the unselected case as expected. (I have a case about this).

In the meantime this works for me:
1) create a text form variable, say called SiteLookupValue, that extracts the selected value from a ListLookup control. The formula/value is:
ifElse(contains(substring(Form.SiteLookup,2,1),"#")
,substring(Form.SiteLookup,3,255),
ifElse(contains(substring(Form.SiteLookup,3,1),"#")
,substring(Form.SiteLookup,4,255)
,substring(Form.SiteLookup,5,255)
)
)
2) create a rule as follows:
if SiteLookupValue equals YourSpecificValue
then YourControl Read-only Yes
else YourControl Read-only No
0 Kudos
Reply
Highlighted
Nintex Newbie

Re: Form Rules do not work as expected

So, I'm not "extracting the value from a List Lookup Control".  

I have a variable that is assigned a value using the lookup function to get the value from a Sharepoint List.  Presumably, this list lookup (http request to Sharepoint API and the server response) and value assignment happens on page / form load.  

 

The value of this variable is as expected, and is displayed on the form for debugging, but the behavior of the target control for the rule appears to indicate that the variable might not be set at the time the rule is evaluated.  

0 Kudos
Reply
Highlighted
Nintex Newbie

Re: Form Rules do not work as expected

Hi @v-tmasenko,

Any update on your case about this issue?

 

I'm experiencing this problem as well and it's kinda hurting us for a PoC we're trying to show a customer.

 

I tried your workaround (which basically takes the text after the #, as long as you don't have more than 99 entries in the lookup list), but this also gives me no result when putting it in a variable and then mapping the variable to another field value.

image.png

image.png

 

My requirement is so simple; I just want the value on the input form to match an entry on another SharePoint list, but it look like I'll have to go the not-so-user-friendly way of doing stuff in workflow after the user manually typed in the value Smiley Frustrated

0 Kudos
Reply
Highlighted
Nintex Newbie

Re: Form Rules do not work as expected

Never mind; the parseLookup() actually works, just not in "Preview" when you're designing the form:

image.png

0 Kudos
Reply
Highlighted
Nintex Newbie

Re: Form Rules do not work as expected

Yes it was fixed in one of the recent updates.

So the work-around I posted is redundant.

0 Kudos
Reply