Hi,
We had a requirement to rename an asset folder , so we used move* option to rename it to a new name. I checked the update references and republish option and the refrences are updated as expected. But for the content fragments inside the renamed folder , i see the cq:parentPath property isn't updated. It's showing old name value. Attaching screenshot ( see the path I have opened is "beyond" but cq:parentPath property still shows "beyondinc" which was the initial value of folder name.
解決済! 解決策の投稿を見る。
トピックはコミュニティのコンテンツの分類に役立ち、関連コンテンツを発見する可能性を広げます。
表示
返信
いいね!の合計
For anyone who wants to know answer to it, the reply I got from Adobe support is -
" I further investigated the issue and found out that the unchanged cq:parentPath is an expected behavior in AEM as a Cloud Service. The fact that the cq:parentPath remains unchanged after a move operation is by design in AEM as a Cloud Service – Assets. This property was never intended to be automatically updated and now serves only as a historical reference. There is no out-of-the-box API or feature available to trigger an automatic update of this property when assets are relocated. If you are needing an updated path reference after asset movements you may need to implement custom logic or workflows to maintain such data within their specific asset management processes. "
表示
返信
いいね!の合計
HI @NidhiSh6 ,
What is the AEM version you are using?
Also these property are being created from DAM Metadata Writeback workflow, go to your workflow console and check if you are seeing any error with the workflow?
If still you face issue, please raise a day care support ticket.
-Tarun
We're currently using AEM Cloud. I’ve reviewed the DAM Metadata Writeback workflow and didn’t find any errors. For newly created content fragments, the property appears to be added correctly. I've also raised a support ticket with Adobe to investigate further.
Thanks, Tarun —really appreciate your help.
表示
返信
いいね!の合計
For anyone who wants to know answer to it, the reply I got from Adobe support is -
" I further investigated the issue and found out that the unchanged cq:parentPath is an expected behavior in AEM as a Cloud Service. The fact that the cq:parentPath remains unchanged after a move operation is by design in AEM as a Cloud Service – Assets. This property was never intended to be automatically updated and now serves only as a historical reference. There is no out-of-the-box API or feature available to trigger an automatic update of this property when assets are relocated. If you are needing an updated path reference after asset movements you may need to implement custom logic or workflows to maintain such data within their specific asset management processes. "
表示
返信
いいね!の合計