Overview:
Fields configured with a DCR Field Type of DCR Editable do not revert to the original values upon rejection of the DCR.
Root Cause:
Rejected DCRs do not perform an update of the related record during a DCR Inbound job. Any DCR editable fields remain with a new rejected value until the Network Subscription is run to update the record.
Solution:
This is currently working as designed. The record contains incorrectly updated fields reverted to the original values when the Network Subscription is run.
Related Documentation:
N/A
Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.
Thank you