When the user submits a Data Change Request (DCR) from the Veeva Network UI, the accreditation information gets pushed into hco_accreditation_2__v and hco_accreditation_3__v.
Is there any way to stop this from happening and keep the information in hco_accreditation_8__v and hco_accreditation_9__v?
There is no way to stop this behavior because the Network UI is designed to automatically resort and remove blank values (same for specialty_1__v...specialty_10__v).
The user can update the field value with what is needed and update through Network Source Subscription after the record is created.
Send us your feedback: We are always looking for feedback to help improve our Knowledge Base! Please let us know if this article is helpful or provide feedback on how we can improve your experience by clicking here.