Having issues with some form validations after updating Nintex version.
Date validation is done through JS
function ValidateHotel() {
var validateHotelPreference = true; var validateHotelCheckinDate = true; var validateHotelCheckoutDate = true; var validateHotelEstimateIsNumber = true; var invalidFields = []; var validFields = [];
Even if date is not null still form can not be submitted
Best answer by MegaJerk
By the way, the best way to maybe approach this is just open up your console to see if your code is throwing any errors there. Since it's both impossible for us to know what your custom code is, and what changes Nintex has made to their code-base, that would be where I would start looking (as I have also been in your shoes).
If that doesn't produce any leads, the next question I would ask is, "what do I want to happen that is no longer happening" and then go and find the code in question where that *thing* is supposed to happen. You can always add the "debugger;" line to your code (see: https://javascript.info/debugging-chrome#debugger-command) so that when it's reached (and the console is open) the debugger will catch it and pause execution so that you can proceed line by line to see what's going on.
If you want further help, say something, but this is the double edged blade of using custom code to do everything! I highly recommend moving your validation code out and away from custom stuff and into the Rule system unless there is some particular thing that you're trying to do (with validation) that just doesn't seem doable in the normal rule system.
As a person who has modified the built in Rule system extensively, I can vouch that it's pretty darned good at doing custom stuff, so long as you're willing to learn a little bit about how it works.
let me know if there is anything else I can help with.
InvokingValidateHotel() through JS Variable. All validations are in a js file. This is a Travel Request , so we have several other validations similar to Hotel for Car, Hotel, Train etc
Issue started happening after CU July updates and Nintex version update to 4.6.2.0
By the way, the best way to maybe approach this is just open up your console to see if your code is throwing any errors there. Since it's both impossible for us to know what your custom code is, and what changes Nintex has made to their code-base, that would be where I would start looking (as I have also been in your shoes).
If that doesn't produce any leads, the next question I would ask is, "what do I want to happen that is no longer happening" and then go and find the code in question where that *thing* is supposed to happen. You can always add the "debugger;" line to your code (see: https://javascript.info/debugging-chrome#debugger-command) so that when it's reached (and the console is open) the debugger will catch it and pause execution so that you can proceed line by line to see what's going on.
If you want further help, say something, but this is the double edged blade of using custom code to do everything! I highly recommend moving your validation code out and away from custom stuff and into the Rule system unless there is some particular thing that you're trying to do (with validation) that just doesn't seem doable in the normal rule system.
As a person who has modified the built in Rule system extensively, I can vouch that it's pretty darned good at doing custom stuff, so long as you're willing to learn a little bit about how it works.
let me know if there is anything else I can help with.
Your reply helped me find the issue, analyzing the console led me to the answer. The field was validated not as an empty string but having incorrect data. Thank you!!! So at the end it was not an issue with the new Nintex version , I had so many other issues after the version upgrade so right away I thought it was related.
