So, I was hoping to add an attribute create date into my list building criteria for a situation where i want to pull anyone who has had certain attributes with certain values added within a certain time frame. However, I'm running into the following problem:
When I simply add a List Only row into T_Keyword to pull !.create_dt from tx_cust_keyword, it inserts into the queries where keyword_no = the row value. I understand that this is necessary for pulling attributes as list criteria because two attributes could have identical key_values and this clarifies in the query which keyword_no to look at. However, it eliminates any possible results from my query.
Has anyone run into this and know how to work around without teaching all employees how to manually edit the query? I thought about making a custom view that basically copied tx_cust_keyword, however, then I run into the opposite problem. When I'm trying to pull from that view on actual attribute values, I'm not specifying a keyword_no and I'm not sure how to get that into the query.
Any thoughts would be much appreciated!
Thanks!
Well, here in our consortium, we have a copy of the Tessitura view VXS_CUST_KEYWORD called LVXS_CUST_KEYWORD that has the create and modified fields. The List Manager element in T_KEYWORD we have is called Attribute Create Date and references this secured view.
I'm not sure what I understand by "run into the opposite problem" (3rd para, 2nd sentence). But creating a new view and referencing it in List Manager would eliminate the need for people to have access to either data they shouldn't see or to "Manual edit".
Let me know if you'd like more information or a hand setting this up!
Martin