Non-localizable fields: Status History

Below is the history of changes to this idea's status. Return to the idea.

  • Under Community Review

    Hi Ron,

    Thank you for your ideas!

    Please provide more input on the expected functionality (preferably with use cases why one or other approach is important):

    1. When localizing an item, CM copies all fields from the parent item. After that, changes to the parent component are not propagated to localized ones. Is this expectation correct for non-localizable fields or should they behave like shadow copies of parent field (e.g. new value should be propagated to local copies as well)?
    2. In order to keep parent-child fields in sync, would it be acceptable to deny changing non-localizable field value on the parent component if it was localized somewhere down in the BluePrint?
    3. Is this feature needed for content (e.g. content of the component) or for other item's metadata fields (e.g. metadata on the structure group) or both?
    Anton Minko (former member)

  • New

    No note was provided with this status update.

    Ron Grisnich