Tessitura Analytics and Custom Fields for Orders, Contributions and Plans

Hi All,

I'm gathering feedback on a Tessitura Analytics roadmap item. The custom fields for Orders, Contributions, and Plans are already available in Analytics. However, they appear in Analytics with field names "Custom 01", "Custom 02", etc. and don't currently respect the characteristics of the field data types as configured in Tessitura. The reasons for this come down to control group security. It is a feature of Tessitura that the first custom field on an Order can be configured as a date value for one control group (Birthdate let's say), and a drop down list of descriptive text values for another control group (Favorite Ice Cream maybe), each appearing with the configured custom field name (description) on the order processing screen. Tessitura also allows us to change what currently IS the first custom field - I no longer wish to track ice creams and would like instead to start tracking a household child-count, as a number - without losing the historical custom field data. Ice creams would still technically be reportable for the orders that have that data stored against them.

I'd like for Analytics to support displaying the name of the custom field (rather than "Custom 01"), and its data type, as configured in Tessitura. There is one issue that may be a non-starter however: a limitation in Sisense that prevents hiding the custom field names and data types of one control group from another (table and column level data security is not currently supported). The data stored IN those fields would NOT be visible across control groups (this can be secured using the same row-level data security already in place in Tessitura Analytics). It's this issue that one organization, with their own set of configured custom order fields (or without any), would see that Birthdate, Favorite Ice Cream, and a Household Child Count are being collected by one or more other members in that Tessitura instance.

Again, members would not see the data stored in these fields across control groups, but would see the field names and have visibility into the types of custom data being collected and stored. Please consider this question from a Contributions and Plans perspective as well. 

How important is it that consortium members not see that other members are... collecting custom data, and the descriptive names of that custom data, when weighed against having those descriptive field names and explicit data types (eg. dates and numerics) in Tessitura Analytics?

Thanks in advance.