since
Mar 02, 2021
Level 1
Re: Image Map feature getting stored in DAM asset metadata
Nithyasri_K
- Adobe Experience Manager
61
0
0
Nithyasri_K
Thanks @raj_mandalapu . This helps will use this as a workaround till I
find a more direct approach.
Views
Likes
Replies
Re: Image Map feature getting stored in DAM asset metadata
Nithyasri_K
- Adobe Experience Manager
54
0
0
Nithyasri_K
Thanks Viji, this works as you have mentioned above with inline
editing.But I am using an image component inside carousel, inline
editing does not work here. Also imagemap property is getting stored in
the carousel node and not in image.Any suggestions for this case
Views
Likes
Replies
Image Map feature getting stored in DAM asset metadata
Nithyasri_K
- Adobe Experience Manager
131
0
4
Nithyasri_K
When I add map to image component, imagemap property is stored in
content component node and DAM asset metadata. So when I drag-drop this
same image in different page/comp, same imagemap is getting added. Is
there a way to store only under content/component node ? My requirement
is to have image map reference only in the page where I edit. Not to
change the asset in DAM, so that it affects all the places where it is
used.
Views
Likes
Replies
Re: Iterate Multivaluedmap in sightly
Nithyasri_K
- Adobe Experience Manager
170
2
1
Nithyasri_K
Hi @Manjunath_K Thank your for the help. Your solution worked with a
slight modification as per my object. ${year.key} ${type.key}
{modelList.modelProp}
Views
Likes
Replies
Iterate Multivaluedmap in sightly
Nithyasri_K
- Adobe Experience Manager
254
0
4
Nithyasri_K
I am trying to iterate a multivaluedmap MultiValuedMap>> through HTL as below. But, I get values upto
two levels which are String. Not able to access ModeObj. ${year} ------ First level
String gets printed ${type}
--------Second level String gets printed ${nav.map[year][type]} or
${nav.map[year][type]['modelObjProp']}------- not working
Views
Likes
Replies
