Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with validation
Search options not deleted
user 53812
Validation checks that the product design satisfies or fits the intended usage (high-level checking), i.e., the software meets the user requirement. This is done through dynamic testing and other forms of review.
0
votes
2
answers
49
views
SP 2013: PreSaveAction validation of Enterprise Keywords column
In my list, I am validating a lot of columns using the PreSaveAction. I have many look-up columns that I want to be required and the OOTB required field way doesn't cut it.
OK - that's cool. I have …
- 23
0
votes
Accepted
SP 2013: PreSaveAction validation of Enterprise Keywords column
So, there's a "hidden" input field associated with it.
For my application, since I only had to worry about one such form field, I was able to validate against:
$("input[id^='TaxKeyword_']").val();
- 23