Smart List Date Filters and Custom Object Records | Community
Skip to main content
Level 5
April 17, 2023
Solved

Smart List Date Filters and Custom Object Records

  • April 17, 2023
  • 1 reply
  • 2711 views

Hello,

Looking to do a basic pull for a Custom Object Record of Membership Date that is 1 year ago to the day. In theory this should work according to everything I've read:

nhabischWings_0-1681740836286.png

But it's pulling all sorts of different dates for the field. When dealing with Custom Object records, is this an issue with the Smart List filtering and using multiple filters of the same object? Or is something wrong with our date field input? It's coming in as the proper YYYY-MM-DD, but something is off.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

The problem with this logic (as people sometimes discover too late) is that the filters are not necessarily looking at the same record.

 

So this could only work if the person has one and only one CO record.

 

The way to prepare for this is having 2 DateTime fields on the CO, each holding the same value.

1 reply

Darshil_Shah1
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
April 17, 2023

What is your SL filter logic  (ANY or AND)? Do you want to pull in records with the "Membership Opening Date" field = any value in the past 1 year or the records with the "Membership Opening Date" field = exactly 365 days in the past from today?

 

FYR - "In past Before x days" operator would pull all people with a date set to a value before x days (e.g., x-1, x-2, etc.) or don't have any value in the field (i.e., Membership Opening Date = NULL would also be filtered in if you're using ANY smart list filter logic.)

 

Level 5
April 17, 2023

Opps sorry, "AND" would be the logic - looking for those who are at exactly 365 days for a 1-year email.


SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
April 17, 2023

The problem with this logic (as people sometimes discover too late) is that the filters are not necessarily looking at the same record.

 

So this could only work if the person has one and only one CO record.

 

The way to prepare for this is having 2 DateTime fields on the CO, each holding the same value.