9,334
edits
View: Difference between revisions
Jump to navigation
Jump to search
→Best practice in renaming a view: add list of disallowed characters, link Localization examples
(→Best practice in renaming a view: add list of disallowed characters, link Localization examples) |
|||
| Line 234: | Line 234: | ||
=== Best practice in renaming a view === | === Best practice in renaming a view === | ||
Keep in mind that the view name is used as a logical name, so it's used all over the application. If someone changes the name of a view, it can cause issues with the application. Especially if they | Keep in mind that the view name is used as a logical name, so it's used all over the application. If someone changes the name of a view, it can cause issues with the application. Especially if they change the default view names on pre-defined entities. | ||
Views are used in map, calendar, in entities as public, associated, or lookup views. So when the name is changed, you should reset the views on all these places. | Views are used in map, calendar, in entities as public, associated, or lookup views. So when the name is changed, you should reset the views on all these places. | ||
It might be easier to use [[Localization]] feature to change the display name of a view, while keeping the logical name untouched. To enable this, you need to keep the view names without spaces or special characters | It might be easier to use [[Localization]] feature to change the display name of a view, while keeping the logical name untouched. To enable this, you need to keep the view names without spaces or special characters. Underscore is okay to use, but the following characters are not: <code><nowiki>/\%#&*<>?|“+:{}</nowiki></code>. Also, some national characters and non-Latin characters are not allowed. See [[Localization examples]] for inspiration. | ||
=== Editable field === | === Editable field === | ||