What is the record field property that should be set to validate dates for <> 30 days?
-
Setting %Date as constant
-
Required
-
Specifying Default using Record and Field values
-
Reasonable date
-
Validate date
The 'Reasonable date' property is specifically designed to validate date fields against logical date ranges, including ensuring dates are not too far in the past or future. This property can be configured to validate that dates fall within a specific range like the last 30 days, preventing invalid or unreasonable date entries.
To answer this question, we need to understand the different record field properties that can be set to validate dates.
Option A) Setting %Date as constant - This option is incorrect because setting %Date as a constant does not validate dates for less than or greater than 30 days. It only sets a constant value for the %Date field.
Option B) Required - This option is incorrect because setting a field as required does not specifically validate dates for less than or greater than 30 days. It only ensures that a value is entered for the field.
Option C) Specifying Default using Record and Field values - This option is incorrect because specifying a default value using record and field values does not validate dates for less than or greater than 30 days. It only sets a default value for the field.
Option D) Reasonable date - This option is correct. The "Reasonable date" property can be set to validate dates for less than or greater than 30 days. It allows you to define a range of reasonable dates and ensures that the entered date falls within that range.
Option E) Validate date - This option is incorrect because the "Validate date" property only validates the format of the entered date, such as ensuring that it is in the correct format (e.g., mm/dd/yyyy).
The correct answer is D) Reasonable date. This option is correct because it allows you to validate dates for less than or greater than 30 days by defining a range of reasonable dates.