• Replies 8 replies
  • Subscribers 339 subscribers
  • Views 34 views
  • Users 0 members are here
Related

t_customer.cust_group?

Levi Sauerbrei
$organization

The Table Structures document doesn't elaborate on the source or reason for t_customer.cust_group.  Is this a deprecated column?  If not, what is its purpose?

I don't have a lot of records with values other than 1 (less than 10%) but I'm always looking for different ways to segment records.

Thanks.

Levi

Parents
  • $organization

    I would take your t_customer.cust_type and join to tr_cust_type. Use the cust_group value off that table.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Nathan Wigham
    Sent: Tuesday, May 29, 2012 9:04 AM
    To: Martin A. Jones
    Subject: RE: [Tessitura Technical Forum] t_customer.cust_group?

     

    In testing reports I found that one of our local ones uses 'cust_group IN (1,3)' as criteria (while I couldn't find a lookup table for these values, cust_group=1 always corresponds to cust_type=1, or Individual; and cust_group=3 always corresponds to cust_type=6, or Organization Contact).  In v10 this worked, but it looks like that field contains only Null values as of v11 (in our test environment).  So the report no longer returns any records.

    I was going to change the criteria to 'cust_type IN (1,6,9,11)' which would represent Individual, Organization Contact, Household, and Contact.  But it got me wondering what happened to the cust_group values.  Is there something in the update process that nulls the values out?  Should we include something in our update script to set the cust_group values?

    Thanks very much!

    Nathan

    From: Levi Sauerbrei <bounce-levisauerbrei8271@tessituranetwork.com>
    Sent: 10/4/2010 1:38:08 PM

    Excellent!  Thanks Ryan.




    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!

Reply
  • $organization

    I would take your t_customer.cust_type and join to tr_cust_type. Use the cust_group value off that table.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Nathan Wigham
    Sent: Tuesday, May 29, 2012 9:04 AM
    To: Martin A. Jones
    Subject: RE: [Tessitura Technical Forum] t_customer.cust_group?

     

    In testing reports I found that one of our local ones uses 'cust_group IN (1,3)' as criteria (while I couldn't find a lookup table for these values, cust_group=1 always corresponds to cust_type=1, or Individual; and cust_group=3 always corresponds to cust_type=6, or Organization Contact).  In v10 this worked, but it looks like that field contains only Null values as of v11 (in our test environment).  So the report no longer returns any records.

    I was going to change the criteria to 'cust_type IN (1,6,9,11)' which would represent Individual, Organization Contact, Household, and Contact.  But it got me wondering what happened to the cust_group values.  Is there something in the update process that nulls the values out?  Should we include something in our update script to set the cust_group values?

    Thanks very much!

    Nathan

    From: Levi Sauerbrei <bounce-levisauerbrei8271@tessituranetwork.com>
    Sent: 10/4/2010 1:38:08 PM

    Excellent!  Thanks Ryan.




    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!

Children