About Liferay classNameId

Every core Liferay entity (JournalArticle, Document, User, Group, Blog, etc.) has a unique numeric identifier called a classNameId. This ID is stored in Liferay's portal database and used throughout the system for asset tracking, permissions, workflows, and custom module development.

Why classNameId Matters

• SQL Queries: Query the AssetEntry table to find all assets of a specific type.
• Permissions API: Check user permissions on specific entity types using classNameId.
• Asset API: Fetch, update, or delete assets by type using the Liferay Asset framework.
• Workflow Integration: Route workflow tasks based on entity type classNameId.
• Custom Modules: Reference entity types in your own Liferay module development.

How classNameId is Used

When you create or publish an asset in Liferay (a blog post, web content article, document, etc.), the system records it in the AssetEntry table with the entity's classNameId. This allows the Asset framework to:

• Track all publishable content across the entire portal in one table
• Apply permissions, categories, tags, ratings, and comments uniformly across all entity types
• Enable unified search, feeds, and content discovery

Example: Query Assets by Type

To find all web content articles in your portal, you could query:

How to Use This Lookup Table

1. Search: Type an entity name (e.g., JournalArticle, User, DLFileEntry) or module name (e.g., journal, asset, blogs) into the search box.
2. Review: The table shows the numeric classNameId, the full Java class name, the module, and a description.
3. Copy: Click the Copy button to copy the full class name to your clipboard.
4. Use: Use the classNameId in your SQL queries, Java code, REST API calls, or configuration files.

Frequently Asked Questions

What is a classNameId in Liferay?

A classNameId is a unique numeric identifier for each core Liferay entity type (JournalArticle, DLFileEntry, User, etc.). Used in database queries, asset lookups, and permission checks.

Where do I use classNameId?

Common uses: SQL queries on AssetEntry table, Permissions API (checkPermission), Asset API lookups, custom module development, workflow integration, and dynamic queries.

Is this tool official?

No. This is a community reference tool. The classNameId values are from Liferay's open-source codebase and are consistent across versions, but always verify in your own Liferay instance.

How do I find the classNameId in my running portal?

Query the portal_classname table: SELECT classnameid, value FROM classname_ WHERE value = 'com.liferay.journal.model.JournalArticle'

Why do some classNameIds not match my portal?

Custom entities or third-party plugins may have different IDs. Always check your portal's classname_ table for the authoritative ID in your instance.

Database Reference

In your Liferay database, the classname_ table contains the authoritative mapping:

This tool displays the standard core entity mappings. Custom plugins and third-party modules may have additional classNameId entries in your instance.