If after you set field and go to field, are you committing the data? If so that would trigger the field validation. But I think If your tabbing through the fields, you should not get prompted after every field unless your clicking outside a field. If validation is checked for not empty.I think you may want to forget field validation and use an OnRecordCommit script trigger.
The field set I mention above has nothing to do with this particular issue. It is setting a different field which has another function altogether. I was just mentioning it so you could see the script steps in case there was a suggestion to add something in there. On the layout I have Last Name, First Name, Street, Town, County, DOB. The tab is set to the order they are on the layout. So if I had validation for DOB to be not empty, as soon as the user clicked the button on another layout which runs the script above to add a new client the first thing it does is prompt to fill in the DOB. Then if you close it and start from the beginning filling in name first as you leave each field it keeps popping up. I need it to just check when you are done filling in the details and go to move on to another layout, much the way websites do with required fields, they don't prompt you at each field entry, they just prompt you when you click submit and say a field is missing.
That's fair enough, but as I said I was/am getting the prompt after every field the way I had it set up despite you thinking I shouldn't.
I will set up the script anyway that works best or as suggested but as I mentioned I was hoping to get some help writing the script correctly as what I tried myself did not work either. I'm very new to script writing so no doubt I'm missing something very simple or obvious. I'd be very appreciative of any help I can get because I myself am just going in circles. I don't follow what you mean by on record commit script trigger.
I apologise if I sound silly...I'm still learning.
Dont apologize....I'm a newbie too...still learning. And I have asked many questions in the last year. It may be helpful if you put up a screen shot of your validation tab, and the actual script. A few more thoughts/questions:
It seems to me you may have a script trigger firing when you exit each field, otherwise you shouldnt have your problem until you try to commit the record (click outside a field, try to use a script, or change layouts).
"So if I had validation for DOB to be not empty, as soon as the user clicked the button on another layout which runs the script above to add a new client the first thing it does is prompt to fill in the DOB. Then if you close it and start from the beginning filling in name first as you leave each field it keeps popping up. I need it to just check when you are done filling in the details and go to move on to another layout..."
Whenever you leave a layout the record commits, either automatically, prompting the validation, or you get a validation message "do you wish to save...., then if you click "save", the validation kicks in.
If it's not working this way, I go back to what parameters are in your validation tab?
I have a couple of individual fields where there are script triggers to track if information in them was changed, DOB does happen to be one of them. It basically checks to see if the info at field entry is the same at field exit if not it places what it was and what it was changed to in an audit table I have along with the date it was changed and by whom.
And yes that prompt happens when users click on say a blank part of the field too but I KNOW they will do this a lot haha. I have users of all computer skill levels using the system so there are those that will be proficient and zoom through the fields by tabbing and others that as you know how it can be will click the wrong spot sometimes.
This is kind of why I thought a script on the layout exit checking to see if the DOB field was blank would work as I thought the layout exit would be when they try to leave the page, not just a field on the page.
1 of 1 people found this helpful
One trick is to place an empty, invisible web viewer object on your layout, located behind all the fields and buttons and sized to cover the entire body of your layout. This object will intercept mouse clicks on the layout back ground to keep that action from comitting the record prematurely.