Shared metadata fields within a SharePoint Document Set fail to propagate to underlying child documents created via the Client-Side Object Model (CSOM) API upon updates to the Document Set. This issue is isolated to CSOM-created documents; manually created documents within the same Document Set exhibit correct metadata propagation behavior. Specifically:

1. Initial Creation: Shared metadata fields are correctly propagated to child documents (both CSOM and manually created) during the initial creation of the Document Set or the child documents.
2. Document Set Updates: Subsequent modifications to the Document Set's shared metadata fields are not reflected in the corresponding metadata of CSOM-created child documents.
3. Manual Document Updates: Manually created documents within the Document Set correctly receive updated shared metadata values.
4. CSOM Document Metadata Modification: Modifying any other metadata field of a CSOM-created child document triggers the propagation of the updated shared metadata values. Observed Behavior and Example:

Consider a shared metadata field "Status" with options "Open" and "Closed." in the documentset.

Upon creation of a document within it, the "Status" field is correctly populated. If the "Status" field of the Document Set is subsequently changed from "Open" to "Closed," the "Status" field of manually created documents within the set is updated to "Closed." However, CSOM-created documents retain the "Open" value. If a separate metadata field of a CSOM-created document is modified (e.g., "Title"), the "Status" field of that document is then updated to "Closed," reflecting the Document Set's current value.

As expected, Sharepoint should handle the sync of Shared metadata values to the underlying documents, but it skipped the documents which are created as part of CSOM. Why is that case? What will be the fix for this?