Nintex forms version 2.8.1.0 - issue with lookup change event

  • 23 November 2015
  • 3 replies
  • 2 views
G
Badge +4

we recently updated to Nintex forms version 2.8.1.0. Earlier we were on Nintex forms version 2.4.1.0. we did this upgrade on the dev environment first to check if the existing functionality is working or not. This was as suggested by Nintex tech specialist.

When I tested our very first application I found couple of issues,

 

1) Lookup control does not work properly when you specify a view name to get the values.

2) This is the most critical one. when the nintex form loads it fires all the javascript behind the form. for. e.g. one of the javascript should have executed on lookup change,

lookup1.change(function () {

lookup2.change(function () {

 

These functions are getting executed even though i have not selected anything from lookup1 and lookup2.

It looks like upgrading Nintex is kind of a big pain.

 

does anyone have any clues about the above issues ?

3 replies

G
Badge +4

Thanks Stephen.

I would like to use the new javascript api's if available. Do you know how can i handle the lookup control events ?

Also i am not using a people picker control. its a simple list lookup / dropdown

G
Badge +4

Hi Stephen,

Thanks. those scripts were helpful. But i guess we still need to put a condition to make sure that the event is not getting fired when first time the form load all the controls. you have to still put a condition to check if the value is blank and e.originalEvent==undefined. I was looking for something where Nintex takes cares of this internally instead of us specifying that condition.

WF$('#' + ddlStaff).on('change', function (e) {

if(lookupvalue != "")

{

if (e.originalEvent != undefined) {

}

I have opened a support ticket with Nintex to see if they can put a fix or provide some alternative.

G
Badge +4

I have also raised this with Nintex support. They said that this is a bug and should be fixed in the next release. I hope we have a better way to handle these events in the next version.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings