on 2019 Feb 07 10:15 AM
We have a field in Hybris model configured as String localized collection like :
<attribute qualifier="xyz" type="localized:StringCollection">
<modifiers optional="true" read="true" write="true" />
<persistence type="property" />
In such case Hybris fallback strategy doesn't work correctly . Only the session language is taken into consideration. If a localization doesn't exist for the given language the result will be empty even it has the fallback localization. Somebody knows is it Hybris issue(or feature 🙂 ) or something wrong with the model configuration. As workaround is to create custom attribute handler . But possibly exists more "pretty" solution
Request clarification before answering.
In this situation, I recommend using a relation instead of StringCollection. You will have much more flexibility as well as you will get rid of this fallback language issue.
Helpful reading - https://help.hybris.com/1811/hcd/8c755da8866910149c27ec908fc577ef.html#typesystemdocumentation-1nrel...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.