Folks,
I'm creating a new local table - so far, so good.
My wrinkle is that I want one of the fields to hold the customer_no - I appreciate that I can have the TR_REFERENCE_COLUMN.dddw_description field show a value like lname + ', ' + fname + ' - ' + customer_no but is there any way of making the Constituent Search screen open up instead?
Does anyone else have an LTR_ table that holds the customer_no value? How do you make this work most efficiently for you?
Martin
Hi, Martin!
Quick post: There is no way to open a Constituent Search from System Tables.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Martin Keen Sent: Monday, January 9, 2017 6:20 PM To: Ryan Creps <rcreps@tessituranetwork.com> Subject: [Tessitura Technical Forum] Local table and Constituent ID field
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!
Following up on Ryan and Troy: FS_GET_CONSTITUENT_DISPLAY_NAME is the function you want for displaying a "pretty name" for a constituent number, but attempting to have a column for selecting constituents at large in your System Tables will cause Tessitura to catch fire and fall over. So, doing something with constituents in the System Tables generally is a bad idea (custom tabs is certainly the way to go there), unless the number of constituents is vanishingly small.
For instance, there are a number of custom System Tables I've built that refer to Tessitura Users: and we all know that Tessitura wants to eventually fold those into customer accounts (as they already have with solicitors). That would still work because the special class of customer records is going to be extremely small. In that case you would determine some way to isolate the limited number of customer accounts that would be relevant to the table, then create a view restricting its returns to that set of customers, and use FS_GET_CONSTITUENT_DISPLAY_NAME as part of the view to provide a "display name" column.
Many thanks for your responses. I suspected this wan't a viable option but thought I'd check anyway!
The background to this is that we are looking for a way to manage scholarships in Tessitura. My idea (and the one favoured by our finance team) is that each scholarship has it's own fund that's used when the monies are paid into us. As funds in Tess have the ability to hold very little reference data, I want to have a system table to hold this - and primary contact is one of the items. As the number of scholarships numbers only about 40, I don't think this will be an issue.
I'm considering the idea that each scholarship is also it's own constituent entity which would allow for the creation of a custom screen to tie the whole thing together.
Does anyone else do this? Can you suggest a better way?