AEM 6.2 Dialog breaking if Multifield items exceeds limit | Community
Skip to main content
P
pradeepdubey82
Level 5
December 13, 2017

AEM 6.2 Dialog breaking if Multifield items exceeds limit

  • December 13, 2017
  • 13 replies
  • 10582 views

Hi All,

I am using AEM 6.2. In my component there are 3 tabs. Each tab has 3 multifields, so total 9  multifields in component. As soon as i drag and drop component in page  and author it, it work as expected(added approximately 200 items in all 9 multifield widgets),  it stored these values in crx repository,  till here everything is fine.

When i click edit button to edit dialog values. Dialog is broken. I analysed till 176(total items in all 9 multifield) elements it is working. After which it start breaking the dialog.

Now i am unable to edit the dialog. This issue is now becoming critical to fix.

Any help is really appreciated, how to make sure to author any no of items in multifield without breaking the dialog when open for edit?

Please advise if anyone face similar challenge.

Installed SP1 on  AEM6.2 also didn't fix my issue.

Thanks,

Pradeep

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

13 replies

Show previous replies
edubey
edubey
Level 10
December 18, 2017

Yeah.....that's the reason I mentioned similar article

1. Remove eaem-nested properties in your dialog multifield, as per above xml you shared there are two.

2. Once its is removed, test a dialog with smaller number of multifield, if your component still works, raise a day care ticket for freeze issue

3. If it doesnt work, then is a JS at project level which backs eaem-nested attribute.

    P
    pradeepdubey82Author
    Level 5
    December 18, 2017

    If i remove eaem-nested property in in  dialog, it doesn't store content in one property after authring. Content is storing in two property, hence data is not loading at all in dialog to edit. This property is responsible to keep the data in one property.

      edubey
      edubey
      Level 10
      December 18, 2017

      Yes, I was expecting something similar

      This attribute is not from OOTB product , so now

      1. You need to find that JS in your project level which is using this as validator and optimize it

      OR

      2. See if you can split one dialog to multiple dialog to make authoring work in simpler way

      These are not the answers you may be expecting but yeah...if there was something purely from product side issue...Day care would have helped.

      If you still feel, you can raise a support ticket for more help.

        Terms & ConditionsAccessibility statement

        Loading footer...