Hi everyone,
I have a weird issue in AEM 6.5.21 with the Asset References where for each item, if it was referenced more than 10 times, the references tab will show not more than 10 items. I have checked the indexes and the results provide, for one example, 12 results, while the UI in the AEM gives 10 results. The same applies to the Classic UI references, always max. of 10 items are shown.
In the UI, I can see that the results are fetched from /bin/wcm/references (Classic UI) or from /mnt/overlay/dam/gui/content/assets/jcr:content/rails/references/items/references.provider.html (Touch UI), but I wasn't able to find any limitation/restrictions to max. 10 items.
Here are some screenshots:
You can see that in the CRX query and in the query explanation, I can see 12 results, while the UI gives 10. While doing a move operation, I see all the references, all 12 of them, but in the UI it's max. 10. This is confusing for the content authors sometimes, so I'd like to get that resolved.
Thanks in advance.
Best regards,
Matija
Solved! Go to Solution.
Views
Replies
Total Likes
Thanks for the reply. I'll try to check with Adobe about it.
In the meantime, I have noticed that after extending the damAssetLucene index, at least the functionality works where I can see all the references are properly updated, even though UI provides only limit of 10 results.
If someone has the same issue with content fragments, extend the existing damAssetLucene index with the following index rule:
<contentFragment
jcr:primaryType="nt:unstructured"
name="jcr:content/contentFragment"
propertyIndex="{Boolean}true"/>Also, to the damAssetLucene root node add the following field:
tags="[visualSimilaritySearch]"
Views
Replies
Total Likes
@MatijaLeskovic I would suggest to check with Adobe with a ticket? In AEM 6.5.21 , the component live usage references scroll also is broken, that have been fixed in SP 22. Similarly this issue also could be one scroll issue.
Views
Replies
Total Likes
Thanks for the reply. I'll try to check with Adobe about it.
In the meantime, I have noticed that after extending the damAssetLucene index, at least the functionality works where I can see all the references are properly updated, even though UI provides only limit of 10 results.
If someone has the same issue with content fragments, extend the existing damAssetLucene index with the following index rule:
<contentFragment
jcr:primaryType="nt:unstructured"
name="jcr:content/contentFragment"
propertyIndex="{Boolean}true"/>Also, to the damAssetLucene root node add the following field:
tags="[visualSimilaritySearch]"
Views
Replies
Total Likes
Views
Likes
Replies