Hey Vraj,

What happens if you use the “Error Occurred” condition in the server rule? Does that pick up the server error?

Cheers,

Ernie

Hi Vraj,

May I know if you are refering to modifying the error messages in K2 ?

If so you might want to checkout the link below 

https://nintex.uservoice.com/forums/932680-k2-cloud/suggestions/42432904-custom-error-messages

The link provided is a forum wherein you can log a new feature request or vote for other

user's request so that they can be considered for future updates.

Should you feel that this post is of use and or an accurate solution to the raised question, I kindly encourage you to mark it as such 
using the 'Best Answer', 'Like' andor ‘Me Too’ options.

Cheers,
Kate

K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member.
 

Hey Kate,

That’s not quite the same issue that Vraj is having. His issue pertains to the “When the Form is in Error” event only picking up client-side errors, and not server-side errors when using server side rules.

I think it’s a bug, rather than a new feature request.

Cheers,

Ernie

Hello @vraj,

As a quick solution (you can also call it dirty solution), what i can think of is to play with hidden data label as below

When the server loads the form

Rule 1: Transfer data - SET IsErrorOccured datalabel = 1

--- Configure the other logic--

Rule N (Last one) : Transfer Data - SET IsErrorOccured datalabel = 0

and On the event Form is initializing,

if IsErrorOccured datalabel = 1 which means some error occured while executing server side rule.

We can check the value of IsErrorOccured datalabel and then show the user the custom error message.

Regards,

Divya Raj