2024 Nov 04 2:11 PM - edited 2024 Nov 04 2:12 PM
Hello everyone! I am having a problem to create a localized attribute by region via Impex. Short description: robots has a cable length and unit, which is different for different regions.
<maptypes>
<maptype code="localized:Cable" argumenttype="RegionCable" returntype="Cable" autocreate="true" generate="false"/>
</maptypes>
<itemtypes>
<itemtype code="RegionCable" extends="GenericItem"
jaloclass="com.blablabla.RegionCable">
<deployment table="RegionCable" typecode="10103"/>
<attributes>
<attribute qualifier="code" type="java.lang.String">
<modifiers read="true" write="true" search="true"/>
</attribute>
</attributes>
<!-- Maybe some translation will come here -->
</itemtype>
<itemtype code="Cable" extends="GenericItem"
jaloclass="com.blablabla.Cable">
<deployment table="Cable" typecode="10102"/>
<attributes>
<attribute qualifier="length" type="java.lang.Integer">
<modifiers read="true" write="true"/>
<persistence type="property"/>
</attribute>
<attribute qualifier="lengthUnit" type="Unit">
<modifiers read="true" write="true"/>
<persistence type="property"/>
</attribute>
</attributes>
</itemtype>
<itemtype code="Robot" extends="Product"
jaloclass="com.blablabla.Robot">
<attributes>
...
<attribute qualifier="cable" type="localized:Cable">
<persistence type="property"/>
</attribute>
</attributes>
</itemtype>
Creating that connection in Backoffice is easy-peasy. The challenge starts, when trying to update the robot via impex
INSERT_UPDATE RegionCable; code[unique=true]
; EU ;
INSERT_UPDATE Cable; &cabId; length[unique=true]; lengthUnit(code)[unique=true]
; 2m ; 2 ; m
UPDATE Robot; code[unique=true]; cable[code=EU]; $catalogVersion
; ROBOT ; 2m
The exception thrown in this case is the following:
Exception ocurred, will ignore: de.hybris.platform.impex.jalo.ImpExException: begin 0, end -1, length 2
Thanks in advance for your suggestions!
Request clarification before answering.
As mansurarisoy pointed out, localized types are really Map types under the hood. So that means your robot will have a different cable in different parts of the world. For example the cable attribute may have values like these:
en_BR | cable1 |
en_US | cable2 |
de | cable3 |
fr | cable3 |
fr_CA | cable2 |
es | cable3 |
where the left column contains ISO codes for the languages (LanguageModel existing in the platform); and the right column contains PKs of the corresponding Cable items. This makes sense, if the cable is some standard cable acceptable in that part of the world. If it's just about the unit of measurement, this design is an overhead and no localization is needed at all, in my opinion.
Now, about the impex. This is impex documentation to use in addition to the links provided mansurarisoy.
I found a few problems with it:
I think, the corrected impex should be like this:
INSERT_UPDATE RegionCable; code[unique=true]
; EU ;
INSERT_UPDATE Cable; length[unique=true]; lengthUnit(code)[unique=true]
; 2 ; m
UPDATE Robot; code[unique=true]; cable(length, lengthUnit(code))[lang=en]
; ROBOT ; 2:m
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
19 | |
14 | |
3 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.