Next Performance as a custom element in Plans

Hi Anthony,

Custom Fields on Plans (like on Orders and Contributions) are set up in the T_KEYWORDS table and deposit the data in the T_PLAN table and, I'm assuming, are a static value - whereas the Flex Header elements are dynamic and (normally) look at the data in the Ticket History.

I'm not sure why you'd hold this as a value against the plan rather than (as Kathleen notes) as a value in the constituent header.  If this is so that it can be included in the Plan Summary report I reckon you could create it as a Custom Field on Plan but you'd need to have a scheduled task (and for this, you'd need a friendly DBA) that runs - usually overnight - to update the field so that it remains current/valid.

Feel free to let us know why you want this held against the Plan - maybe there's a better/easier way of getting the result you want!

Martin 

Hi Anthony,

Custom Fields on Plans (like on Orders and Contributions) are set up in the T_KEYWORDS table and deposit the data in the T_PLAN table and, I'm assuming, are a static value - whereas the Flex Header elements are dynamic and (normally) look at the data in the Ticket History.

I'm not sure why you'd hold this as a value against the plan rather than (as Kathleen notes) as a value in the constituent header.  If this is so that it can be included in the Plan Summary report I reckon you could create it as a Custom Field on Plan but you'd need to have a scheduled task (and for this, you'd need a friendly DBA) that runs - usually overnight - to update the field so that it remains current/valid.

Feel free to let us know why you want this held against the Plan - maybe there's a better/easier way of getting the result you want!

Martin