Same functionality as Segment has for Dynamic Content Rule Filter Criteria "Has Linked Contact in Cu

User_C2WG0

As mentioned in this KB document "Dynamic Content: Wrong Content is Shown When Based on a Custom Object Record Which Should Meet Multiple Criteria (Doc ID 2469782.1)", if there are multiple CDO records are linked with a Contact, the behaviors of the "Has Linked Contact in Custom Object" filter are different when it is used in a Segment and a Dynamic Content.

In Segment, we can set multiple conditions in one "Has Linked Contact in Custom Object" filter.

But in Dynamic Content rule, we are only able to set one condition in one "Has Linked Contact in Custom Object" filter.

As results, if there is multiple linked CDO Records for a Contact, 'the filter in Segment' is able to filter out the CDO Record with the multiple conditions are completely matched Record properly.

However, 'the filter in Dynamic Content' will check the conditions separately, so it will include all the CDO Records that is matching any conditions.

So, this Idea is for ensuring the "Has Linked Contact in Custom Object" filter of Dynamic Content Rule have the same behavior with the same name filter in Segment.

- Reference: Existing Enhancement Request -- Enh 21824105.

josh.martin

Ken - so glad to see that I'm not crazy here! We've had to build so many workarounds to this lack of functionality...so I'm hopeful we can get this on Oracle's radar for a needed enhancement.

I see that you are referencing an existing enhancement request. Any chance there has been progress made on that?

User_C2WG0

Ken - so glad to see that I'm not crazy here! We've had to build so many workarounds to this lack of functionality...so I'm hopeful we can get this on Oracle's radar for a needed enhancement.

I see that you are referencing an existing enhancement request. Any chance there has been progress made on that?

Hi Josh,

Sorry that an enhancement request or dream-it Idea has no any ETA to support team, it is completely reviewed deeply by our product team, as you can see the vote number is only 70 (voted by 7 accounts) for this one, it may not sufficient to prioritize this thing at this moment, or it may have any other concern / difficulty for implementing it in current release. Anyway, unlike with a defect, the product design is out of control by support team, it's completely decided by our Product Team.

Brad West

Hi Josh,

Sorry that an enhancement request or dream-it Idea has no any ETA to support team, it is completely reviewed deeply by our product team, as you can see the vote number is only 70 (voted by 7 accounts) for this one, it may not sufficient to prioritize this thing at this moment, or it may have any other concern / difficulty for implementing it in current release. Anyway, unlike with a defect, the product design is out of control by support team, it's completely decided by our Product Team.

So we're at 230 votes now... this lacking functionality is such a maddening inconsistency...

Any closer to resolution? Or any word on when the next generation of dynamic content will be coming?

Sebastiaan Van Dingenen-iODigital

This needs to happen... It's never fun that you have to build programs and update rules just to fit everything in a single field for your dynamic content.