This is to reverse a product change that was made in 4.0 SP6.
During CRM set-up, our Blackbaud consultant configured and marked certain constituencies as 'inactive' after we created the global change that would add them based on specific transactions or other data in the system. This allows us to continue to use/display these constituencies on a constituent record, but prevents users from adding them directly. This was a wonderful approach for a number of our constituencies.
The change in SP6, however, prevents this as no constituencies that are not marked as 'active' are displayed. We need a way to display constituencies but prevent users from front-end addition. We would like another constituency status for this situation, maybe something like 'active but hidden'.
|Organization Name (Please enter full organization name)||The Nature Conservancy|