User-defined constituency is changed to a different user-defined constituency when a record is affected by the duplicate check settings in an enhanced revenue batch.

After handling the duplicate check settings in an enhanced revenue batch and committing the transaction, a constituent's user-defined constituency is changed to a different user-defined constituency. 
We are currently evaluating this issue and will update this article when we have more information.
 

Environment

 3.0.516, patch 20

Was this article helpful?