Hello. I'm doing a local custom version of Revenue by Source and Appeal (ap_camp_appeal_expense). In it individual source codes are subtotaled by source groups. The person I'm building this for would like there to be additional subtotals of certain source numbers (but not others) that have the same source group. So for example, in the source group 12 'development' (which already subtotals), source numbers 2, 5, and 7 should also subtotal, but not 1, 3, 6, etc.
I don't see a good way to do this. Has anyone else run into something similar?
Unknown said:Has anyone else run into something similar?
Project requirements that run counter to the structure of information in Tessitura? Oh my yes.
Basically they want things totaled by group, then also totaled by some other arbitrary group. I can see two options: 1) include a multi-select parameter for Source. You'll want another parameter for Appeal before it which restricts the sources available, or the multi-select menu will become unwieldy, and also unreadable (you'll likely have many sources in different appeals with the same or similar names). The user will have to do multiple runs to get what they want, but if the request for these subgroups is arbitrary, or likely to change often, this is the only reasonable way to do it.
Alternatively, if there is a real sense of subgroups within source groups, you might create a custom table which allows you to define these sub-groups, and then use that in your stored procedure to create more fine-grained groupings.