Prevent Duplicate Value On Entry

vinsnash

The first field in the main form is an SSN. What rule can I concoct that will validate the SSN does not already exist in the Object and report an error at the point when the field is filled and focus goes to the next field?

I've tried several variations of "IF Exists" with "THIS" and "THAT" to no avail. I've marked the rule as "Dynamic" also and given it a priority of 1. I'm sure there must be a solution.

The problem is that the rule only reports an error after the rest of the fields have been entered and the attempt to "CREATE" is made. This wastes an inordinate amount of time and it is the number one complaint I have from users.

Vins Nash

vinsnash

Forgot to set the "Notify" switch.

tford

So, can you share your final solution?

tford

What "Notify" switch are you talking about?

vinsnash

The "Notify me when a reply is posted" check box.

I am unable to make the rule execute until the create button is clicked on the main form.

The rule then checks for a duplicate and reports the error. Meanwhile the user has filled a screen with data from an already entered instance.

I don't have a solution. I just can't imagine there isn't one. Immediate confirmation of a duplicate key is ubiquitous in any system that must keep unique records.

Vins

asawyer13

Tom,
Do you know if this can be done?
Alan

pbrad

Hi Vins,
I agree that sometimes it would be nice to be able to validate the uniqueness of a field value as soon as that value has been entered rather than have to wait to create the object only to find out that somebody else had already created it.

There doesn't seem to be an easy way to do this yet but as a workaround you could consider the following approach:

1.Create a non persisted object with an SSN field in it.

Create a process similar to:
Rule1->ENTER NEW NonPersistedObject
Rule2->if EXISTS Object WHERE(Object.SSN=NonPersistedObject.SSN Then
REPORT ERROR 'An Object exists for this SSN already'
Rule3-> ENTER NEW Object WITH Object.SSN=NonPersistedObject.SSN

Now, just call the process to start the job of entering your Object. If the SSN exists, you won't get past the Error but if it doesn't exist, you can proceed with the entering of the Object.
Cheers,
Pete

tford

Perfect solution Pete! I was thinking of writing something similar.

Tom

vinsnash

One for the "Dummies Book"!

We old programmers are used to adding 'non persistent' fields to data entry forms just for user decisions on the fly. I don't recall what we called them but 'persistent' wasn't in any jargon I remember. I remember using such to trigger 'events' in special situations.

Vins Nash

pbrad

Hi,
Non persisted objects are extremely powerful and useful for a wide variety of tasks. Essentially they perform the role of complex, programmable variables that can be global in nature. You can keep them in context as long as you need them and can 'park' them if need be, in an accessible persisted object like the LoggedInSystemUser or System Settings. (Tom Ford is the master of this) A good rule of thumb is that if you ever hit a roadblock, consider NP Objects as part of a potential solution.

One of the more difficult aspects of learning AwareIM is that you have to throw all previous programming methodologies out the window and embrace the AwareIM paradigm. In that respect, previous programming experience can sometimes be a negative factor. A logical mind is a far more valuable asset.

Let me know if the suggested approach doesn't work for you and we can figure something else out.

cheers,
Pete