Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

AssetEntryUsage entries are not automatically generated during lar importing

Written By

Sergio Alonso

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • We observed that after importing a full site export (pages + web contents), there are not any entries for AssetEntryUsage in database.
  • We checked it with our own groovy script.
  • Our problem is that we have more than twenty sites with hundreds of web contents in each of them, and we want to show their usages from our searchers.

Environment

  • Liferay DXP 7.2

Resolution

  • In Liferay DXP 7.2, the AssetEntryUsage entity is not included in the export process. Thus, when a lar file is imported, there are not any AssetEntryUsage entities imported directly.
  • What happens is these entities are generated in a lazy way when the user requests them either from web content edition (View Usages tab) or from kebab menu in web content administration (View Usages option).

Additional Information

  • The source code which does the AssetEntryUsage entities generation is: 
    com.liferay.asset.taglib.internal.servlet.taglib.util.AssetEntryUsagesTaglibUtil.recordAssetEntryUsage(String className, long classPK)
    className: gets the related to "com.liferay.journal.model.JournalArticle"
    classPK: gets the classpk attribute from AssetEntry
  • The source is available from DXP 7.2 Fix Pack 8+

 

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?