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. 


 3.0.516, Service Pack 9

Was this article helpful?