• Replies 14 replies
  • Subscribers 414 subscribers
  • Views 259 views
  • Users 0 members are here
Related

Custom Criteria

Michelle Blau (Past Member)
$organization

Hello!

I'm working on building 2 custom criterion and I need a little assistance. 

Price Type Category: Below is what I have in T_KEYWORD, but received the error: 'Syntax Error in Query: Invalid column name 'customer_no (List Sql). Based on the error, I think this means that my issue is the Detail Table doesn't contain a customer id column. I think what I need to do in this case is create a custom view?

Desc: Price Type Category

Data Type: Number

Edit Mask: Alpha Numeric

Detail Tbl: TR_PRICE_TYPE

Detail Col: !.price_type_category

Ref Tbl: TR_PRICE_TYPE_CATEGORY

Ref Idcol: id

Ref Desccol: description

Primary Group Default: Default Value Number

Unique Production Seasons: What I want is to be able to pull lists of patrons that purchased tickets to more than 1 production each season. I started by copying Ticket History Unique Perfs in T_KEYWORD. This worked successfully without errors, but wanted to confirm I did this correctly. 

Desc: Tkt History Unique Prod Season

Data Type: Number

Edit Mask: Number

Detail Tbl: vs_ticket_history

Detail Col: count(distinct !.prod_season_no)

Thanks!

Parents
  • $organization
    I could be wrong, but you first must create the view before you can use it.
     
    In 'LVS_CRITERIA_PRICE_TYPE_CATEGOROY', the syntax is L = custom, V = view, S = secured.  In other words, it is a custom to your organization secured view that you have to create before you can use it within a query.
     
    Another common mistake is forgetting to grant access rights of the view to impusers and the tessitura_app after it has been created.
     
    GRANT REFERENCES, SELECT on [LVS_CRITERIA_PRICE_TYPE_CATEGORY] to impusers, tessitura_app
    GO
     
    Neil
     
Reply
  • $organization
    I could be wrong, but you first must create the view before you can use it.
     
    In 'LVS_CRITERIA_PRICE_TYPE_CATEGOROY', the syntax is L = custom, V = view, S = secured.  In other words, it is a custom to your organization secured view that you have to create before you can use it within a query.
     
    Another common mistake is forgetting to grant access rights of the view to impusers and the tessitura_app after it has been created.
     
    GRANT REFERENCES, SELECT on [LVS_CRITERIA_PRICE_TYPE_CATEGORY] to impusers, tessitura_app
    GO
     
    Neil
     
Children