List Manager Attribute Count Error

Nothing has changed in 12.5.1 (at least as far as I know). So, I would think it is something else in the list criteria.  Have you tried to pull a list with other attributes? Maybe, the replace individuals, add associations, etc. is messing it up.  I would run a one off in SSMS and see if you get a result. 

Travis

Example (can be easily adjusted for dealing HH):

select distinct  z.customer_no ,a.description , b.id , z.keyword_no
from
T_KEYWORD a
join T_KWCODED_VALUES b on a.keyword_no= b.keyword_no and b.id =  #### -- KWCODED_VALUE ID goes here
left join TX_CUST_KEYWORD z on a.keyword_no = z.keyword_no and z.keyword_no =#### --keyword id goes here
where  z.key_value = b.key_value

Hi Travis, 

I used a query similar to the one you've suggested and got results. We're not using any of the HH things in the list and the attribute is on the Individual records anyway. 

Hmm, it's a puzzler. 

Hi Travis, 

I used a query similar to the one you've suggested and got results. We're not using any of the HH things in the list and the attribute is on the Individual records anyway. 

Hmm, it's a puzzler. 

Hi Kelly

Does the user group you're running it under not have access to the control group on the attribute?

Have you checked what query the List is actually running underneath?

I've found that quite useful trying to interpret odd results. I look at the query and think "You're doing what???".

Also, of course, you can then copy the query out and play with it in SSMS -  and if you get different results from what you get  running it in Tess, you know it's time for a call to TASK.

Ken

I think it's time to call TASK. 

Everything is correct regarding Control Groups. 

When I pull a simple query in SSMS using TX_CUST_KEYWORD and referencing that Keyword No I get results, but not with the query straight out of List manager. 

Thanks for all you suggestions. 

Kelly

Hi Kelly, 

I was just wondering if you ever got to the bottom of this? We seem to be having a similar issue with one of Education attributes where it's fine if you run a query in SSMS and doing an attribute search in the Constituents, but will not work in List Manager. 

I'm about to raise on TASK but thought I'd see if you'd figured it out before I do :-)

Thanks

Gemma

Hello Gemma, 

Yes we did. My particular issue was to do with a incorrect value in 'ref_IDCol'. The attribute needed to use "key_value" as the reference as that is the data which is stored in TX_CUST_KEYWORD.

Hope this helps. If not a TASK ticket will sort you out. 

Kelly

Thanks Kelly, looks like we've got a different issue as our ref_IDCol is correctly showing key_value.

I'll get it raised with Tessitura now :-)

Thanks

Gemma