How to prevent records from being created/updated under certain cases.

[emyrold]

We have a custom table where I have written (what I thought was a simple) BR to prevent a record from being created if:

- for every field_01 + field_02 combination, there needs to be a unique field_03 value.

e.g. field_01 = appName, field_02 = environment and field_03 = profileName

There should always be only one profileName for every appName and environment combination.

The table has many other columns per record, but these are the key fields.

The issue I have, is my (before) BR (with both insert and update checked) works when I create new records.   And when I update an existing record where I change profileName frome "Joe" to "Sally" (assuming Sally does not already exist).   However, if I now go and change any other value of other fields on the record, it prevents the update because profileName already exists.   The only work-a-round for now until I fix this logic is that when I want to change one of the other field values, I have to temporarily change profileName to something unique while I make the save and then again rename it back to the original profileName again.

So is there a way to do this in one BR or do I need two, one for insert and one for update?

var tla = current.u_tla;
var env = current.u_environment;
var profile = current.u_profile;

var hostGR = new GlideRecord('u_cdm_host_migration');
hostGR.addQuery('u_tla', tla);
hostGR.addQuery('u_environment', env);
hostGR.addQuery('u_profile', profile);
hostGR.query();

if (hostGR.next()) {
   current.u_profile.setError('Profile Name: ' +profile+ ' already exists for this TLA and Environment');
   current.setAbortAction(true);
}

[Tanaji Patil]

Thanks Erik

[Deepak Ingale1]

Nicely done