Legacy Knowledge Base
Published Sep. 10, 2025

Compile error for CustomSQLUtil after upgrading a custom module to DXP 7.1+

Written By

Eugene Shin

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

  • When addressing build.gradle changes needed for com.liferay.portal.dao.orm.custom.sql by removing the version number, our build fails. A compile error is returned.

Environment

  • Liferay DXP 7.1+

Resolution

  • As of DXP 7.1, the static class com.liferay.portal.dao.orm.custom.sql.CustomSQLUtil and its module com.liferay.portal.dao.orm.custom.sql have been removed. Instead, use the modularized CustomSQL OSGi service from com.liferay.portal.dao.orm.custom.sql.api, as the com.liferay.util.dao.orm.CustomSQLUtil class in util-java still exists. If previously using the class and upgrading to DXP 7.1 and above, you must update your dependencies to reflect the changes.
    • In a Liferay Workspace with liferay.workspace.product set, leave out the version, because the target platform supplies it.
    • Otherwise, use the version from your release's BOM (1.x for DXP 7.1, 2.x for 7.2, 3.x for 7.3, 4.x for 7.4 and later). For example:
    • provided group: "com.liferay", name: "com.liferay.portal.dao.orm.custom.sql.api", version: "1.0.1"
      

Additional Information

  • For related context, see the attached HistoricMBThread-daoRemoval.pdf discussion.
Did this article resolve your issue ?

Legacy Knowledge Base