You are here: Configuration > Attributes and Arrays > Date Attributes

Date Attributes


The Date type attribute lets you define and use dates in Search and Configuration flows. Date attributes can be created at all levels of the product hierarchy, just like other configurable attributes.

All date attribute properties can be defined as they would on a text field type configurable attribute, including Set Type, Auto Update, Hidden, Required, Hide in Transaction, and Status.

Another major feature is the ability to define a Range Check on dates.

The date attribute is displayed as a text box with a date selector tool. This gives the user the option to either enter a date manually or select one from the calendar. An automatic validation runs to ensure that the date complies with the application and user profile information.

Date attributes can be of array or non-array type. Date arrays cannot be displayed as menus.


ClosedAccessing the Date Attribute Editor Page

  1. ClosedNavigate to the Configurable Attributes Administration List page.

    1. Click Admin to go to the Admin Home Page.

    2. Click Catalog Definition in the Products section.

      The Supported Products page appears.

    3. In the Navigation column, select Configurable Attribute and then click List.

      The Configurable Attributes Administration List page appears.

  2. Click the name of an attribute with Date in the Attribute Type column, or create a new attribute.

    The Date Attribute Editor page appears.

ClosedUsing the Date Attribute Editor Page

The Date Attribute Editor page has the following sections under the General tab: Main Information, Properties, and Default Data.

ClosedMain Information Section

  1. Edit the Name of the attribute.
  2. Enter a Description.

    If Help Icon is checked for the attribute in the Configuration Flow Editor, the description appears when the user hovers over the help icon.

    For more information, see Configuration Flows.

ClosedProperties Section

  1.  Choose the Set Type:
    • None The user can input any value without encountering an error message.
    • Set A recommendation rule can change the value entered by the user unless the attribute is locked by the user.
    • Forced Set A recommendation rule will change the value of the attributes regardless of what the user enters and if the attribute is locked or not.
  1. Select the appropriate checkbox for:
    • Required This will require the user to enter a value before proceeding to a commerce transaction.
    • Hidden This attribute will not appear to the user. It can be used in rules.
    • Auto Update This will by updated by the system without the user invoking an action.
    • Hide In Transaction This attribute is hidden within a commerce document.
  1. Choose the Status of the attribute:
    • Active An attribute that is active will appear to the buyer and/or be included in rules.

      All attributes are active by default.

    • Inactive An inactive attribute cannot appear in a rule to the user.
    • Internal An internal attribute will only appear to FullAccess users.
  1. Click Show Start/End Dates to specify how long the attribute will remain in the chosen status.

      If no duration is specified, the attribute maintains its status until the admin changes it.

ClosedDefault Data Section

  1. In the Default field, enter a default date or select a date from the date picker (if necessary).
  2. Check Use Current Date if you always want to use the current date as the default data.
  3. Select a validation. 
    • None: A validation will not be run.
    • Range Check: Enter a date manually, select one from the calendar tool, or use the current date. This can be used to verify that a date falls within an appropriate range before proceeding.


ClosedUse in Configuration Rules

Users will be able to use Date Attributes as simple and advanced condition attributes within all Configuration rules. Dates can be used in the Condition, Action, Condition Input, and Action Input like other configurable attributes. In addition, Recommendations and Constraints defined on Date Attributes return Date objects.

The following operators are available when data attributes are used in simple conditions:


While reading values of date attributes, the FullAccess user performs an isnull check to avoid errors.

Date attributes are supported in Bulk Upload and Download.

Date attributes are supported inthe Configuration SOAP API in the database format [yyyy-MM-dd 00:00:00].

However, a user cannot set a time component for dates through SOAP. All dates are set with the time component as 00:00:00.

    Attribute range calculations are validated on the Value Punch-In.

    Example: If the value was passed in the URL to the Configuration, it will be validated and an error message will appear.

    This affects both Mobile and Desktop.

Have as few attributes "auto-update" as possible.

Dates in Configuration do not support time.

    NULL and blank Integer values are treated as separate values.

    - NULL= 0
    - Blank = ""

    If you use logic that tests for NULL values in rule conditions or BML, this logic should be updated.

    Using "null" as an attribute value is strongly discouraged.


Related Topics Link IconSee Also