Hello,
Has anyone successfully added next performance (name/date/time) as a custom element in a constituent plan? If so, can you share the code that enables this?
Thanks!
Anthony
Hi Anthony,
I know flex headers have this code – can you steal something from there, perhaps? (admittedly, I haven’t worked a lot with custom elements in plans yet).
Cheers,
Kathleen
From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Anthony Busti Sent: Wednesday, January 04, 2017 12:01 PM To: Kathleen Smith Subject: [Tessitura Development Forum] Next Performance as a custom element in Plans
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development 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!
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
Instead of a custom Plan field (because of the reasons Martin explained), you could consider adding a custom portfolio element so that a worker can see that data at-a-glance in their portfolio. Kathleen is definitely correct that you can copy/paste the code for "Next Performance" from TR_FLEX_HEADER_ELEMENT into TR_PORTFOLIO_CUSTOM_ELEMENT and then add it to your portfolios. (You might need to change the view from LVS_TKT_HIST to VS_TICKET_HISTORY depending on your system setup.)
-Michael Wilcox, Tessitura Network
Thanks for the responses! We just wanted a quick way for a solicitor to see when someone was coming next if they were entering information in to the plan. I don't know if it's feasible for us to have it on the header as our headers have lots of information on it already (would become a space issue). But our DBA already suggested the portfolio option which I do love and will definitely implement.
Anthony,
Just saw this. We do the next show custom portfolio element here at PAA. Happy to help if you have any questions.
Hi Matthew,
How do you get the next show element to work?
I'm happy to share the line of code for this - just wondering what format you wanted it in...........
For example, my string returns the perf details as Jun 14 2018 8:00PM Ex Machina
select top 1 CONVERT(varchar,perf_dt,100) + ' ' + perf_name from LVS_TKT_HIST where perf_dt >= GETDATE() and customer_no = @customer_no order by perf_dt
Of course, you should check that the secure view LVS_TKT_HIST is valid for the task - ticket history being usually customised. This works as either a Flex Header or Portfolio element.