Having upgraded to latest release of Nintex Forms 2013 we see synchronization issues that cause some of the lookup controls to be evaluated later than async formulae try to use their values (Support case under way with mitchellslater).
Solved! Go to Solution.
You could use this following function to refresh all calculations :
If you want to target a specific control, you could also use this one :
Tried that, but no queries followed
Update: the trick was to find and update the hidden input that actually had subscribers to that event, not the one that was obvious and had no subscribers.
I'm trying to come up with a remedy in a situation where forms that worked suddenly work for some items and not for others. A control displaying (control mode=diplay) a pre-populated lookup value that should filter a lookup query suddenly gets overlooked by query builder and the lookup function looks for <IsNull><FieldRef Name='ID' /></IsNull> which is nonsense by itself. Mitchell almost reproduced this but in his case that lookup function is reevaluated, unlike in our case. I need to force this invalidation and reevaluation without major rebuild of a complex set of form templates.
Trish, it wasn't the code actually, it was the form design: several controls of similar meaning, some of them hidden and playing a greater role than those readily available in the UI.