Skip to main content
Nintex Community Menu Bar

We have a requirement where we want to validate the page and display errors (if any) on the page without saving the model. What would be the best way to achieve this?

Maybe use a UI only formula field for each validation and then display the values of the UI only fields in a text component on button click?


A few things to consider here.



  1. Skuid actually tests all “required” fields before pushing a save request to the server. So though your user is attempting the Save action - if some field is required - the Save Event will never be triggered and the error messages will be displayed.




  2. If your validation is server side (Like Salesforce validation rules) - we have no way to trigger those rules without attempting a Save action. But Salesforce will do a similar thing as what Skuid does above.




  3. We are currently rolling out new client side validation functionatlity for our FORM component. Today you can validate on simple formats, on formulas and on snippets via declarative configuration within the Form Field properties. See image below.

    But for this you need to be on Dubai Update 3 or the new Edinburgh release (which will be GA next week)




Hopefully this helps. Do let us know more specifically what kind of validation you are attempting to enforce. We are continuing to explore these use cases…


Thanks @Skuidward_Tentacles and @Rob_Hatch for your responses. We currently have a lot of fields which are marked as Required on the form level. In case any of the field is not filled in, we want to display the error message of Required on the field on the click of a ‘Validate’ button without saving the model.


@Rob_Hatch I see the ‘Required: True’ in the screenshot that you have provided, is this something that will come out in the next update? We are currently on Dubai Update 3 and have Validations tab on Field but I can’t find this option on my side.


Yes - in the next update we are moving the required property on Form fields to the validation tab, and allowing you to check for requireness with the same trigger that other client side validation rules are connected to. That update should be available on our Releases page in the next few days.


Reply