This is working as expected. When a Product’s Date attribute is referenced in CML, the constraints engine will default the Date attribute value to Jan 1, 9999.
Workarounds:
Set the configurable annotation to false:
@(configurable=false)
date Date_Attribute;
OR
Use a preference Rule to assign the date.
preference(Date_Attribute == null -> Date_Attribute == "2026-12-31”);
OR
Use the defaultValue annotation within a domain.
@(defaultValue = “2027-01-01”)
date Date_Attribute = ["2026-01-01", "2027-01-01”];
OR
If CML should ignore the Date attribute completely, consider also commenting:
// date Date_Attribute;
See also:
005387374

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.