• Replies 8 replies
  • Subscribers 339 subscribers
  • Views 31 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

  • $organization

    This column controls whether or not a constituent is an individual (“I”), organization (“O”),  or Contact (“C”) which is a further categorization of Constituent Type.  This value is set when a constituent is created from the Constituent Type (TR_CUST_TYPE.cust_group) or when the type is changed.

     

    This also controls what appears in the Constituent Search results.  There are checkboxes for Individual, Organization, Contacts in the top of the search window. 

     

    This is normally the point at which I point these out and someone says…”oh that’s what those check boxes are for!”, which is what I did a few years ago when Anna showed them to me.

    J

    -Ryan

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Levi Sauerbrei
    Sent: Monday, October 04, 2010 11:08 AM
    To: Ryan Creps
    Subject: [Tessitura Technical Forum] t_customer.cust_group?

     

    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




    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!

  • $organization in reply to Levi Sauerbrei

    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

  • $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!

  • $organization in reply to Marty Jones

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

    Elegant, I like it.  Thanks for the suggestion!

    Nathan

  • $organization

    This is part of the denormalizing in v11.  In previous versions, the T_CUSTOMER.cust_group was kept in sync with TR_CUST_TYPE.cust_group.

     

    +Ryan Creps

    +Tessitura Network

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Nathan Wigham
    Sent: Tuesday, May 29, 2012 10:40 AM
    To: Ryan Creps
    Subject: RE: [Tessitura Technical Forum] t_customer.cust_group?

     

    Marty Jones:

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

    Elegant, I like it.  Thanks for the suggestion!

    Nathan

    From: Marty Jones <bounce-martyjones7649@tessituranetwork.com>
    Sent: 5/29/2012 9:11:32 AM

    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!




    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!

  • $organization in reply to Ryan Creps (Past Staff Member)

    Ryan (or anyone else),

    We have a list criterion that doesn't work now because cust_group is null in T_CUSTOMER.  I'm trying to figure out how to make this work in v11.  Is there any way without creating a view to pull the customer_no and cust_group together?

    Here's the entry in T_KEYWORD as it is:

    keyword_no 430
    description Constituent Category
    data_type 2
    edit_mask Number
    detail_tbl T_Customer
    detail_col !.cust_group
    ref_tbl TR_CUST_GROUP
    ref_IDCol id
    ref_DescCol description

    Thanks for any help!

    Bryan Evans | Manager of Data Analysis
    Cincinnati Symphony and Pops Orchestra
    Music Hall | 1241 Elm St. | Cincinnati OH 45202
    513.744.3283 ph | 513.744.3535 fax
    www.cincinnatisymphony.org 

    Connect with the CSO and Pops
    Join Email list | Facebook | Twitter | YouTube

  • $organization in reply to Bryan Evans

    Bryan,

    I don't think there is another way without creating a view since to get the cust_group you have join via they TR_CUST_TYPE table. Then pointing the detailTbl to the view.

    The view can be similar to below:

     

    Select c.customer_no, c.cust_type, cg.id as cust_group

    From T_CUSTOMER c 

    Left Join TR_CUST_TYPE ct on c.cust_type = ct.id 

    Left Join TR_CUST_GROUP cg on ct.cust_group = cg.id

     

    Maybe someone else may know of a different way.



    [edited by: Renville Williams at 2:34 PM (GMT -6) on 16 Nov 2012]