Retain custom field values when moving or cloning content across workspaces
under review
V
Vijay Sakthivel
Currently, custom field values are not retained when articles or page categories are moved to a different workspace or when they are cloned. This requires users to manually re-enter custom field values after these operations. Introducing support for preserving custom field values during move and clone operations to provide a more seamless content management experience would be greatly helpful in reducing manual effort.
Log In
M
Mukesh Sriram
Hi Vijay, Institutional Magpie, thanks for raising this request. I completely understand the pain point here. I'll take it up to be added to the roadmap and will get it sorted out sooner. Thanks.
D
D360 Product Management
updated the status to
under review
I
Institutional Magpie
This also applies when articles are translated via AI: The translated articles do not currently have the same custom fields as the native-language article by default. Please keep user-defined field values both when translating and when moving/cloning.
V
Vijay Sakthivel
Raised on behalf of Violet Lemming