adding solicit code when creating a new constituent from RENXT online gift

Jennifer, this is an unusual request. Folks don't usually make requests when making an online gift that needs to be reflected as a solicit code. I'm not sure there's anything that can be done or the product managers will prioritize this, but can you explain why you need to add a solicit code? Maybe some of us can help you figure out a different strategy that for that information. Thanks.

The way Solicit Codes was intended, and the way most people/orgs use it, is only for exceptions when requested by the constituent. So no one else I know uses "all mail," for example: it's assumed we can mail, email, etc., unless it specifically says we can't. I don't know of anyone that adds a solicit code for every constituent and the way it's designed is you shouldn't. For example, Solicit Code is an exclusion filter in Mail in the db view. You don't filter in "all mail" — that's assumed — you filter out the "no mail." Hope that helps. :) [This is for U.S. orgs. If you're outside the U.S. and getting into Consent issues, you should be using RE Consent and not manually populating the opt-in via the "all mail" solicit code.]