Solicit codes appearing unexpectedly in BBIS transaction batch and committing the reverse of the Supporter’s choice

When a Supporter makes changes to solicit codes in BBIS and then in the same session (i.e., without logging out) the Supporter makes other profile changes then this data will go to a BBIS Batch, and this will include the Biographical tab, and include the unexpected “Requests no email” row in the transaction data. This data is already written to CRM directly. When the batch is committed that batch will cause the solicit codes to be lost instead of retained.

Download and install the latest patch, which contains all fixes from previous patches. If you are running an older version, download and install the latest version and then the patch. 

Environment

 3.0.516.28
 3.0.516, Service Pack 9

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.