Brian is correct. Attributes are treated specially by criteria sets and you can’t directly pull their audit data (like creation date). Building a view would be the way to go, but if you do that you’ll need to create new criteria for all pieces of the attribute (type, value, and creation date) that pull from the view so you can use them together. You would not be able to successfully use the existing attribute criteria with new view attribute criteria because criteria they would be looking at different tables/views.
And now that I think about it, you may not need to create a view. If you just added all new list criteria that look at the table where constituent attributes are stored, I think that would work. The standard attribute criteria (ones where a single entry in T_KEYWORD doubles for both the attribute type/name and the corresponding criterion) are 2 for 1. They save you the step of having to add a criterion for the attribute name, in other words you select the criterion for a specific attribute and just select an attribute value for the value. If you create a set of generic attribute criteria (one for name, one for value, and ones for any of the audit data) you would have to always select 2 criteria any time you wanted to look at the attribute, one for attribute name where you select the specific attribute for the criterion value, and one for the attribute value where you select the attribute value for the criterion value.
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com