After Migrating Folders_g to Framework Folders, Security Fields Do Not Get Propagated
Last updated on AUGUST 07, 2017
Applies to:Oracle WebCenter Content - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Content Server
When propagating metadata down from a parent folder, the only field selected on the propagation form to propagate is the User ACL field or some other security field.
The child folders and content items do not get changed from the propagation.
Sometimes an error is generated like this:
csFldUnableToPropagate Unable to propagate. Unable to propagate the null field ''xPdfwTemplateID''
The error could reference any metadata field. This happens even though the field in the error message was not selected to propagate.
It is expected that the security fields that are selected should be propagated successfully, with no errors.
The issue can be reproduced at will with the following steps:
1. The User ACL contains 1 user.
2. Select Edit -> Metadata on the parent folder. Add another user to the User ACL on the metadata form of the parent folder. There are now 2 users in the User ACL, and this is what should be propagated.
3. Select Edit -> Propagate on the parent folder. Check only the box for the User ACL field, and click Propagate.
4. The child folders and content items do not get changed from the propagation. Sometimes, the error is seen even though the xPdfwTemplateID field was not selected to propagate.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms