Non-localizable fields

Fields marked as non-localizable in a schema cannot be edited in localized components (should appear as read-only field in local copies).

Example of configuring a non-localizable field:

Tridion Sites Ideas schema configuration interface showing a field detail section with 'Non-localizable' checkbox circled, indicating the field is set to be non-editable in localized components.

Ron Grisnich

Top Comments

Mark Saunders over 5 years ago in reply to Suman Daripa +1

I would suggest we keep it simple. If the field already exists and components are created based on it when the change is made, the system simply tells the user "Hey, there's content localized already …

Parents

Suman Daripa over 5 years ago

Would be a very useful feature. Currently developers achieve this with Event System. Can you please explain what would be the behaviour if someone mark a field in schema when it is already in use and localized components contain local value to the field?
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
Ron Grisnich over 5 years ago in reply to Suman Daripa

Thanks for your response, Suman. In my opinion, there are multiple approaches feasible, including only allowing this on new fields and overriding the values of fields in localized components (potentially loosing (localized) content).
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel

Comment

Ron Grisnich over 5 years ago in reply to Suman Daripa

Thanks for your response, Suman. In my opinion, there are multiple approaches feasible, including only allowing this on new fields and overriding the values of fields in localized components (potentially loosing (localized) content).
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel

Children

No Data

Tridion Ideas > Tridion Sites Ideas

Non-localizable fields

Top Comments