Passing today's date into a Lobby navigation link's URL filter using a substitution like `#TODAY#` against a truncated-date attribute doesn't seem to filter correctly, while a hardcoded date value in the same style of filter works fine.

Q: Passing today's date into a Lobby navigation link's URL filter using a substitution like `#TODAY#` against a truncated-date attribute doesn't seem to filter correctly, while a hardcoded date value in the same style of filter works fine.

The #TODAY#-against-a-truncated-date-attribute pattern (for example, DateEnteredTruncated eq #TODAY#) has been confirmed to work correctly in general — if it's not working for a specific field, check whether that field is actually a full datetime/timezone-aware attribute rather than a genuinely truncated date attribute, since the two behave differently when compared against a plain date substitution value; trying the equivalent filter against a known-working truncated-date field (like an existing "Created Today" lobby element) is a good way to confirm whether the substitution mechanism itself or the specific field type is the actual issue.

Answer

The #TODAY#-against-a-truncated-date-attribute pattern (for example, DateEnteredTruncated eq #TODAY#) has been confirmed to work correctly in general — if it's not working for a specific field, check whether that field is actually a full datetime/timezone-aware attribute rather than a genuinely truncated date attribute, since the two behave differently when compared against a plain date substitution value; trying the equivalent filter against a known-working truncated-date field (like an existing "Created Today" lobby element) is a good way to confirm whether the substitution mechanism itself or the specific field type is the actual issue.

← Browse Platform, Aurena, and customization questions