on 01-26-2022 12:40 PM
Hi CAP Community,
we have different entities in our CAP project (Node.js) where we use localized strings. The locale property of the *_texts entities are defined as String and are not associated with a Locales entity by CAP. This makes maintaining translations for those entities in Fiori Elements apps error prone, as the user can enter anything in the locale field.
Is there a way in CAP to link the locale in the *_texts entities to a dedicated Locale entity? If not, how can we provide a user-friendly way to maintain such translations? Or is the localized String feature only intended for data that is not maintained by end users?
Kind regards,
Sebastian
User | Count |
---|---|
78 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.