Details
-
Type:
Regression Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 6.2.0 CE M4
-
Fix Version/s: 6.2.0 CE M5
-
Component/s: DM
-
Labels:None
-
Environment:Tomcat 7.0.34 + MySQL 5. Portal 6.2.x GIT ID: 2a04b1292782b1d0be60152b33153d7508c100b0.
-
Fix Priority:5
-
Caused by:Another new feature
-
Similar Issues:
Description
This doesn't happen in ee-6.1.x. In ee-6.1.x, the original fields are present when editing a document type.
Steps to reproduce:
- Go to Control Panel > Documents and Media
- Click Manage > Document Types and add a Document Type with a Boolean field
- Click on the actions menu next to the created document type and click Edit
- The boolean field won't be there, and there will be a Metadata field at the bottom that has the same name as the document type
Expected result:
The boolean field should be present in the build canvas. All the original fields ought to be there as this makes it easy for the user to edit the existing document type. There also shouldn't be any metadata fields because the user didn't add one when creating the document type.
Actual result:
The build canvas is empty, and there is a metadata field that has the same name as the document type.
Issue Links
- is caused by
-
LPS-32875
DDM structure keys should be unique per groupId and classNameId
-

This issue is caused by
LPS-32875.Working as of:
Tomcat 7.0.34 + MySQL 5. Portal 6.2.x GIT ID: 85b610beac9c9ebbae386e57dbd370c6317ae769.
Git bisect output: