Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Upgrade Error DDM Forms Replacing Polls

Written By

Kenny Back

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 are running an upgrade from Liferay 7.0 to 7.4 and observing the following error in the log:
WARN  [main][BasePortletIdUpgradeProcess:511] null
com.liferay.portal.kernel.log.LogSanitizerException: org.postgresql.util.PSQLException:
ERROR: duplicate key value violates unique constraint "ix_cb778855"_  Detail: Key 
(ownerid, ownertype, plid, portletid, ctcollectionid)=
(0, 3, 0, com_liferay_dynamic_data_mapping_form_web_portlet_DDMFormAdminPortlet, 0) 
already exists. [Sanitized]

Environment

  • DXP 7.0 > DXP 7.4

Resolution

  • The upgrade is failing because it is trying to convert the older version of what DDM Forms replaced, Polls. 
  • Two queries can be run to resolve this. 
Select * from PortletPreferences where portletid = 'com_liferay_polls_web_portlet_PollsPortlet'

If you can confirm that  com_liferay_polls_web_portlet_PollsPortlet  is present then run the next query:

Delete from PortletPreferences where portletid = 'com_liferay_polls_web_portlet_PollsPortlet'

Additional Information

  • There is a ticket being worked on to patch this in a future update: LPS-187221 

 

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