Legacy Knowledge Base
Published Jun. 30, 2025

ServiceBuilder Updates Not Reflected in Database

Written By

Daniel Martinez Cisneros

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

Service Builder changes does not apply updates on database after add or delete a column in service.xml

Environment

  • Quarterly Releases

Resolution

Liferay has the property schema.module.build.auto.upgrade set to false by default. Unless you set this property to true in your environment, the auto upgrade will not be executed and changes to the database will not be applied.

As mentioned in the Liferay documentation, Liferay DXP DOES NOT support Build Auto Upgrade in production. The steps to upgrade changes in service.xml are explained below:

  1. Create an upgradeStep as described in this link.
  2. After creating the upgradeStep defining table changes, execute the buildService task and deploy the -service and -api modules.
  3. Once deployed, go to Gogo Shell and execute the upgrade:
upgrade:execute [module_name]
//Verify execution:
upgrade:list [module_name]

After applying these steps, your Service Builder will be updated and columns will be added or removed (you can also create indexes). Changes will also be reflected in the Release_ and ServiceComponent tables.

Additional information

Did this article resolve your issue ?

Legacy Knowledge Base