onCustomValidation not resolving promises

Ask the community
,
1

Can anyone confirm whether returning a promise works in onCustomValidation or whether I’m doing it incorrectly? This prevents me from validating the form input using a database call or backend function.

Here is some sample code that executes because the console log “Invite code is not valid” is printed out. However, the reject function does not update the validation state of the input field.

$w("#input5").onCustomValidation((value, reject) => {

		console.log("Validating code " + value);

		return wixData.query("InviteCodes")

		.eq("inviteCode", value)

		.find()

		.then((results) => {

			if(results.length === 0) {

				reject("Invite code is not valid");

				console.log("Invite code is not valid");

			}

		});

	});

});

Similar code written synchronously works fine and the field shows with a red border. However, this is not ideal because I need to preload sensitive data to the client instead of validating on the backend.

$w("#input5").onCustomValidation((value, reject) => {

		console.log("Validating code " + value);

		codes.forEach(code => {

                    if (code.inviteCode === value) {

                        return;

                    }

                })

                reject("Unknown invite code");

	});
2

I can’t get a query inside onCustomValidation to work either. Here is my code:

if (value){
$w(“#clinicsDs”).setFilter(wixData.filter()
.eq(“clinicId”, value)
)
.then(results => {
if ($w(“#clinicsDs”).getTotalCount() != 1) {
reject("Invalid Clinic Id. ");
}
})
}

Have you had any luck getting this to work?

3

I found a round about way to get it to work. I created an onChange event handler for the input that needs to be validated against the dataset. In that event handler, I first disable the “Sign Up” button, then perform the filter. If the filter result is a single row, the entered value is valid and I re-enable the button.
I also have an onCustomValidation event handler but it is really a safety net as it tests whether the “Sign Up” button is enabled AND the dataset count is 1. This condition should never be false, but if somehow it is, the validation is rejected.
It isn’t elegant by any means but it does ensure that the member can’t register with an invalid value and that is what really counts.
Hope this helps.