Skip to main content
New Idea

Ability to "Null Check" In Email Varients

Related products:None
  • February 22, 2018
  • 3 replies
  • 15 views

steve_davis
I have a customer that would like to "null check" a text field and use that to dictate a variant be used. There are a lot of filter options but != NULL isn't one. Engineering suggested enhancement request. 

3 replies

dan_ahrens
Forum|alt.badge.img+2
  • Expert ⭐️⭐️⭐️
  • 1984 replies
  • March 5, 2018
Agreed that a NULL option would be useful.

In the meantime, could you set your logic criteria such that the Default variant catches these individuals? 

diane_morneau
Forum|alt.badge.img
  • Helper ⭐️⭐️⭐️
  • 112 replies
  • April 18, 2018
Our use case is to produce Japanese letters and eventually in other languages too. In addition to the account and contact names in "English" representation, we have fields that allow us to store these names in their native language. Let's call them Foreign account name and foreign contact name.

For Japanese customers, we have two letter variants to cover the cases when the foreign names are provided versus not provided. Our inability to test for these fields being nul within an Advanced Outreach forces us to split these into two Power lists to send out the right letter. The day that the foreign fields information will be filled, they will be picked up again and receive the other version of the letter, which is not desired either.

The lack of being able to set the logic in the AO is doubling our work by forcing us to segment unduly our mailings... and we are only dealing with one language at this point.

abhishek_sivaraman
Hi Diane and Steve,

Agree with you. We will fix this soon (1 to 2 months).

Thanks
Abhishek S

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings