Hi, I am very new to Tessitura, so this might be an easy fix and I am just overlooking it. But here is the situation,
we are moving to the Wordfly email platform. As part of that process, we created new Attributes -> Interests to store
information on which of our email newsletters our customers have chosen to subscribe to.
I created those using System Tables TR_TKW_CATEGORY and TR_TKW.
They successfully appear and are editable under the constituent Attribute tab.
But, and this is the problem, they are not available to select as an Element when creating an Output Set for use with List Manager.
I have referenced the Output_Set_Manager_Cookbook and it provides this instuction to add an element:
Column Name
Example Value
Description
Attributes - local
Data_From
VXS_CUST_KEYWORD
Data_Where
[Blank]
Virtual Ind
[Unchecked]
Category
Attributes
NOTE: For Attributes that can be added multiple times to a Constituent with different values, Single_row should be unchecked. Check the Attribute’s setup in T_KEYWORD
Name of your Attribute
Group Id
Data_Select
!.key_value
Single_row
[Checked]
Primary Group Default
Keyword_no
ID of the Attribute in T_KEYWORD
But where I run into the issue is "Keyword_No". I am not seeing the Interests I created in T_Keyword, so I have no idea what value to enter here.
Do I need to manually add them there as well? Or is there some other obvious part of this process that I am overlooking?
Henry,
Your Interests aren't in T_KEYWORD, they're in TR_TKW. There's a table, TX_CUST_TKW that stores the interests by tkw id and customer number - you just need a secure view of TX_CUST_TKW to use for the output element, and it's already there: VXS_CUST_TKW should work
Mindee,
Thank you for your response. It was super helpful, but I am now running into another error when I try to save my newly created Interests in TR_QUERY_ELEMENT.
I enter a Description, a Group ID and the Keyword #. But then I run into problems at the Data Select. I initially tried !.key_value, but that returns and error saying {Invalid Column Name "key_value"}.
It looks like the previously existing elements in TR_QUERY_ELEMENT have data selects that have been defined in a separate table as they are quite specific (ex:!.perf_name, !.campaign_no, etc...). Any idea what I shut due using for a data select or what step in the process I missed where I would have defined the data select the newly created interests should be using? These are just checkbox data, so it should be either 1 for checked or 0 for unchecked.
Also, side question, is TX_CUST_TKW a table that can be viewed? When I asked my Tessitura admin for access to it, he said he couldn't find it in the Security App (I'm in marketing, so I have no idea what that really means in terms of Tessitura administration).