This solution also worked for me. We are currently on 6.5.13. Thanks!!!

I also encountered this issue on 6.5.9 in our test environment with the column component and resolved it by running offline compaction. Thanks.

@Shashi_Mulugu thanks for the answer.

Hey, I was wondering what happens when a dispatcher runs out of cache space?

Of course this comment wasn't helpful and it's not even remotely as funny as you thought it was. Do better next time.

Thanks for the info and link. Our webmaster runs compaction weekly and was noticing the numbers steadily increasing and was wondering how the naming conventions would be handled since we're up around 64832.

The tar files used by AEM in the repository/segmentstore have names like dataNNNNNL.tar, where NNNNN is a 5 digit number and L is a letter. What happens when NNNNN needs to be greater than 99999?

It's not related to AEM Forms either. Please stop polluting this thread with unrelated suggestions.

Arun,I am aware of how to implement show/hide logic for widgets within a dialog. That's not what i'm asking about here. I'm referring to the specific showhide xtype which handles show/hide logic for the HTML elements in a web form, not widgets in a dialog. The values captured in this xtype are passe...

Hey Arun,Thanks for the reply but the examples provided won't work for this scenario. The showhide is an OOTB xtype. It is used to capture the show/hide logic for fields within a web form instead show/hide logic for widgets within a dialog.