Exporting and Importing DDL Records using a Global Scope structure results in a NPE

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.0 DXP FP10, Master
• Fix Version/s: 7.0.0 DXP FP27, 7.0.X EE, 7.0.4 CE GA5, 7.1.X, Master
• Component/s: Content Publishing > Staging, Dynamic Data Lists, Dynamic Data Mapping
• Labels:
  • liferay-digital-enterprise-70-sp5
  • liferay-fixpack-de-27-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Story Points: 1.25
• Fix Priority: 3
• Git Pull Request: https://github.com/matethurzo/liferay-portal/pull/1653

Importing a global scope DDMStructure can lead to an incorrectly mapped sourceCompanyGroupId which leads to a NPE during the import (See stack.txt).

Data exported (See attached lar file):
DDLRecord using a default Global scope DDMStructure (Inventory). The exported lar file will contain the exported DDMStructure in the global scope (id 20152).

On import:
The DDMStructure will be imported as a new structure in the imported site scope, not global. This causes the PortletDataContextImpl to incorrectly map the sourceCompanyGroupId to the target import site, which causes future resolution of the sourceCompanyGroupId to resolve to the target site instead of the global site.