Legacy Knowledge Base
Published Jul. 2, 2025

Site export (or staging enabling) fails with "missing reference(s) that could not be found during the process."

Written By

Sorin Pop

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

  • I am exporting a site and it fails with an error like "The Dynamic Data Mapping Template (Automatic Copy): Service Menu has missing reference(s) that could not be found during the process." and a stack trace like in the attached file (site_export_error.txt)

Environment

  • DXP 7.1, DXP 7.2

Resolution

  • The root cause is that the "displayStyleGroupId" portletPreference is 0 (or blank, which resolves to 0) or, for example, you had programmatically created several pages and ADTs, including setting portlet preferences on those pages to use the custom ADTs. That code didn't set the displayStyleGroupId.
  • Make sure to properly set displayStyleGroupId. Fix the templates within your theme to include the corresponding displayStyleGroupId pref as well as cleanup/remove existing portletPrefs or fix the affected portletpreferences rows with an SQL. 
  • The use cases can be different and therefore so the resolution. What is important, and what we learned so far is that this has to do with some kind of custom code (custom theme, etc.) which does not set displayStyleGroupId properly. Hopefully that should be enough to figure it out for your specific case.

 

Did this article resolve your issue ?

Legacy Knowledge Base