What happens if the "DeDuped Custodians" field is associated with an object other than the "Custodian Object"?

When the "DeDuped Custodians" field is associated with an object that is not the designated "Custodian Object," it disrupts the expected functioning of the document publishing process. This association is critical as it maps specific custodians to the corresponding documents they are responsible for. If this relationship is misaligned, the system cannot appropriately recognize and validate the custody of the documents, leading to a halt in the publishing process.

In practical terms, this means that documents cannot be published to the workspace as the underlying data structure that supports this operation becomes invalid. A correct association is essential for the logical integrity of the data being processed, ensuring that custodians are accurately linked to their documents. Without this proper linkage, the process encounters a failure point, resulting in an inability to publish, as the system may flag this inconsistency as a significant issue that prevents further action.