SOLVED

Fields spread out across different custom objects

Go to solution
LCENTENO
Level 3

Fields spread out across different custom objects

Hi everyone,

Quick question. I have a set of 7 different criteria that I am investigating to setup a smart list for a recurring campaign. The data fields do exist, however they are spread out across different custom objects.

For example, one custom object (we will call it "Balance") has the "Tier" field, while the other custom object (we will call it "Rating") has the "Rate" field, and the last custom object (we will call it "Acquisition") has the "Acquisition Date" field. 

What would be the best way to setup a campaign smart list to include these fields? Thanks in advance for your help.

Best,

Lucas

1 ACCEPTED SOLUTION

Accepted Solutions
Darshil_Shah1
Level 10 - Community Advisor + Adobe Champion

Re: Fields spread out across different custom objects

You can use the Has xyz custom object filter for CO and its field is abc in the SL, but that won't guarantee you're referencing the records in different COs in relation to one another (e.g., this logic won't guarantee that the qualified records have all the records in different COs added in the same timeframe). This will just check whether the people have each CO record with the respective field as per the constraint in the Has CO filter set.

View solution in original post

2 REPLIES 2
Darshil_Shah1
Level 10 - Community Advisor + Adobe Champion

Re: Fields spread out across different custom objects

You can use the Has xyz custom object filter for CO and its field is abc in the SL, but that won't guarantee you're referencing the records in different COs in relation to one another (e.g., this logic won't guarantee that the qualified records have all the records in different COs added in the same timeframe). This will just check whether the people have each CO record with the respective field as per the constraint in the Has CO filter set.

Katja_Keesom
Level 10 - Community Advisor + Adobe Champion

Re: Fields spread out across different custom objects

@Darshil_Shah1 is absolutely right. The only thing I find many people struggle with is the double negatives in setting up filters like this, as you need to combine your "has or does not have a Custom Object record" that "does or does not meet" the constraints.

As an example: Has Balance with Tier is not X and Does not have Rating where Rate is Y translates to the fact that there does noeed to be a Balance record with Tier being equal to anything but X and there cannot be a Rating record with value Y (so there can be a Rating record as long as the value is not Y).

You can combine your different CO filters with the normal All/Any/Advanced filter logic.