Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.

AEM Upgrade 6.5.17 issue with Nested Multi-field Authoring Focus Missing

Avatar

Level 3

This is regarding the AEM upgrade as we are upgrading to AEM SP 6.5.17  and The issue is when we add fields in the nested Multi-field then the focus is wrongly mapped to the first field of the parent or the first field of the first set of the nested field. This issue happens only if the nested multi-field is added inside the tabs. Please let me know if any one experience this issue in AEM SP 6.5.13. Any help is appreciated. Thank you.

7 Replies

Avatar

Level 3

I fixed the same issue a year back, below steps might be helpful to you resolve the same

  • Add new property for the same node as composite="{Boolean}true".
  • Go to the child node named as field and remove acs-commons-nested property.
  • Update the sling:resourceType for the field from granite/ui/components/foundation/form/fieldset to granite/ui/components/coral/foundation/container.

Make sure nested multiField are storing the data in nodes format and not in JSON format.

For already configured json data nodes write a script to convert it into the jcrNodes

Avatar

Level 3

@Nilesh_Mali  Thanks for the quick response. Whatever you suggested those are already there in the nested multi field node structure and not to implement. is there any other things which to be implement, Please check and suggest. Please find my comments inline. Thanks

 

  • Add new property for the same node as composite="{Boolean}true" -  These property are already there.
  • Go to the child node named as field and remove acs-commons-nested property. - This property is already not there.
  • Update the sling:resourceType for the field - Coral path is already there. from granite/ui/components/foundation/form/fieldset to granite/ui/components/coral/foundation/container

 

Avatar

Level 3

@Nilesh_Mali Please find the dialog xml below and let me know if any other thing required. Thanks

 

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"
jcr:mixinTypes="[]"
jcr:primaryType="nt:unstructured"
jcr:title="Test Header Configuration"
sling:resourceType="cq/gui/components/authoring/dialog">
<content
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/container">
<items jcr:primaryType="nt:unstructured">
<tabs
jcr:primaryType="nt:unstructured"
jcr:title="Test Configuration Tabs"
sling:resourceType="granite/ui/components/coral/foundation/tabs"
maximized="{Boolean}true">
<items jcr:primaryType="nt:unstructured">
<test-products
jcr:primaryType="nt:unstructured"
jcr:title="Test Menu"
sling:resourceType="granite/ui/components/coral/foundation/container"
margin="{Boolean}true">
<items jcr:primaryType="nt:unstructured">
<columns
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/fixedcolumns"
margin="{Boolean}true">
<items jcr:primaryType="nt:unstructured">
<column
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/container">
<items jcr:primaryType="nt:unstructured">
<testType
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/form/select"
fieldDescription="Test Type"
fieldLabel="Test Type"
name="./testType">
<items jcr:primaryType="nt:unstructured">
<selectlayout
jcr:primaryType="nt:unstructured"
text="Select Layout"
value="select"/>
<oldlayout
jcr:primaryType="nt:unstructured"
text="Test Menu old"
value="old"/>
<newlayout
jcr:primaryType="nt:unstructured"
text=" Test Menu new"
value="new"/>
</items>
</testType>
<testTabHeading
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/form/textfield"
fieldDescription="Test Heading"
fieldLabel="Test Heading"
name="./testHeading"/>
<testMenulabel
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/form/textfield"
fieldDescription="Test Menu Label"
fieldLabel="Test Menu Label"
name="./testMenuLabel"/>
<productlist
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/form/multifield"
composite="{Boolean}true"
fieldLabel="Product Lists">
<field
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/container"
name="./productsList">
<items jcr:primaryType="nt:unstructured">
<prodheading
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/form/textfield"
fieldDescription="Enter The Product Heading"
fieldLabel="Product Heading"
name="./productHeading"/>
<produrl
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/form/pathbrowser"
fieldDescription="Enter The Product URL"
fieldLabel="Product URL"
name="./productUrl"/>
<productscta
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/form/multifield"
composite="{Boolean}true"
fieldLabel="Products CTA Fields">
<field
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/include"
name="./prodsCTA"
path="/mnt/override/apps/myproject/components/reusable-fields/headercta"
resourceType="granite/ui/components/coral/foundation/container"/>
</productscta>
</items>
</field>
</productlist>
</items>
</column>
</items>
</columns>
</items>
</test-products>
</items>
</tabs>
</items>
</content>
</jcr:root>

Avatar

Level 2

Hi Adobe Expert, 

I am also facing the same issue and tried the solution. but it is not working. any help is much appreciated.

Avatar

Level 3

Ji @senthil86 , We opened a support ticket with Adobe . This issue is expected and they said to wait for the hot fix release from adobe for this issue. I think you can check the same they might have released the hot fix package for this. Thanks

Avatar

Level 2

@kchaura Thank you. we recently updated 6.5.20. but we are facing the same issue.