Creating a list builder element for one interest only

Sorry, too early in the morning. Read as output element.

Are you giving your keywords an alias? 

ID  NNN

DESCRIPTION  tricky keyword

CATEGORY          NNN

DATA_SELECT  !.keyN

DATA_FROM  (select customer_no, key_value as ‘keyN’, keyword_no as ‘kwN’ from VXS_CUST_KEYWORD)

DATA_WHERE  kwN = N

(N=numeral)

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Sadie Prater
Sent: Wednesday, August 26, 2015 9:04 AM
To: John Trimble <J.Trimble@dbdt.com>
Subject: [Tessitura Technical Forum] Creating a list builder element for one interest only

Hey Everyone. My organization ran into an issue the other day and I was hoping for some guidance.  We are currently tracking our out-outs through Constituent Interests and would like to have list builder elements dedicated to the opt out parameters so that it is a bit more fool-proof for the users making lists/extractions.

The issue we are running into is that the custom interest element made in T_Keywords is not constraining the element to only one tkw id.  Can anyone point me in the right direction on how to get this element constrained to only one tkw from VSX_CUST_TKW?

Thank you in advance for any help or guidance.

Technical details on the current setup:

The T_KEYWORD entry reads:

Keyword No = 449

Description = Opt out of Paper Mailing*

Data Type = String

Edit Mask = None

Detail Tbl = VSX_CUST_TKW

Detail Col = !.selected

Ref Tbl = TR_GOOESOFT_DROPDOWN

Ref Idcol = short_desc

Ref Desccol = description

Ref Where = code=1 AND id=1

Ref Sort = (NULL)

Category = Contact Preferences*

Use for List = List Only

Multiple Value = N

Control Group = Default Control Group

Custom ID= (NULL)

Custom Limit =(NULL)

Custom Required = N

Custom Default Value = (NULL)

Incl In Basic Search = N

Keyword Desc = Customer opts out of receiving direct mail

Primary Group Default = Default Value No

Parent Table = (NULL)

Parent Key Column = (NULL)

Key Column = (NULL)

Using this setup we are getting the following: no constraints Where a1.tkw in (43)

Select Distinct a.customer_no 

 From V_CUSTOMER_WITH_PRIMARY_GROUP a  WITH (NOLOCK)

 JOIN (Select a1.customer_no From VXS_CUST_TKW a1 WITH (NOLOCK) Where a1.selected in ('Y')) as e ON e.customer_no = a.customer_no

 Where  IsNull(a.inactive, 1) = 1 

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Sorry, too early in the morning. Read as output element.

Are you giving your keywords an alias? 

ID  NNN

DESCRIPTION  tricky keyword

CATEGORY          NNN

DATA_SELECT  !.keyN

DATA_FROM  (select customer_no, key_value as ‘keyN’, keyword_no as ‘kwN’ from VXS_CUST_KEYWORD)

DATA_WHERE  kwN = N

(N=numeral)

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Sadie Prater
Sent: Wednesday, August 26, 2015 9:04 AM
To: John Trimble <J.Trimble@dbdt.com>
Subject: [Tessitura Technical Forum] Creating a list builder element for one interest only

Hey Everyone. My organization ran into an issue the other day and I was hoping for some guidance.  We are currently tracking our out-outs through Constituent Interests and would like to have list builder elements dedicated to the opt out parameters so that it is a bit more fool-proof for the users making lists/extractions.

The issue we are running into is that the custom interest element made in T_Keywords is not constraining the element to only one tkw id.  Can anyone point me in the right direction on how to get this element constrained to only one tkw from VSX_CUST_TKW?

Thank you in advance for any help or guidance.

Technical details on the current setup:

The T_KEYWORD entry reads:

Keyword No = 449

Description = Opt out of Paper Mailing*

Data Type = String

Edit Mask = None

Detail Tbl = VSX_CUST_TKW

Detail Col = !.selected

Ref Tbl = TR_GOOESOFT_DROPDOWN

Ref Idcol = short_desc

Ref Desccol = description

Ref Where = code=1 AND id=1

Ref Sort = (NULL)

Category = Contact Preferences*

Use for List = List Only

Multiple Value = N

Control Group = Default Control Group

Custom ID= (NULL)

Custom Limit =(NULL)

Custom Required = N

Custom Default Value = (NULL)

Incl In Basic Search = N

Keyword Desc = Customer opts out of receiving direct mail

Primary Group Default = Default Value No

Parent Table = (NULL)

Parent Key Column = (NULL)

Key Column = (NULL)

Using this setup we are getting the following: no constraints Where a1.tkw in (43)

Select Distinct a.customer_no 

 From V_CUSTOMER_WITH_PRIMARY_GROUP a  WITH (NOLOCK)

 JOIN (Select a1.customer_no From VXS_CUST_TKW a1 WITH (NOLOCK) Where a1.selected in ('Y')) as e ON e.customer_no = a.customer_no

 Where  IsNull(a.inactive, 1) = 1 

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!